Monoco Memo
Use this skill to quickly capture fleeting notes (fleeting ideas) without creating a formal Issue.
When to Use Memo vs Issue
| Scenario | Use | Reason |
|---|---|---|
| Temporary ideas, inspirations | Memo | No tracking needed, no completion status required |
| Code snippets, link bookmarks | Memo | Quick record, organize later |
| Meeting notes | Memo | Record first, then extract tasks |
| Actionable work unit | Issue | Requires tracking, acceptance criteria, lifecycle |
| Bug fix | Issue | Needs to record reproduction steps, verification results |
| Feature development | Issue | Needs design, decomposition, delivery |
Core Principle: Memos record ideas; Issues handle actionable tasks.
Commands
Add Memo
bash
monoco memo add "Your memo content"
Optional parameters:
- •
-c, --context: Add context reference (e.g.,file:line)
Examples:
bash
# Simple record monoco memo add "Consider using Redis cache for user sessions" # Record with context monoco memo add "Recursion here may cause stack overflow" -c "src/utils.py:42"
View Memo List
bash
monoco memo list
Displays all unarchived memos.
Open Memo File
bash
monoco memo open
Opens the memo file in the default editor for organizing or batch editing.
Workflow
code
Idea flashes → monoco memo add "..." → Regular organization → Extract into Issue or archive
- •Capture: Use
monoco memo addimmediately when you have an idea - •Organize: Regularly (e.g., daily/weekly) run
monoco memo listto review - •Convert: Transform valuable memos into formal Issues
- •Archive: Remove from memos after processing
Best Practices
- •Keep concise: Memos are quick notes, no detailed description needed
- •Convert timely: Valuable ideas should be converted to Issue as soon as possible to avoid forgetting
- •Clean up regularly: Memos are temporary, don't let them accumulate indefinitely
- •Use context: When recording code-related ideas, use
-cparameter to mark the location