From 0cee0f896228ec306b7c14ffa7ee8b033a0ca03c Mon Sep 17 00:00:00 2001 From: Justin Parker Date: Fri, 5 Dec 2025 15:41:23 -0800 Subject: [PATCH] v1.0.2 --- .agent/workflows/plan2code-1--plan.md | 40 ++++++++++++++++--- .agent/workflows/plan2code-2--document.md | 2 +- .claude/commands/plan2code-1--plan.md | 40 ++++++++++++++++--- .claude/commands/plan2code-2--document.md | 2 +- .continue/prompts/plan2code-1--plan.prompt.md | 40 ++++++++++++++++--- .../prompts/plan2code-2--document.prompt.md | 2 +- .cursor/rules/plan2code-1--plan.mdc | 40 ++++++++++++++++--- .cursor/rules/plan2code-2--document.mdc | 2 +- .github/agents/plan2code-1--plan.agent.md | 40 ++++++++++++++++--- .github/agents/plan2code-2--document.agent.md | 2 +- .github/prompts/plan2code-1--plan.prompt.md | 40 ++++++++++++++++--- .../prompts/plan2code-2--document.prompt.md | 2 +- .windsurf/workflows/plan2code-1--plan.md | 40 ++++++++++++++++--- .windsurf/workflows/plan2code-2--document.md | 2 +- CHANGELOG.md | 14 +++++++ plan2code-1--plan.md | 40 ++++++++++++++++--- plan2code-2--document.md | 2 +- 17 files changed, 294 insertions(+), 56 deletions(-) diff --git a/.agent/workflows/plan2code-1--plan.md b/.agent/workflows/plan2code-1--plan.md index d9fc060..82a917e 100644 --- a/.agent/workflows/plan2code-1--plan.md +++ b/.agent/workflows/plan2code-1--plan.md @@ -15,6 +15,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 @@ -24,6 +34,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 @@ -92,14 +103,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-.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-.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) @@ -181,7 +209,7 @@ The `specs/PLAN-DRAFT-.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 diff --git a/.agent/workflows/plan2code-2--document.md b/.agent/workflows/plan2code-2--document.md index 28aec0a..51f615a 100644 --- a/.agent/workflows/plan2code-2--document.md +++ b/.agent/workflows/plan2code-2--document.md @@ -157,7 +157,7 @@ Each task should be: ## Prerequisites -- [x] Phase X-1 must be complete (if applicable) +- [ ] Phase X-1 must be complete (if applicable) - [ ] [Any other prerequisites: env vars set, services running, etc.] ## Tasks diff --git a/.claude/commands/plan2code-1--plan.md b/.claude/commands/plan2code-1--plan.md index 323ed56..c4322da 100644 --- a/.claude/commands/plan2code-1--plan.md +++ b/.claude/commands/plan2code-1--plan.md @@ -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-.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-.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-.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 diff --git a/.claude/commands/plan2code-2--document.md b/.claude/commands/plan2code-2--document.md index 7c6586e..a81090e 100644 --- a/.claude/commands/plan2code-2--document.md +++ b/.claude/commands/plan2code-2--document.md @@ -153,7 +153,7 @@ Each task should be: ## Prerequisites -- [x] Phase X-1 must be complete (if applicable) +- [ ] Phase X-1 must be complete (if applicable) - [ ] [Any other prerequisites: env vars set, services running, etc.] ## Tasks diff --git a/.continue/prompts/plan2code-1--plan.prompt.md b/.continue/prompts/plan2code-1--plan.prompt.md index 32ba1b2..93127e1 100644 --- a/.continue/prompts/plan2code-1--plan.prompt.md +++ b/.continue/prompts/plan2code-1--plan.prompt.md @@ -16,6 +16,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 @@ -25,6 +35,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 @@ -93,14 +104,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-.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-.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) @@ -182,7 +210,7 @@ The `specs/PLAN-DRAFT-.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 diff --git a/.continue/prompts/plan2code-2--document.prompt.md b/.continue/prompts/plan2code-2--document.prompt.md index 9910a90..f9e168a 100644 --- a/.continue/prompts/plan2code-2--document.prompt.md +++ b/.continue/prompts/plan2code-2--document.prompt.md @@ -158,7 +158,7 @@ Each task should be: ## Prerequisites -- [x] Phase X-1 must be complete (if applicable) +- [ ] Phase X-1 must be complete (if applicable) - [ ] [Any other prerequisites: env vars set, services running, etc.] ## Tasks diff --git a/.cursor/rules/plan2code-1--plan.mdc b/.cursor/rules/plan2code-1--plan.mdc index 3cfdfed..14d11a1 100644 --- a/.cursor/rules/plan2code-1--plan.mdc +++ b/.cursor/rules/plan2code-1--plan.mdc @@ -16,6 +16,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 @@ -25,6 +35,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 @@ -93,14 +104,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-.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-.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) @@ -182,7 +210,7 @@ The `specs/PLAN-DRAFT-.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 diff --git a/.cursor/rules/plan2code-2--document.mdc b/.cursor/rules/plan2code-2--document.mdc index 90832b7..3151ccb 100644 --- a/.cursor/rules/plan2code-2--document.mdc +++ b/.cursor/rules/plan2code-2--document.mdc @@ -158,7 +158,7 @@ Each task should be: ## Prerequisites -- [x] Phase X-1 must be complete (if applicable) +- [ ] Phase X-1 must be complete (if applicable) - [ ] [Any other prerequisites: env vars set, services running, etc.] ## Tasks diff --git a/.github/agents/plan2code-1--plan.agent.md b/.github/agents/plan2code-1--plan.agent.md index d9fc060..82a917e 100644 --- a/.github/agents/plan2code-1--plan.agent.md +++ b/.github/agents/plan2code-1--plan.agent.md @@ -15,6 +15,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 @@ -24,6 +34,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 @@ -92,14 +103,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-.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-.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) @@ -181,7 +209,7 @@ The `specs/PLAN-DRAFT-.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 diff --git a/.github/agents/plan2code-2--document.agent.md b/.github/agents/plan2code-2--document.agent.md index 28aec0a..51f615a 100644 --- a/.github/agents/plan2code-2--document.agent.md +++ b/.github/agents/plan2code-2--document.agent.md @@ -157,7 +157,7 @@ Each task should be: ## Prerequisites -- [x] Phase X-1 must be complete (if applicable) +- [ ] Phase X-1 must be complete (if applicable) - [ ] [Any other prerequisites: env vars set, services running, etc.] ## Tasks diff --git a/.github/prompts/plan2code-1--plan.prompt.md b/.github/prompts/plan2code-1--plan.prompt.md index 065b111..bdbf182 100644 --- a/.github/prompts/plan2code-1--plan.prompt.md +++ b/.github/prompts/plan2code-1--plan.prompt.md @@ -16,6 +16,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 @@ -25,6 +35,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 @@ -93,14 +104,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-.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-.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) @@ -182,7 +210,7 @@ The `specs/PLAN-DRAFT-.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 diff --git a/.github/prompts/plan2code-2--document.prompt.md b/.github/prompts/plan2code-2--document.prompt.md index 29785e0..6c58278 100644 --- a/.github/prompts/plan2code-2--document.prompt.md +++ b/.github/prompts/plan2code-2--document.prompt.md @@ -158,7 +158,7 @@ Each task should be: ## Prerequisites -- [x] Phase X-1 must be complete (if applicable) +- [ ] Phase X-1 must be complete (if applicable) - [ ] [Any other prerequisites: env vars set, services running, etc.] ## Tasks diff --git a/.windsurf/workflows/plan2code-1--plan.md b/.windsurf/workflows/plan2code-1--plan.md index d9fc060..82a917e 100644 --- a/.windsurf/workflows/plan2code-1--plan.md +++ b/.windsurf/workflows/plan2code-1--plan.md @@ -15,6 +15,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 @@ -24,6 +34,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 @@ -92,14 +103,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-.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-.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) @@ -181,7 +209,7 @@ The `specs/PLAN-DRAFT-.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 diff --git a/.windsurf/workflows/plan2code-2--document.md b/.windsurf/workflows/plan2code-2--document.md index 28aec0a..51f615a 100644 --- a/.windsurf/workflows/plan2code-2--document.md +++ b/.windsurf/workflows/plan2code-2--document.md @@ -157,7 +157,7 @@ Each task should be: ## Prerequisites -- [x] Phase X-1 must be complete (if applicable) +- [ ] Phase X-1 must be complete (if applicable) - [ ] [Any other prerequisites: env vars set, services running, etc.] ## Tasks diff --git a/CHANGELOG.md b/CHANGELOG.md index 139de8a..5d9b49a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,20 @@ All notable changes to Plan2Code will be documented in this file. +## v1.0.2 - 2025-12-05 + +### 🐛 Fixed + +- Fixed pre-checked prerequisite checkbox in Phase template (`[x]` → `[ ]`) - generated phase documents no longer appear with prerequisites already complete + +### 📦 Updated + +- Added Session Start logic to Planning Mode - automatically detects and resumes from existing `PLAN-DRAFT-*.md` files +- Replaced vague scope indicators with measurable criteria (phases, requirements, components, integrations) +- Added Large Project checkpoint workflow - projects meeting Large thresholds now checkpoint at Phase 3 and resume in a new conversation +- Added output economy rule - keeps phase responses concise, reserving detailed schemas/APIs for final PLAN-DRAFT +- Updated PLAN-DRAFT template with new status options: `Draft | Phase 3 Complete - Resume at Phase 4 | Complete` + ## v1.0.1 - 2025-12-05 ### 📦 Updated diff --git a/plan2code-1--plan.md b/plan2code-1--plan.md index 323ed56..c4322da 100644 --- a/plan2code-1--plan.md +++ b/plan2code-1--plan.md @@ -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-.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-.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-.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 diff --git a/plan2code-2--document.md b/plan2code-2--document.md index 7c6586e..a81090e 100644 --- a/plan2code-2--document.md +++ b/plan2code-2--document.md @@ -153,7 +153,7 @@ Each task should be: ## Prerequisites -- [x] Phase X-1 must be complete (if applicable) +- [ ] Phase X-1 must be complete (if applicable) - [ ] [Any other prerequisites: env vars set, services running, etc.] ## Tasks