Help us improve
Share bugs, ideas, or general feedback.
From r-skills
Creates an implementation plan before writing code for new features, architectural changes, or complex refactoring, including steps, risks, testing, and success criteria.
npx claudepluginhub ab604/claude-code-r-skills --plugin r-skillsHow this command is triggered — by the user, by Claude, or both
Slash command
/r-skills:planThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /plan - Implementation Planning Use the planner agent to create a comprehensive implementation plan before writing any code. ## When to Use - New features or functionality - Architectural changes - Complex refactoring - Multi-file modifications - When requirements need clarification ## What the Planner Does 1. **Restate Requirements** - Clarify what needs to be built 2. **Identify Risks** - Surface potential issues and blockers 3. **Create Step Plan** - Break down implementation into phases 4. **Define Success Criteria** - How to verify completion ## The planner agent will NOT write...
/planPlans implementation before changing code or content, producing structured output with assumptions, risks, and open questions.
/makeCreates structured implementation plan in docs/plans/yyyymmdd-<task-name>.md for described feature or task via interactive context gathering and focused questions.
/plannewCreates new development plan from scratch using feature/project description. Enters plan mode, enforces TDD/DRY/SOLID principles, sets up tasks with strict rules.
/planCreates a structured implementation plan for a requested feature or change, with requirements analysis, architecture review, step breakdown, risks, and a sequential numbered checklist.
/planStarts pre-implementation planning mode for detailed strategies on features, systems, APIs, databases, and infrastructure. Outputs structured plan with requirements, designs, tasks, risks; requires explicit user approval before coding.
/planGenerates detailed 3-phase implementation plans covering requirements, design, tasks, risks, and quality checks for any project. Awaits explicit user approval before coding.
Share bugs, ideas, or general feedback.
Use the planner agent to create a comprehensive implementation plan before writing any code.
/plan Add bootstrap confidence intervals to the model summary output
After receiving a plan, respond with:
The planner will provide:
# Implementation Plan: [Feature Name]
## Overview
[Summary of what will be built]
## Requirements
- [Requirement 1]
- [Requirement 2]
## Implementation Steps
### Phase 1: [Phase Name]
1. [Step with file path and action]
2. [Step with file path and action]
### Phase 2: [Phase Name]
...
## Testing Strategy
- Unit tests: [what to test]
- Integration tests: [what to verify]
## Risks & Mitigations
- **Risk**: [Description]
- Mitigation: [How to address]
## Success Criteria
- [ ] Criterion 1
- [ ] Criterion 2
/tdd - Test-driven development workflow/code-review - Review code for quality issues