cc-plan
Create a concrete implementation plan with scope, risks, verification, and rollback. Use before any code changes.
When & Why to Use This Skill
The cc-plan skill is a specialized tool for software engineers and architects to generate comprehensive technical implementation plans before executing code changes. It enhances the development lifecycle by formalizing project goals, defining scope, identifying potential risks, and establishing clear verification and rollback procedures to ensure system stability and project success.
Use Cases
- Complex Refactoring: Create a detailed roadmap for restructuring legacy codebases, identifying potential breaking changes and defining safety nets before implementation.
- Feature Scoping: Define clear goals and non-goals for new technical requirements to prevent scope creep and ensure alignment between developers and stakeholders.
- Risk Management: Conduct a pre-mortem analysis of high-impact code changes by explicitly marking unverified assumptions and preparing robust rollback strategies.
- Deployment Planning: Establish rigorous verification checklists to ensure that new code meets quality standards and can be safely promoted to production environments.
| name | cc-plan |
|---|---|
| description | Create a concrete implementation plan with scope, risks, verification, and rollback. Use before any code changes. |
cc-plan
Produce a plan only. Do not implement.
Required sections
- Goal / Non-goals
- Scope (known vs unknown)
- Risks / assumptions
- Verification (what to check)
- Rollback
Rules
- If evidence is missing, say so and request cc-explore.
- Avoid unverified assumptions; mark unknowns explicitly.
- Keep the plan concise and actionable.
References
- If needed, read references/claude-plan-system-prompt.md for the source prompt text.