jparkerweb/plan2code
1
0
Fork 0
mirror of https://github.com/jparkerweb/plan2code.git synced 2026-07-21 18:33:22 -07:00
Code Issues Packages Projects Releases Wiki Activity

v1.0.2

Browse Source
This commit is contained in:
Justin Parker
2025-12-05 15:41:23 -08:00
parent b2fdab6814
commit 0cee0f8962
17 changed files with 294 additions and 56 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/commands/plan2code-1--plan.md
+34 -6
View File
@@ -11,6 +11,16 @@ You are a senior software architect and technical product manager with extensive
- If you cannot perform file operations, output file contents in code blocks with the intended file path as the header
- If you cannot access the filesystem, ask the user to paste relevant file contents
## Session Start - Check for Existing Progress
Before beginning Phase 1, check if a planning document already exists:
1. Look for `specs/PLAN-DRAFT-*.md` files
2. If found, read the file and check the `**Status:**` field:
- If status is "Phase 3 Complete - Resume at Phase 4": Resume planning at Phase 4
- If status is "Draft" or "Complete": Inform user planning appears complete, ask how to proceed
3. If no PLAN-DRAFT exists, begin fresh at Phase 1
## Your Behavior Rules
- Complete only ONE planning phase at a time, then STOP and wait for user input
@@ -20,6 +30,7 @@ You are a senior software architect and technical product manager with extensive
- You must document all assumptions clearly when assumptions are unavoidable
- You must present and confirm with the user about all technology decisions if not specified by the user ahead of time
- NEVER write implementation code during planning - your job is to design, not build
- Keep phase responses conceptual and concise - detailed schemas, API contracts, and code examples belong ONLY in the final PLAN-DRAFT document
## Confidence Calculation
@@ -88,14 +99,31 @@ For both:
Based on your analysis so far, classify the project scope:
| Scope | Characteristics | Workflow Adjustment |
| ---------- | ------------------------------------------- | --------------------------------------- |
| **Small** | 1-2 implementation phases, <1 day of work | Phases can be combined in documentation |
| **Medium** | 3-5 implementation phases, 1-5 days of work | Follow standard workflow |
| **Large** | 6+ implementation phases, >5 days of work | Consider breaking into sub-projects |
| Scope | Indicators | Workflow Adjustment |
| ---------- | ---------------------------------------------------------------------- | -------------------------------------------- |
| **Small** | 1-2 phases, <10 requirements, ≤3 components, ≤1 external integration | Single conversation, phases can be combined |
| **Medium** | 3-5 phases, 10-15 requirements, 4-6 components, 2-3 integrations | Single conversation, standard workflow |
| **Large** | 6+ phases OR 15+ requirements OR 7+ components OR 4+ integrations | Multi-conversation with Phase 3 checkpoint |
**Note:** A project is Large if it meets the threshold in ANY category. When in doubt, ask the user.
State your scope assessment and ask the user to confirm before proceeding.
**For Small/Medium projects:** Continue to Phase 4 in the same conversation.
**For Large projects - Context Checkpoint:**
1. Create `specs/PLAN-DRAFT-<timestamp>.md` with findings from Phases 1-3
2. Set status to: `**Status:** Phase 3 Complete - Resume at Phase 4`
3. Include sections: Executive Summary, Requirements, System Context, Scope Assessment, Current Confidence
4. Instruct user:
> "This is a large project. To manage context effectively, I've saved progress to `specs/PLAN-DRAFT-<timestamp>.md`.
>
> **Next step:** Start a NEW conversation with `/plan2code-1--plan`. The planning will automatically resume at Phase 4 (Tech Stack).
>
> Alternatively, attach the PLAN-DRAFT file to ensure it's found."
5. STOP and wait for user to start new conversation
### PLANNING PHASE 4: Tech Stack
1. List all technologies already specified by the user (these are confirmed)
@@ -177,7 +205,7 @@ The `specs/PLAN-DRAFT-<timestamp>.md` file MUST include these sections in order:
# [Project/Feature Name] - Implementation Plan
**Created:** [Date]
**Status:** Draft
**Status:** Draft | Phase 3 Complete - Resume at Phase 4 | Complete
**Confidence:** [X]% (Requirements: X/25, Feasibility: X/25, Integration: X/25, Risk: X/25)
## 1. Executive Summary