Quick goal planning for technical tasks. Compressed vision-requirements-spec-plan into a single goal.md through a brief interview (3-6 questions). For tasks bigger than ad-hoc but not needing the full feature process.
Compressed alternative to the full feature development process. Produces a single goal.md document through a quick conversational interview — typically 3-6 questions total.
One document instead of four. Plain language instead of formal requirement IDs. Quick interview instead of deep multi-phase discovery.
When to use this:
When NOT to use this:
/feature-vision, /feature-requirements, /feature-spec, /feature-planIMPORTANT: Start by creating a TODO list to track the 3 phases of goal creation. Mark the first phase as "in_progress" and others as "pending".
A goal.md is a single markdown file with four sections:
Target length: 1-2 pages total. If it's getting longer, you're over-thinking it — use the full feature process instead.
Understand what and why. Ask ONE question at a time:
Keep it conversational. Don't ask questions you can answer yourself from context — check the codebase, memory, and project docs first. If the goal is already clear from what the user said, skip straight to confirming your understanding rather than re-asking.
Goal of this phase: Enough understanding to write a clear goal statement and requirements bullets.
Understand how. Again, ONE question at a time:
Be opinionated. If you know the user's stack and preferences, propose an approach and ask for confirmation rather than open-ended questions. Check the codebase for existing patterns before asking.
Goal of this phase: Key technical decisions made. Ready to write the document.
Before generating, confirm the save location:
goals/YYYY-MM-DD-brief-name/goal.md relative to the current project rootGenerate the goal.md with this structure:
# Goal: [Brief Title]
## Goal Statement
[One paragraph — what you're building, why it's needed, what success looks like.]
## Requirements
- [Simple bullet — what the system must do]
- [Another capability]
- [Any constraints]
- [Keep these plain and practical]
## Technical Approach
[Brief — what tools, languages, frameworks. Key technical decisions and why.
Integration points with existing systems. 1-2 short paragraphs max.]
## Plan
- [ ] Step 1 — description
- [ ] Step 2 — description
- [ ] Step 3 — description
- [ ] Sub-step if needed
- [ ] Step N — verify everything works
After generating: Mark all TODO phases complete. Ask if the user wants to start executing the plan or adjust anything first.