5-phase-workflow 1.1.1 → 1.2.0

package/src/commands/5/quick-implement.md

@@ -10,6 +10,43 @@ user-invocable: true
 
 Fast path for small, well-understood tasks (1-5 files). Skips extensive planning phases but preserves state tracking and skill-based implementation.
 
+## ⚠️ CRITICAL SCOPE CONSTRAINT
+
+**THIS COMMAND IS FOR SMALL, FOCUSED TASKS ONLY (1-5 FILES).**
+
+Your job in this command:
+✅ Get task description
+✅ Extract ticket ID
+✅ Create quick plan (max 5 components)
+✅ Get user approval on plan
+✅ Initialize state tracking
+✅ Execute implementation
+✅ Run verification
+✅ Report completion
+
+Your job is NOT:
+❌ Handle complex features (6+ files)
+❌ Work across multiple domains
+❌ Skip clarifying questions if unclear
+❌ Skip state file updates
+❌ Create feature spec files (use full workflow)
+❌ Commit changes (user handles this)
+
+**This is a FAST PATH for well-understood, small tasks. For anything complex, use the full workflow.**
+
+## ❌ Boundaries: What This Command Does NOT Do
+
+**CRITICAL:** This command has a LIMITED scope. Do NOT:
+
+- ❌ **Use for complex features** - 6+ files or multiple domains → use full workflow
+- ❌ **Skip clarifying questions** - If implementation is unclear, ask first
+- ❌ **Skip state updates** - State file updates are MANDATORY
+- ❌ **Create feature specs** - This is for quick tasks, not full features
+- ❌ **Auto-commit** - User handles commits
+- ❌ **Skip plan approval** - Always show plan and get user approval first
+
+**If the task involves more than 5 files or multiple domains, STOP and recommend the full workflow instead.**
+
 ## Process
 
 ### Step 1: Get Task Description
@@ -49,27 +86,16 @@ feature_name="${TICKET_ID}-${slug}"
 
 ### Step 5: Create Plan
 
-Write plan to `.5/${feature_name}/plan.md`:
-
-```markdown
-# Quick Implementation: ${TICKET_ID}
+Write plan to `.5/${feature_name}/plan.md` using the template structure.
 
-## Task
-${DESCRIPTION}
+**Template Reference:** Use the structure from `.claude/templates/workflow/QUICK-PLAN.md`
 
-## Components
-
-| # | Type | Name | Skill | Module |
-|---|------|------|-------|--------|
-| 1 | {type} | {name} | {skill} | {module} |
-
-## Affected Modules
-- {module-1}
-- {module-2}
-
-## Execution
-{parallel | sequential | direct}
-```
+The template contains placeholders for:
+- **Header:** `# Quick Implementation: {TICKET-ID}`
+- **Task:** The task description
+- **Components table:** Columns for #, Type, Name, Skill, Module
+- **Affected Modules:** List of modules that will be modified
+- **Execution:** Mode (parallel, sequential, or direct)
 
 ### Step 6: Present Plan and Iterate
 
@@ -147,24 +173,44 @@ For each component:
 
 #### Step-Executor Delegation
 
-Read `.claude/agents/step-executor.md` and spawn:
+Spawn an agent with inline instructions:
 
 ```
 Task tool call:
-  subagent_type: step-executor
+  subagent_type: general-purpose
+  model: haiku
   description: "Execute quick implementation for ${feature_name}"
   prompt: |
-    {Contents of step-executor.md}
+    Implement components for a feature by finding patterns in existing code.
+
+    ## Feature
+    ${feature_name}
 
-    ---
+    ## Components
+    {component list from plan}
 
-    ## Your Task
+    ## Process
+    For each component:
 
-    Feature: ${feature_name}
-    Components:
-    {component list from plan with full skill prompts}
+    **If creating a new file:**
+    1. Find a similar file using Glob (e.g., *Service.ts for services)
+    2. Read it to understand the pattern (imports, structure, exports)
+    3. Create the new file following that pattern
+    4. Verify the file exists
 
-    Execution mode: {parallel | sequential}
+    **If modifying a file:**
+    1. Read the file
+    2. Make the described change using Edit tool
+    3. Verify the change
+
+    ## Output
+    Report what you created/modified:
+    - {path}: {brief description}
+
+    ## Rules
+    - Find patterns from existing code, don't invent conventions
+    - Don't skip components - attempt all
+    - Don't interact with user - just execute and report
 ```
 
 Process results and **update state file** (MANDATORY):
@@ -224,7 +270,7 @@ Skill tool call:
 Report to user:
 
 ```
-Quick implementation complete!
+✅ Quick implementation complete!
 
 ${TICKET_ID}: ${DESCRIPTION}
 
@@ -238,10 +284,12 @@ Tests: {Success | Skipped}
 State: .5/${feature_name}/state.json
 
 Next steps:
-- Review and commit changes
-- For a new task, run `/clear` before starting
+1. Review and commit changes
+2. For a new task, run `/clear` before starting
 ```
 
+**🛑 YOUR JOB IS COMPLETE. DO NOT START NEW TASKS.**
+
 ## Skill Mappings
 
 Skills are project-specific and should be configured in your project's `.claude/skills/` directory. Common patterns include:
@@ -256,12 +304,3 @@ Skills are project-specific and should be configured in your project's `.claude/
 | Tests | Project-specific test skill |
 | Simple edits | Edit tool directly |
 
-## DO NOT
-
-- DO NOT use for complex features (6+ files, multiple domains)
-- DO NOT skip clarifying questions if implementation is unclear
-- **DO NOT skip state file updates** (breaks resumability)
-- **DO NOT skip state file initialization** (Step 7 is mandatory)
-- **DO NOT skip state file completion update** (Step 10 is mandatory)
-- DO NOT create feature spec files (use full workflow for that)
-- DO NOT commit changes (user handles this)