Initial commit

commands/write-plan.md

@@ -0,0 +1,157 @@
+---
+description: Create plan and tasklist from planning discussion
+---
+
+# Plan Command
+
+Formalize the planning discussion from plan mode into structured documentation. This command is run AFTER iterating with Claude in plan mode. The user has already discussed and refined the approach. Your job is to capture and formalize what was discussed.
+
+Assume the engineer using the plan has zero context for the codebase. Document everything they need: which files to touch, code/testing/docs to check, how to test. Assume they are skilled but know little about the toolset or problem domain.
+
+## Arguments
+
+**Input**: `$ARGUMENTS`
+
+**Expected format**: `/write-plan {feature-name} [planning context]`
+
+**Parsing:**
+
+- First token: feature name
+- Remaining tokens: optional planning guidance or focus areas
+  - Example: `user-auth focus on OAuth2 and session management`
+
+**Feature name requirements:**
+
+- Format: kebab-case (lowercase with hyphens)
+- Length: 1-3 words, concise and descriptive
+- Characters: lowercase letters, numbers, hyphens only
+- Examples: `query-command`, `user-auth`, `auth`, `export`
+- Avoid: special characters, uppercase, underscores
+
+**If no feature name provided:**
+
+- Analyze conversation to suggest an appropriate feature name based on discussion
+- Present suggestion: "Based on our discussion, I suggest the feature name: '{suggested-name}'"
+- Ask user to confirm before creating files
+
+**Feature name usage:**
+`{feature-name}` is a placeholder that gets replaced with the extracted feature name throughout this command.
+
+Example file paths:
+
+- `plans/{feature-name}-plan.md`
+- `plans/{feature-name}-tasklist.md`
+
+## Instructions
+
+### 1. Extract Planning Context
+
+1. If skill `read-constitution` not loaded, load it
+2. If skill `claude-workflow` not loaded, load it
+
+Read the following if not already loaded:
+
+- `references/plan-spec.md`
+- `references/tasklist-spec.md`
+
+**Context Extraction:**
+
+Analyze the conversation to extract:
+
+- Requirements and scope (IN/OUT)
+- Design decisions with rationale (WHY)
+- Alternatives considered and rejected
+- Technical constraints and dependencies
+- File and component structure
+
+Review as much of the conversation as necessary to capture all planning context. Focus particularly on recent messages and any structured outputs (e.g., /brainstorm results, design summaries, input arguments to this command).
+
+**Complexity Assessment:**
+
+Assess feature complexity (Simple/Medium/Complex) using these criteria:
+
+**Simple:**
+
+- 1-2 files affected
+- Single component or module
+- <5 tasks total
+- Minimal external dependencies
+- Focus on MUST requirements from specs
+
+**Medium:**
+
+- 3-5 files affected
+- 2-3 components involved
+- 5-15 tasks total
+- Some cross-component integration
+- Include MUST + SHOULD requirements
+
+**Complex:**
+
+- 6+ files affected
+- 4+ components involved
+- 15+ tasks total
+- Significant architectural changes or cross-system integration
+- Include MUST + SHOULD + MAY requirements
+
+---
+
+### 2. Create Planning Documents
+
+Create `plans/{feature-name}-plan.md`:
+
+- Follow plan-spec.md structure, tailoring depth to feature complexity
+- Use extracted context from Section 1
+
+Create `plans/{feature-name}-tasklist.md`:
+
+- Follow tasklist-spec.md structure, tailoring depth to feature complexity
+- Break into phases aligned with plan's Implementation Strategy
+- Include checkpoints per SKILL.md guidance
+- Stay faithful to discussion, use clear language
+
+---
+
+### 3. Validate Documents
+
+**Validate plan**:
+
+- [ ] Plan validated against all MUST/SHOULD requirements in plan-spec.md
+- [ ] If validation fails: revise plan and re-validate until all requirements pass
+
+**Validate tasklist**:
+
+- [ ] Tasklist validated against all MUST/SHOULD requirements in tasklist-spec.md
+- [ ] If validation fails: revise tasklist and re-validate until all requirements pass
+
+**Validate coherence** between documents:
+
+- [ ] Tasklist execution follows plan's Implementation Strategy pattern
+- [ ] Tasklist execution follows plan's Testing approach
+- [ ] Files marked [CREATE]/[MODIFY] in plan appear as tasks in tasklist
+- [ ] Consistent terminology between documentsss
+- [ ] Tasks reference only files/components defined in plan
+- [ ] If coherence fails: revise either document and re-validate until all checks pass
+
+---
+
+### 4. Finalization
+
+Confirm both files exist and are valid, then present summary:
+
+```text
+Planning documents created successfully! ✅
+
+Created:
+- plans/{feature-name}-plan.md
+- plans/{feature-name}-tasklist.md
+
+Implementation Structure:
+- {N} phases defined
+- {M} total tasks
+
+Next Steps:
+Run `/implement-plan {feature-name}` to begin phase-by-phase implementation.
+```
+
+Done. Wait for user to run `/implement-plan {feature-name}`.