Agile Add Capture
Table of Contents
When to use this skill
When the user describes an idea, observation, bug, or feature request and asks to "capture" it or file it in the inbox — a single, well-defined item rather than a block of freeform notes. For bulk decomposition of unstructured text, use How do I capture ideas from freeform text? instead.
How to use this skill
- Derive the capture fields from the user's message:
- slug — snake_case, 3–6 words, noun phrase (e.g.
warn_on_create_without_role). - title — 5–10 words, imperative or noun phrase.
- description — one sentence: what it is.
- tags — 2–4 relevant tags (component, topic, area).
- slug — snake_case, 3–6 words, noun phrase (e.g.
Scaffold the file via
compass add capture:./compass.sh add capture \ --slug <slug> \ --parent-dir doc/agile/product_backlog/inbox \ --title "<title>" \ --description "<description>" \ --tags "<tag1>,<tag2>"
- Fill in the body:
* What— one paragraph: the idea, with enough detail to act on it later. Include any file paths, line numbers, or links the implementer will need.* Why— motivation: the problem being solved, inconsistency being fixed, or user need being met.* References— any links, file paths, or related captures.* See also— id-links to related knowledge docs or stories.
Commit and push:
git add <file> && git commit -m "[agile] Capture: <title>" && git push
Recipes
- How do I capture ideas from freeform text? — bulk variant: decompose unstructured notes into multiple captures.
Reference
- Product backlog — bucket structure (inbox / next / deferred / discarded) and triage lifecycle.
- Document types§=capture= — required frontmatter and sections.