| name | idea-capture |
| description | Save, update, link, or delete an idea, task candidate, PR, issue, project thought, conversation insight, or outcome in the user's Markdown idea directory. Use when the user invokes $idea-capture, says to remember/save/capture/log an idea, says an existing idea is done, dropped, duplicate, or reopened, or asks to delete/remove/clean a completed or unwanted idea. |
Idea Capture
Use the model for meaning: identify the actual idea, choose human-readable wording, adapt to the user's language, summarize evidence, judge cost/impact/confidence, and decide genuine related ideas.
Use scripts/idea_store.py for mechanics: resolve the store, search/list/read notes, write notes, mark status, and delete exactly matched files. Do not hand-edit idea files unless the helper cannot perform the operation.
Workflow
- Resolve the store with
python scripts/idea_store.py resolve. If the user gives a directory, run python scripts/idea_store.py resolve --dir <dir> --create --save. If no store exists, ask one short setup question for the idea directory.
- For a new capture or substantial update, read
references/idea-note-schema.md and references/capture-guidance.md.
- Use
python scripts/idea_store.py find "<query>" to quickly retrieve relevant ideas from titles, filenames, metadata, URLs, and bodies. Use it for user-provided text, URLs, source ids, filenames, or keywords. Use python scripts/idea_store.py list for status/project scans before creating a new note.
- Compose the note JSON yourself from the source context. Then write it with
python scripts/idea_store.py write.
- For done/dropped/duplicate/reopened/doing, use
find or read to identify the target, then use python scripts/idea_store.py mark with one exact locator: --id, --source-id, --source-url, or --path.
- For delete/remove/clean requests, use
python scripts/idea_store.py delete only after locating exactly one note by id, source_id, source_url, or file path. Never delete by fuzzy title or broad search result alone.
Language
Match the user's language for filenames, titles, visible note bodies, and final responses. Keep metadata keys stable. Preserve canonical code names, commands, API names, file paths, and source titles when translating them would reduce clarity.
Final Response
End with one line:
<Action>: <title-or-id> -> <path>
Use Captured, Updated, Marked, or Deleted for the action.
