| name | subsection-task |
| description | Start implementing a roadmap subsection with impact analysis and structured Q&A. Use when user says "start subsection", "work on subsection", "implement [Phase X] [Subsection Y]", or references working on a specific phase/subsection from the roadmap. Analyzes settled work for impacts, asks clarifying questions with options, then delegates to task-creator for file creation. |
Subsection Task
Implements the spec-driven development workflow for starting a new roadmap subsection.
Workflow
Step 1: Extract Parameters
Identify the Phase and Subsection from user's request.
If clearly specified: Extract directly (e.g., "work on Phase 7, My Library Page")
If ambiguous or missing: Prompt the user:
"Which Phase and Subsection would you like to work on? Please specify like: 'Phase 7: My Library & Discovery' → 'My Library Page'"
Step 2: Read Required Files
Read these files to understand context:
ai_docs/prep/roadmap.md # Current roadmap with completed/pending work
ai_docs/dev_templates/task_template.md # Task document template
Step 3: Identify Settled Work
Scan the roadmap for items marked as:
- ✅ COMPLETED
- "Approved"
- "Settled"
- Design decisions with rationale
Create a list of potentially impacted settled work relevant to this subsection.
Step 4: Impact Analysis
For each potentially impacted item, apply the Material Change Filter:
Only propose changes to settled work if they materially affect correctness, scalability, or safety.
Do NOT propose changes based on:
- Elegance or refactoring opportunities
- Stylistic improvements
- Speculative future needs
If no material impacts exist, explicitly state:
"No change proposals required — this subsection does not materially impact any settled work."
If material impacts exist, prepare as Change Requests (do not implement):
"⚠️ Change Request Required: [description of material issue and affected settled work]"
Step 5: Ask Clarifying Questions
For any ambiguity in the subsection requirements, ask questions using this format:
**Q[N]: [Question Topic]**
[Context for why this matters]
- **Option A:** [Description]
- **Option B:** [Description]
- **Option C:** [Description]
*My recommendation: Option [X]* - [Brief rationale]
Guidelines:
- Limit to 3-5 questions per message to avoid overwhelming
- Always provide a recommended option
- Follow up if more questions arise from answers
Step 6: Present Implementation Preview
After questions are resolved, present the Implementation Options:
**👤 IMPLEMENTATION OPTIONS:**
**A) Preview High-Level Code Changes**
Show detailed code snippets and specific changes before implementing.
**B) Proceed with Implementation**
Begin implementation phase by phase.
**C) Provide More Feedback**
Address additional questions or modify the approach.
Wait for explicit user choice before proceeding.
Step 7: Create Task Document
Once Option A preview is validated or Option B is chosen:
Read and follow the workflow in .claude/skills/task-creator/SKILL.md to create the numbered task file in ai_docs/tasks/.
The task document should include:
- All Q&A decisions made
- Impact analysis results
- Any approved Change Requests
- Implementation plan from the roadmap subsection
Example Usage
User: "Start working on Phase 7, subsection My Library Page"
Response:
- Read
ai_docs/prep/roadmap.md and ai_docs/dev_templates/task_template.md
- Find Phase 7 → My Library Page requirements
- Identify settled work: Phase 3 prompt schema, Phase 6A Prompt Studio
- Analyze impacts → "No change proposals required"
- Ask questions about filtering, pagination, bulk actions
- Present implementation options
- On approval, delegate to task-creator skill
Key Principles
- Material changes only: Don't propose changes for style or speculation
- Options format: Always provide A/B/C options with recommendations
- Explicit approval: Never proceed without user choosing an option
- Delegate file creation: Use task-creator skill for actual task document
