5-phase-workflow 1.1.1 → 1.2.0

package/src/commands/5/configure.md

@@ -19,6 +19,37 @@ After running this command, proceed through the standard phases:
 4. `/5:verify-implementation` - Verify configuration
 5. `/5:review-code` - Review generated files
 
+## ⚠️ CRITICAL SCOPE CONSTRAINT
+
+**THIS COMMAND ONLY CREATES THE CONFIGURATION FEATURE SPEC. IT DOES NOT CONFIGURE.**
+
+Your job in this command:
+✅ Analyze project (detect type, build commands, etc.)
+✅ Gather user preferences via questions
+✅ Create feature spec at `.5/CONFIGURE/feature.md`
+✅ Tell user to run /5:plan-implementation CONFIGURE
+
+Your job is NOT:
+❌ Write config.json directly (Phase 3 does this)
+❌ Create CLAUDE.md directly (Phase 3 does this)
+❌ Generate skills directly (Phase 3 does this)
+❌ Skip user interaction
+❌ Assume project structure
+
+**After creating the feature spec and informing the user, YOUR JOB IS COMPLETE. EXIT IMMEDIATELY.**
+
+## ❌ Boundaries: What This Command Does NOT Do
+
+**CRITICAL:** This command has a LIMITED scope. Do NOT:
+
+- ❌ **Write config.json** - That's Phase 3's job (via configure-project skill)
+- ❌ **Create CLAUDE.md** - That's Phase 3's job
+- ❌ **Generate skills** - That's Phase 3's job
+- ❌ **Skip questions** - Always confirm detected values with user
+- ❌ **Assume structure** - Detect or ask, don't guess
+
+**If you find yourself creating config files or CLAUDE.md, STOP IMMEDIATELY. You should only be creating the feature spec.**
+
 ## Configuration Process
 
 ### Step 1: Analyze Project (auto-detect, no user interaction)
@@ -153,11 +184,24 @@ fi
 - "Suggested test command: `{command}`. Use this?"
   - Options: "Yes (recommended)", "Customize", "None (no test step)"
 
-**2f. Confirm CLAUDE.md generation:**
+**2f. Review tool preference:**
+- "Which code review tool would you like to use?"
+  - Options:
+    1. "Claude (built-in, no setup needed)" — always available
+    2. "CodeRabbit CLI (requires installation)" — external tool
+    3. "None (skip automated review)"
+- If user selects CodeRabbit and it was not detected in Step 1d:
+  - Inform: "CodeRabbit CLI is not installed. You can install it later:"
+    - macOS: `brew install --cask coderabbit`
+    - Other: `curl -fsSL https://cli.coderabbit.ai/install.sh | sh`
+    - Then: `coderabbit auth login`
+  - Record the preference as `coderabbit` regardless (will prompt at review time if still missing)
+
+**2g. Confirm CLAUDE.md generation:**
 - "Generate/update CLAUDE.md? This will analyze your codebase to document structure and conventions."
   - Options: "Yes (recommended)", "Skip"
 
-**2g. Confirm project-specific skills:**
+**2h. Confirm project-specific skills:**
 - Present proposed skills based on detected project type (see skill table in configure-project/SKILL.md)
 - "These project-specific skills were detected for your {project-type} project: {skill-list}. Confirm or customize?"
   - Options: "Use these (recommended)", "Customize", "Skip skill generation"
@@ -186,7 +230,7 @@ Create `.claude/.5/config.json` with the following values:
 - Test timeout: 300000ms
 - CodeRabbit: {available/not-available}, authenticated: {yes/no}
 - IDE integration: {available/not-available}, type: {type}
-- Review tool: {coderabbit/none}
+- Review tool: {claude/coderabbit/none}
 
 ### Requirement 2: Generate Documentation Files
 Analyze the codebase and generate modular documentation:

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

@@ -19,6 +19,41 @@ This skill is part of **Phase 1** (Feature Planning) of the 5-phase workflow:
 
 This skill enables **optional iterative refinement** of feature specs after initial planning through discussion, clarification, and requirement changes. Use it when the initial spec needs adjustments before proceeding to implementation planning.
 
+## ⚠️ CRITICAL SCOPE CONSTRAINT
+
+**THIS COMMAND ONLY UPDATES FEATURE SPECIFICATIONS. IT DOES NOT PLAN OR IMPLEMENT.**
+
+Your job in this command:
+✅ Read existing feature specification
+✅ Ask what user wants to discuss
+✅ Explore codebase if needed for context
+✅ Ask clarifying questions
+✅ Update feature specification
+✅ Tell user to run /5:plan-implementation
+
+Your job is NOT:
+❌ Create new feature specs (use /5:plan-feature)
+❌ Create implementation plans
+❌ Map to technical components
+❌ Start implementation
+❌ Write any code
+❌ Rewrite entire feature spec (only update changed sections)
+
+**After updating the feature spec and informing the user, YOUR JOB IS COMPLETE. EXIT IMMEDIATELY.**
+
+## ❌ Boundaries: What This Command Does NOT Do
+
+**CRITICAL:** This command has a LIMITED scope. Do NOT:
+
+- ❌ **Create new feature specs** - That's /5:plan-feature
+- ❌ **Create implementation plans** - That's Phase 2 (/5:plan-implementation)
+- ❌ **Start implementation** - That's Phase 3 (/5:implement-feature)
+- ❌ **Write any code** - This is planning only
+- ❌ **Rewrite entire spec** - Only update sections that changed
+- ❌ **Delete previous Q&A** - Append new discussions, keep history
+
+**If you find yourself creating plans or writing code, STOP IMMEDIATELY. You are exceeding this command's scope.**
+
 ## Use Cases
 
 Use this skill when:
@@ -196,15 +231,19 @@ After updating the spec, tell the developer:
 
 ## Instructions Summary
 
+Follow these steps **IN ORDER** and **STOP after step 9**:
+
 1. **Extract feature name** - From user input or by matching ticket ID
 2. **Read feature spec** - Load current state from `.5/{feature-name}/feature.md`
 3. **Ask initial question** - What do they want to discuss?
 4. **Explore if needed** - Understand codebase context
 5. **Interactive Q&A** - Multiple rounds of clarifying questions
-6. **Iterate** - Allow continued discussion
-7. **Update feature spec** - Modify relevant sections
+6. **Iterate** - Allow continued discussion until user is satisfied
+7. **Update feature spec** - Modify only the relevant sections that changed
 8. **Track changes** - Document discussion history
-9. **Inform developer** - Summarize changes and next steps
+9. **Inform developer** - Summarize changes and ask: "Discuss more or run `/clear` followed by `/5:plan-implementation {feature-name}`?"
+
+**🛑 STOP HERE. YOUR JOB IS COMPLETE. DO NOT CREATE IMPLEMENTATION PLANS.**
 
 ## Key Principles
 
@@ -216,14 +255,6 @@ After updating the spec, tell the developer:
 6. **Preserve history** - Keep previous Q&A, add new discussions
 7. **Clear next steps** - Guide user on what to do next
 
-## DO NOT in This Skill
-
-- DO NOT rewrite the entire feature spec (only update changed sections)
-- DO NOT skip asking what the user wants to discuss
-- DO NOT create new feature specs (use /plan-feature for that)
-- DO NOT proceed to technical planning (that's Phase 2's job)
-- DO NOT start implementation
-- DO NOT delete previous Q&A sections (append to them)
 
 ## Discussion Patterns