- Added Initial Context Check to Planning Phase 1 - Model now asks about additional files, reference materials, and external integrations before

analyzing requirements
- Added user verification checklist and git checkpoint to `Implementation Phase 3` - Phase completion reports now guide users through verification and git checkpointing before starting the next phase

.agent/workflows/plan2code-1--plan.md

@@ -42,6 +42,18 @@ Report each sub-score when stating your overall confidence percentage.
 
 ### PLANNING PHASE 1: Requirements Analysis
 
+**Initial Context Check:**
+
+Before analyzing requirements, ask the user:
+
+1. Are there additional files or folders I should examine? (code, configs, schemas, etc.)
+2. Any reference materials to review? (designs, mockups, wireframes, API specs, diagrams)
+3. Will this integrate with any external systems, APIs, or services I should know about?
+
+_If you cannot access files directly, ask the user to paste relevant excerpts or describe key structures._
+
+Once the user confirms there's nothing else or provides additional assets, review them and proceed with requirements analysis.
+
 1. Carefully read all provided information about the project or feature
 2. Extract and list all functional requirements explicitly stated
 3. Identify implied requirements not directly stated

.agent/workflows/plan2code-3--implement.md

@@ -196,6 +196,26 @@ When the phase is complete, provide this summary:
 
 [Any blockers, spec clarifications, or deviations - or "None"]
 
+## Verify It Yourself
+
+Before moving on, confirm this phase is working:
+
+- **Files exist**: The files listed above were created/modified
+- **No syntax errors**: Open new files in your editor - no red underlines or errors
+- **App runs** (if applicable): Start command runs without crashing
+- **Quick check**: [Describe 1-2 specific things to verify based on what was built]
+
+## Save Your Progress
+
+Before starting the next phase, commit your progress:
+
+\`\`\`bash
+git add -A
+git commit -m "Complete Phase X: [Phase Name]"
+\`\`\`
+
+This creates a checkpoint you can return to if needed.
+
 ## Next Steps
 
 The next uncompleted phase is Phase Y: [Name].
@@ -210,9 +230,11 @@ To continue, start a NEW conversation with:
 When phase implementation is complete, always tell the user:
 
 1. What was accomplished (completion summary)
-2. Files to attach in next session for the next phase
+2. How to verify the phase is working (quick checks)
-3. Reminder to start a NEW conversation
+3. How to save progress with a git commit (provide the command, do not execute it)
-4. If all phases complete: recommend proceeding to finalization
+4. Files to attach in next session for the next phase
+5. Reminder to start a NEW conversation
+6. If all phases complete: recommend proceeding to finalization
 
 Example for continuing:
 
@@ -245,5 +267,6 @@ If the user says "abort", "cancel", "start over", or similar:
 - Update checkboxes IMMEDIATELY after completing each task
 - ONE phase per conversation by default
 - Do NOT run tests unless explicitly listed as a task
+- Do NOT run git commands - provide commit instructions for the user to execute
 - Flag blockers and spec issues clearly - do not silently skip or assume
 - Your job is to BUILD according to spec, not to redesign

.claude/commands/plan2code-1--plan.md

@@ -38,6 +38,18 @@ Report each sub-score when stating your overall confidence percentage.
 
 ### PLANNING PHASE 1: Requirements Analysis
 
+**Initial Context Check:**
+
+Before analyzing requirements, ask the user:
+
+1. Are there additional files or folders I should examine? (code, configs, schemas, etc.)
+2. Any reference materials to review? (designs, mockups, wireframes, API specs, diagrams)
+3. Will this integrate with any external systems, APIs, or services I should know about?
+
+_If you cannot access files directly, ask the user to paste relevant excerpts or describe key structures._
+
+Once the user confirms there's nothing else or provides additional assets, review them and proceed with requirements analysis.
+
 1. Carefully read all provided information about the project or feature
 2. Extract and list all functional requirements explicitly stated
 3. Identify implied requirements not directly stated

.claude/commands/plan2code-3--implement.md

@@ -192,6 +192,26 @@ When the phase is complete, provide this summary:
 
 [Any blockers, spec clarifications, or deviations - or "None"]
 
+## Verify It Yourself
+
+Before moving on, confirm this phase is working:
+
+- **Files exist**: The files listed above were created/modified
+- **No syntax errors**: Open new files in your editor - no red underlines or errors
+- **App runs** (if applicable): Start command runs without crashing
+- **Quick check**: [Describe 1-2 specific things to verify based on what was built]
+
+## Save Your Progress
+
+Before starting the next phase, commit your progress:
+
+\`\`\`bash
+git add -A
+git commit -m "Complete Phase X: [Phase Name]"
+\`\`\`
+
+This creates a checkpoint you can return to if needed.
+
 ## Next Steps
 
 The next uncompleted phase is Phase Y: [Name].
@@ -206,9 +226,11 @@ To continue, start a NEW conversation with:
 When phase implementation is complete, always tell the user:
 
 1. What was accomplished (completion summary)
-2. Files to attach in next session for the next phase
+2. How to verify the phase is working (quick checks)
-3. Reminder to start a NEW conversation
+3. How to save progress with a git commit (provide the command, do not execute it)
-4. If all phases complete: recommend proceeding to finalization
+4. Files to attach in next session for the next phase
+5. Reminder to start a NEW conversation
+6. If all phases complete: recommend proceeding to finalization
 
 Example for continuing:
 
@@ -241,5 +263,6 @@ If the user says "abort", "cancel", "start over", or similar:
 - Update checkboxes IMMEDIATELY after completing each task
 - ONE phase per conversation by default
 - Do NOT run tests unless explicitly listed as a task
+- Do NOT run git commands - provide commit instructions for the user to execute
 - Flag blockers and spec issues clearly - do not silently skip or assume
 - Your job is to BUILD according to spec, not to redesign

.continue/prompts/plan2code-1--plan.prompt.md

@@ -43,6 +43,18 @@ Report each sub-score when stating your overall confidence percentage.
 
 ### PLANNING PHASE 1: Requirements Analysis
 
+**Initial Context Check:**
+
+Before analyzing requirements, ask the user:
+
+1. Are there additional files or folders I should examine? (code, configs, schemas, etc.)
+2. Any reference materials to review? (designs, mockups, wireframes, API specs, diagrams)
+3. Will this integrate with any external systems, APIs, or services I should know about?
+
+_If you cannot access files directly, ask the user to paste relevant excerpts or describe key structures._
+
+Once the user confirms there's nothing else or provides additional assets, review them and proceed with requirements analysis.
+
 1. Carefully read all provided information about the project or feature
 2. Extract and list all functional requirements explicitly stated
 3. Identify implied requirements not directly stated

.continue/prompts/plan2code-3--implement.prompt.md

@@ -197,6 +197,26 @@ When the phase is complete, provide this summary:
 
 [Any blockers, spec clarifications, or deviations - or "None"]
 
+## Verify It Yourself
+
+Before moving on, confirm this phase is working:
+
+- **Files exist**: The files listed above were created/modified
+- **No syntax errors**: Open new files in your editor - no red underlines or errors
+- **App runs** (if applicable): Start command runs without crashing
+- **Quick check**: [Describe 1-2 specific things to verify based on what was built]
+
+## Save Your Progress
+
+Before starting the next phase, commit your progress:
+
+\`\`\`bash
+git add -A
+git commit -m "Complete Phase X: [Phase Name]"
+\`\`\`
+
+This creates a checkpoint you can return to if needed.
+
 ## Next Steps
 
 The next uncompleted phase is Phase Y: [Name].
@@ -211,9 +231,11 @@ To continue, start a NEW conversation with:
 When phase implementation is complete, always tell the user:
 
 1. What was accomplished (completion summary)
-2. Files to attach in next session for the next phase
+2. How to verify the phase is working (quick checks)
-3. Reminder to start a NEW conversation
+3. How to save progress with a git commit (provide the command, do not execute it)
-4. If all phases complete: recommend proceeding to finalization
+4. Files to attach in next session for the next phase
+5. Reminder to start a NEW conversation
+6. If all phases complete: recommend proceeding to finalization
 
 Example for continuing:
 
@@ -246,5 +268,6 @@ If the user says "abort", "cancel", "start over", or similar:
 - Update checkboxes IMMEDIATELY after completing each task
 - ONE phase per conversation by default
 - Do NOT run tests unless explicitly listed as a task
+- Do NOT run git commands - provide commit instructions for the user to execute
 - Flag blockers and spec issues clearly - do not silently skip or assume
 - Your job is to BUILD according to spec, not to redesign

.cursor/rules/plan2code-1--plan.mdc

@@ -43,6 +43,18 @@ Report each sub-score when stating your overall confidence percentage.
 
 ### PLANNING PHASE 1: Requirements Analysis
 
+**Initial Context Check:**
+
+Before analyzing requirements, ask the user:
+
+1. Are there additional files or folders I should examine? (code, configs, schemas, etc.)
+2. Any reference materials to review? (designs, mockups, wireframes, API specs, diagrams)
+3. Will this integrate with any external systems, APIs, or services I should know about?
+
+_If you cannot access files directly, ask the user to paste relevant excerpts or describe key structures._
+
+Once the user confirms there's nothing else or provides additional assets, review them and proceed with requirements analysis.
+
 1. Carefully read all provided information about the project or feature
 2. Extract and list all functional requirements explicitly stated
 3. Identify implied requirements not directly stated

.cursor/rules/plan2code-3--implement.mdc

@@ -197,6 +197,26 @@ When the phase is complete, provide this summary:
 
 [Any blockers, spec clarifications, or deviations - or "None"]
 
+## Verify It Yourself
+
+Before moving on, confirm this phase is working:
+
+- **Files exist**: The files listed above were created/modified
+- **No syntax errors**: Open new files in your editor - no red underlines or errors
+- **App runs** (if applicable): Start command runs without crashing
+- **Quick check**: [Describe 1-2 specific things to verify based on what was built]
+
+## Save Your Progress
+
+Before starting the next phase, commit your progress:
+
+\`\`\`bash
+git add -A
+git commit -m "Complete Phase X: [Phase Name]"
+\`\`\`
+
+This creates a checkpoint you can return to if needed.
+
 ## Next Steps
 
 The next uncompleted phase is Phase Y: [Name].
@@ -211,9 +231,11 @@ To continue, start a NEW conversation with:
 When phase implementation is complete, always tell the user:
 
 1. What was accomplished (completion summary)
-2. Files to attach in next session for the next phase
+2. How to verify the phase is working (quick checks)
-3. Reminder to start a NEW conversation
+3. How to save progress with a git commit (provide the command, do not execute it)
-4. If all phases complete: recommend proceeding to finalization
+4. Files to attach in next session for the next phase
+5. Reminder to start a NEW conversation
+6. If all phases complete: recommend proceeding to finalization
 
 Example for continuing:
 
@@ -246,5 +268,6 @@ If the user says "abort", "cancel", "start over", or similar:
 - Update checkboxes IMMEDIATELY after completing each task
 - ONE phase per conversation by default
 - Do NOT run tests unless explicitly listed as a task
+- Do NOT run git commands - provide commit instructions for the user to execute
 - Flag blockers and spec issues clearly - do not silently skip or assume
 - Your job is to BUILD according to spec, not to redesign

.github/agents/plan2code-1--plan.agent.md

@@ -42,6 +42,18 @@ Report each sub-score when stating your overall confidence percentage.
 
 ### PLANNING PHASE 1: Requirements Analysis
 
+**Initial Context Check:**
+
+Before analyzing requirements, ask the user:
+
+1. Are there additional files or folders I should examine? (code, configs, schemas, etc.)
+2. Any reference materials to review? (designs, mockups, wireframes, API specs, diagrams)
+3. Will this integrate with any external systems, APIs, or services I should know about?
+
+_If you cannot access files directly, ask the user to paste relevant excerpts or describe key structures._
+
+Once the user confirms there's nothing else or provides additional assets, review them and proceed with requirements analysis.
+
 1. Carefully read all provided information about the project or feature
 2. Extract and list all functional requirements explicitly stated
 3. Identify implied requirements not directly stated

.github/agents/plan2code-3--implement.agent.md

@@ -196,6 +196,26 @@ When the phase is complete, provide this summary:
 
 [Any blockers, spec clarifications, or deviations - or "None"]
 
+## Verify It Yourself
+
+Before moving on, confirm this phase is working:
+
+- **Files exist**: The files listed above were created/modified
+- **No syntax errors**: Open new files in your editor - no red underlines or errors
+- **App runs** (if applicable): Start command runs without crashing
+- **Quick check**: [Describe 1-2 specific things to verify based on what was built]
+
+## Save Your Progress
+
+Before starting the next phase, commit your progress:
+
+\`\`\`bash
+git add -A
+git commit -m "Complete Phase X: [Phase Name]"
+\`\`\`
+
+This creates a checkpoint you can return to if needed.
+
 ## Next Steps
 
 The next uncompleted phase is Phase Y: [Name].
@@ -210,9 +230,11 @@ To continue, start a NEW conversation with:
 When phase implementation is complete, always tell the user:
 
 1. What was accomplished (completion summary)
-2. Files to attach in next session for the next phase
+2. How to verify the phase is working (quick checks)
-3. Reminder to start a NEW conversation
+3. How to save progress with a git commit (provide the command, do not execute it)
-4. If all phases complete: recommend proceeding to finalization
+4. Files to attach in next session for the next phase
+5. Reminder to start a NEW conversation
+6. If all phases complete: recommend proceeding to finalization
 
 Example for continuing:
 
@@ -245,5 +267,6 @@ If the user says "abort", "cancel", "start over", or similar:
 - Update checkboxes IMMEDIATELY after completing each task
 - ONE phase per conversation by default
 - Do NOT run tests unless explicitly listed as a task
+- Do NOT run git commands - provide commit instructions for the user to execute
 - Flag blockers and spec issues clearly - do not silently skip or assume
 - Your job is to BUILD according to spec, not to redesign

.github/prompts/plan2code-1--plan.prompt.md

@@ -43,6 +43,18 @@ Report each sub-score when stating your overall confidence percentage.
 
 ### PLANNING PHASE 1: Requirements Analysis
 
+**Initial Context Check:**
+
+Before analyzing requirements, ask the user:
+
+1. Are there additional files or folders I should examine? (code, configs, schemas, etc.)
+2. Any reference materials to review? (designs, mockups, wireframes, API specs, diagrams)
+3. Will this integrate with any external systems, APIs, or services I should know about?
+
+_If you cannot access files directly, ask the user to paste relevant excerpts or describe key structures._
+
+Once the user confirms there's nothing else or provides additional assets, review them and proceed with requirements analysis.
+
 1. Carefully read all provided information about the project or feature
 2. Extract and list all functional requirements explicitly stated
 3. Identify implied requirements not directly stated

.github/prompts/plan2code-3--implement.prompt.md

@@ -197,6 +197,26 @@ When the phase is complete, provide this summary:
 
 [Any blockers, spec clarifications, or deviations - or "None"]
 
+## Verify It Yourself
+
+Before moving on, confirm this phase is working:
+
+- **Files exist**: The files listed above were created/modified
+- **No syntax errors**: Open new files in your editor - no red underlines or errors
+- **App runs** (if applicable): Start command runs without crashing
+- **Quick check**: [Describe 1-2 specific things to verify based on what was built]
+
+## Save Your Progress
+
+Before starting the next phase, commit your progress:
+
+\`\`\`bash
+git add -A
+git commit -m "Complete Phase X: [Phase Name]"
+\`\`\`
+
+This creates a checkpoint you can return to if needed.
+
 ## Next Steps
 
 The next uncompleted phase is Phase Y: [Name].
@@ -211,9 +231,11 @@ To continue, start a NEW conversation with:
 When phase implementation is complete, always tell the user:
 
 1. What was accomplished (completion summary)
-2. Files to attach in next session for the next phase
+2. How to verify the phase is working (quick checks)
-3. Reminder to start a NEW conversation
+3. How to save progress with a git commit (provide the command, do not execute it)
-4. If all phases complete: recommend proceeding to finalization
+4. Files to attach in next session for the next phase
+5. Reminder to start a NEW conversation
+6. If all phases complete: recommend proceeding to finalization
 
 Example for continuing:
 
@@ -246,5 +268,6 @@ If the user says "abort", "cancel", "start over", or similar:
 - Update checkboxes IMMEDIATELY after completing each task
 - ONE phase per conversation by default
 - Do NOT run tests unless explicitly listed as a task
+- Do NOT run git commands - provide commit instructions for the user to execute
 - Flag blockers and spec issues clearly - do not silently skip or assume
 - Your job is to BUILD according to spec, not to redesign

.windsurf/workflows/plan2code-1--plan.md

@@ -42,6 +42,18 @@ Report each sub-score when stating your overall confidence percentage.
 
 ### PLANNING PHASE 1: Requirements Analysis
 
+**Initial Context Check:**
+
+Before analyzing requirements, ask the user:
+
+1. Are there additional files or folders I should examine? (code, configs, schemas, etc.)
+2. Any reference materials to review? (designs, mockups, wireframes, API specs, diagrams)
+3. Will this integrate with any external systems, APIs, or services I should know about?
+
+_If you cannot access files directly, ask the user to paste relevant excerpts or describe key structures._
+
+Once the user confirms there's nothing else or provides additional assets, review them and proceed with requirements analysis.
+
 1. Carefully read all provided information about the project or feature
 2. Extract and list all functional requirements explicitly stated
 3. Identify implied requirements not directly stated

.windsurf/workflows/plan2code-3--implement.md

@@ -196,6 +196,26 @@ When the phase is complete, provide this summary:
 
 [Any blockers, spec clarifications, or deviations - or "None"]
 
+## Verify It Yourself
+
+Before moving on, confirm this phase is working:
+
+- **Files exist**: The files listed above were created/modified
+- **No syntax errors**: Open new files in your editor - no red underlines or errors
+- **App runs** (if applicable): Start command runs without crashing
+- **Quick check**: [Describe 1-2 specific things to verify based on what was built]
+
+## Save Your Progress
+
+Before starting the next phase, commit your progress:
+
+\`\`\`bash
+git add -A
+git commit -m "Complete Phase X: [Phase Name]"
+\`\`\`
+
+This creates a checkpoint you can return to if needed.
+
 ## Next Steps
 
 The next uncompleted phase is Phase Y: [Name].
@@ -210,9 +230,11 @@ To continue, start a NEW conversation with:
 When phase implementation is complete, always tell the user:
 
 1. What was accomplished (completion summary)
-2. Files to attach in next session for the next phase
+2. How to verify the phase is working (quick checks)
-3. Reminder to start a NEW conversation
+3. How to save progress with a git commit (provide the command, do not execute it)
-4. If all phases complete: recommend proceeding to finalization
+4. Files to attach in next session for the next phase
+5. Reminder to start a NEW conversation
+6. If all phases complete: recommend proceeding to finalization
 
 Example for continuing:
 
@@ -245,5 +267,6 @@ If the user says "abort", "cancel", "start over", or similar:
 - Update checkboxes IMMEDIATELY after completing each task
 - ONE phase per conversation by default
 - Do NOT run tests unless explicitly listed as a task
+- Do NOT run git commands - provide commit instructions for the user to execute
 - Flag blockers and spec issues clearly - do not silently skip or assume
 - Your job is to BUILD according to spec, not to redesign

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 All notable changes to Plan2Code will be documented in this file.
 
+## v1.0.1 - 2025-12-05
+
+### 📦 Updated
+
+- Added Initial Context Check to `Planning Phase 1` - Model now asks about additional files, reference materials, and external integrations before
+  analyzing requirements
+- Added user verification checklist and git checkpoint to `Implementation Phase 3` - Phase completion reports now guide users through verification and git checkpointing before starting the next phase
+
 ## v1.0.0 - 2025-12-04
 
 ### ✨ Added

plan2code-1--plan.md

@@ -38,6 +38,18 @@ Report each sub-score when stating your overall confidence percentage.
 
 ### PLANNING PHASE 1: Requirements Analysis
 
+**Initial Context Check:**
+
+Before analyzing requirements, ask the user:
+
+1. Are there additional files or folders I should examine? (code, configs, schemas, etc.)
+2. Any reference materials to review? (designs, mockups, wireframes, API specs, diagrams)
+3. Will this integrate with any external systems, APIs, or services I should know about?
+
+_If you cannot access files directly, ask the user to paste relevant excerpts or describe key structures._
+
+Once the user confirms there's nothing else or provides additional assets, review them and proceed with requirements analysis.
+
 1. Carefully read all provided information about the project or feature
 2. Extract and list all functional requirements explicitly stated
 3. Identify implied requirements not directly stated

plan2code-3--implement.md

@@ -192,6 +192,26 @@ When the phase is complete, provide this summary:
 
 [Any blockers, spec clarifications, or deviations - or "None"]
 
+## Verify It Yourself
+
+Before moving on, confirm this phase is working:
+
+- **Files exist**: The files listed above were created/modified
+- **No syntax errors**: Open new files in your editor - no red underlines or errors
+- **App runs** (if applicable): Start command runs without crashing
+- **Quick check**: [Describe 1-2 specific things to verify based on what was built]
+
+## Save Your Progress
+
+Before starting the next phase, commit your progress:
+
+\`\`\`bash
+git add -A
+git commit -m "Complete Phase X: [Phase Name]"
+\`\`\`
+
+This creates a checkpoint you can return to if needed.
+
 ## Next Steps
 
 The next uncompleted phase is Phase Y: [Name].
@@ -206,9 +226,11 @@ To continue, start a NEW conversation with:
 When phase implementation is complete, always tell the user:
 
 1. What was accomplished (completion summary)
-2. Files to attach in next session for the next phase
+2. How to verify the phase is working (quick checks)
-3. Reminder to start a NEW conversation
+3. How to save progress with a git commit (provide the command, do not execute it)
-4. If all phases complete: recommend proceeding to finalization
+4. Files to attach in next session for the next phase
+5. Reminder to start a NEW conversation
+6. If all phases complete: recommend proceeding to finalization
 
 Example for continuing:
 
@@ -241,5 +263,6 @@ If the user says "abort", "cancel", "start over", or similar:
 - Update checkboxes IMMEDIATELY after completing each task
 - ONE phase per conversation by default
 - Do NOT run tests unless explicitly listed as a task
+- Do NOT run git commands - provide commit instructions for the user to execute
 - Flag blockers and spec issues clearly - do not silently skip or assume
 - Your job is to BUILD according to spec, not to redesign