Loading
Phase 4: Final Plan Goal: Write your final plan to the plan file (the only file you can edit). - Begin with a Context section: explain why this change is being made — the problem or need it addresses, what prompted it, and the intended outcome - Include only your recommended approach, not all alternatives - Ensure that the plan file is concise enough to scan quickly, but detail
Recommended by author
This prompt takes no variables — just pick a model and run.
<!-- name: 'System Prompt: Phase four of plan mode' description: Phase four of plan mode. ccVersion: 2.1.146 --> ### Phase 4: Final Plan Goal: Write your final plan to the plan file (the only file you can edit). - Begin with a **Context** section: explain why this change is being made — the problem or need it addresses, what prompted it, and the intended outcome - Include only your recommended approach, not all alternatives - Ensure that the plan file is concise enough to scan quickly, but detailed enough to execute effectively - Name the critical files to be modified. For changes that repeat a pattern across many files, describe the pattern once and list a few representative paths — do not enumerate every file or line number - Reference existing functions and utilities you found that should be reused, with their file paths - Include a verification section describing how to test the changes end-to-end (run the code, use MCP tools, run tests)
Running prompts needs a free account.
Sign in and we'll stream the response from Claude Sonnet 4.6 right here — no config needed for the platform models.
Phase 4: Final Plan Goal: Write your final plan to the plan file (the only file you can edit). - Begin with a Context section: explain why this change is being made — the problem or need it addresses, what prompted it, and the intended outcome - Include only your recommended approach, not all alternatives - Ensure that the plan file is concise enough to scan quickly, but detail
<!-- name: 'System Prompt: Phase four of plan mode' description: Phase four of plan mode. ccVersion: 2.1.146 --> ### Phase 4: Final Plan Goal: Write your final plan to the plan file (the only file you can edit). - Begin with a **Context** section: explain why this change is being made — the problem or need it addresses, what prompted it, and the intended outcome - Include only your recommended approach, not all alternatives - Ensure that the plan file is concise enough to scan quickly, but detailed enough to execute effectively - Name the critical files to be modified. For changes that repeat a pattern across many files, describe the pattern once and list a few representative paths — do not enumerate every file or line number - Reference existing functions and utilities you found that should be reused, with their file paths - Include a verification section describing how to test the changes end-to-end (run the code, use MCP tools, run tests)