5-phase-workflow 1.1.2 → 1.2.1

package/src/commands/5/plan-feature.md

@@ -101,9 +101,14 @@ Use Task tool with subagent_type=Explore for complex exploration.
 
 **Goal:** Understand what already exists so you can ask informed questions.
 
-### Step 4: Intensive Collaboration (5-10 Questions)
+### Step 4: Intensive Collaboration (5-10 Questions, ONE AT A TIME)
 
-**CRITICAL:** After exploring the codebase, engage in intensive Q&A using the AskUserQuestion tool. Ask 5-10 clarifying questions based on your findings. This is NOT optional.
+**CRITICAL:** After exploring the codebase, engage in intensive Q&A. This is NOT optional.
+
+- Ask 5-10 clarifying questions using AskUserQuestion
+- **ONE question at a time** - wait for answer before next question
+- Do NOT list multiple questions in one message
+- Do NOT skip to creating feature.md before asking at least 5 questions
 
 **Question categories to explore:**
 
@@ -154,7 +159,7 @@ Use Task tool with subagent_type=Explore for complex exploration.
 - "Could we use existing Z component instead?"
 - "Is a full factory needed or just simple creation?"
 
-Use AskUserQuestion to present options and trade-offs. Multiple questions can be asked in batches.
+**Ask questions ONE AT A TIME.** Use AskUserQuestion for each question. For clarifying questions, provide 2-4 options where meaningful. Wait for the user's answer before asking the next question. Open questions (like feature description) can use free text.
 
 ### Step 5: Determine Feature Name
 
@@ -164,95 +169,25 @@ Based on the feature description and discussion:
 
 ### Step 6: Create Feature Specification
 
-Write a comprehensive feature spec to `.5/{TICKET-ID}-{description}/feature.md` with the following structure.
+Write a comprehensive feature spec to `.5/{TICKET-ID}-{description}/feature.md` using the template structure.
 
 **THIS IS YOUR FINAL OUTPUT. After creating this file, proceed immediately to Step 7.**
 
-```markdown
-# Feature: {TICKET-ID} - {Title}
-
-## Ticket ID
-{TICKET-ID}
-
-## Summary
-{1-2 sentence overview of what will be implemented}
-
-## Problem Statement
-{Why is this feature needed? What problem does it solve?}
-
-## Requirements
-
-### Functional Requirements
-- {Requirement 1}
-- {Requirement 2}
-- ...
-
-### Non-Functional Requirements
-- {Performance requirements}
-- {Compatibility requirements}
-- ...
-
-## Constraints
-- {Business constraints}
-- {Technical constraints}
-- {Time/resource constraints}
-
-## Affected Components
-- **{component/module-1}** - {What changes here}
-- **{component/module-2}** - {What changes here}
-- **{component/module-3}** - {What changes here}
-- ...
-
-## Entity/Component Definitions
-
-### {EntityName} (if applicable)
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| id | {Entity}Id | Yes | Unique identifier |
-| name | String | Yes | Entity name |
-| ... | ... | ... | ... |
+**Template Reference:** Use the structure from `.claude/templates/workflow/FEATURE-SPEC.md`
 
-### Business Rules
-- {Rule 1}
-- {Rule 2}
-- ...
+The template contains placeholders like `{TICKET-ID}`, `{Title}`, `{1-2 sentence overview}`, etc. Replace all placeholders with actual values based on your research and the Q&A session.
 
-## Acceptance Criteria
-- [ ] {Criterion 1 - how to verify success}
-- [ ] {Criterion 2}
-- [ ] {Criterion 3}
-- ...
-
-## Alternatives Considered
-
-### Option 1: {Alternative approach}
-**Pros:** {Benefits}
-**Cons:** {Drawbacks}
-**Decision:** Rejected because {reason}
-
-### Option 2: {Another alternative}
-**Pros:** {Benefits}
-**Cons:** {Drawbacks}
-**Decision:** Rejected because {reason}
-
-### Chosen Approach: {Selected approach}
-**Rationale:** {Why this approach was chosen}
-
-## Questions & Answers
-
-### Q1: {Question from collaboration phase}
-**A:** {Answer from developer}
-
-### Q2: {Question}
-**A:** {Answer}
-
-...
-
-## Next Steps
-After approval:
-1. Run `/clear` to reset context
-2. Run `/5:plan-implementation {TICKET-ID}-{description}`
-```
+Key sections to populate:
+- **Ticket ID & Summary** - From branch extraction and feature description
+- **Problem Statement** - Why this feature is needed
+- **Requirements** - Functional and non-functional requirements from discussion
+- **Constraints** - Business, technical, and time constraints identified
+- **Affected Components** - Discovered from codebase exploration
+- **Entity Definitions** - If the feature involves new data structures
+- **Acceptance Criteria** - Verifiable criteria for success
+- **Alternatives Considered** - Options discussed and why chosen approach was selected
+- **Questions & Answers** - Document the Q&A from the collaboration phase
+- **Next Steps** - Instructions for proceeding to Phase 2
 
 ## Instructions
 
@@ -265,7 +200,7 @@ Follow these steps **IN ORDER** and **STOP after step 8**:
 5. **Challenge assumptions** - Present alternatives, question complexity
 6. **Determine feature name** - Create short kebab-case description
 7. **Create feature specification** in `.5/{TICKET-ID}-{description}/feature.md`
-8. **Inform the developer** to review the spec and then run `/clear` followed by `/5:plan-implementation {TICKET-ID}-{description}`
+8. **Inform the developer** to review the spec, run `/clear` to reset context, and then run `/5:plan-implementation {TICKET-ID}-{description}`
 
 **🛑 STOP HERE. YOUR JOB IS COMPLETE. DO NOT PROCEED TO IMPLEMENTATION.**
 
@@ -315,7 +250,9 @@ Follow these steps **IN ORDER** and **STOP after step 8**:
     **Next steps:**
     1. Review the feature spec
     2. If changes needed: `/5:discuss-feature PROJ-1234-add-emergency-schedule`
-    3. If approved: `/clear` then `/5:plan-implementation PROJ-1234-add-emergency-schedule`"
+    3. If approved:
+       - **Run `/clear` to reset context** (recommended between phases)
+       - Then run `/5:plan-implementation PROJ-1234-add-emergency-schedule`"
 
 **🛑 COMMAND COMPLETE. The skill stops here and waits for user to proceed to Phase 2.**