Capture a raw idea quickly into docs/planning/ideas/ with a date-prefixed filename and YAML frontmatter. Use when the user says "I have an idea", "capture idea", "new idea", or invokes /capture-idea.
Use this skill when the user says:
/capture-ideaCapture a raw idea quickly into docs/planning/ideas/ with a date-prefixed filename and YAML frontmatter. Ideas are stage 1 of the planning pipeline: captured → evaluated → promoted to PRD.
Creates: docs/planning/ideas/YYYY-MM-slug.md
Accept whatever the user provides — a single sentence is enough. Do not ask clarifying questions upfront.
Before writing the file, search the codebase to understand what the idea refers to:
Only ask the user a question if the idea is so ambiguous that you cannot make a reasonable inference about what it refers to in this codebase (e.g., a single word with no context). One targeted question maximum.
From the description and codebase context, determine:
add-llms-txt-file)seo | engineering | content | design | infrastructureclient-request | analytics | competitor-research | internal | seo-dataunset unless the user signals urgencycaptured on creationFilename format: YYYY-MM-slug.md using today's date for YYYY-MM.
Use the template at docs/planning/templates/idea.md. Populate all frontmatter fields. Write concise content under each section heading based on what you found in the codebase — do not leave sections as empty placeholders. Leave prd: "" blank (filled when promoted).
After creating the file, always update docs/planning/ideas/_index.md:
.md files in docs/planning/ideas/ (excluding _index.md)title, status, priority, and domain_index.md with:
updated date in frontmatter_index.md does not exist, create it using this structureTell the user the file was created at docs/planning/ideas/YYYY-MM-slug.md and ask if they want to immediately evaluate it (status: evaluating) or leave it as captured for later triage.
---