This skill should be used when the user asks to "create a plan", "plan the implementation", "design the approach", "break down the task", "write an implementation plan", or invokes the rpikit:plan command. Provides methodology for creating actionable implementation plans with verification criteria.
/plugin marketplace add bostonaholic/rpikit/plugin install rpikit@rpikitThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Create an implementation plan for: $ARGUMENTS
Planning transforms research findings into actionable implementation strategy. A good plan enables disciplined execution by breaking work into granular tasks with clear verification criteria. Plans serve as contracts between human and AI, ensuring alignment before code is written.
Look for existing research at: docs/plans/YYYY-MM-DD-$ARGUMENTS-research.md
(Search for files matching *-$ARGUMENTS-research.md pattern)
If research exists:
If no research exists:
Task tool with subagent_type: "file-finder"
Prompt: "Find files related to [task]. Goal: [what will be implemented]"
Before planning tasks, establish what "done" looks like:
Use AskUserQuestion to clarify requirements if needed.
Determine implementation risk level:
| Stakes | Characteristics | Planning Rigor |
|---|---|---|
| Low | Isolated change, easy rollback, low impact | Brief plan |
| Medium | Multiple files, moderate impact, testable | Standard plan |
| High | Architectural, hard to rollback, wide impact | Detailed plan |
Document the classification and rationale in the plan.
Decompose work into granular, verifiable steps.
Identify target files:
Use file paths from research document, or if unavailable, use the file-finder agent to locate files for each task area:
Task tool with subagent_type: "file-finder"
Prompt: "Find files for [specific task]. Looking for [what to modify]"
For each task include:
Prefer small tasks (2-5 minute verification time).
Group related tasks into phases with checkpoint verifications.
Research implementation approaches (when needed):
If the plan involves unfamiliar libraries, APIs, or patterns, use the web-researcher agent to inform task design:
Task tool with subagent_type: "web-researcher"
Prompt: "[specific question about implementation approach, library usage, or best practice]"
#### Step 1.1: Add validation function
- **Files**: `src/utils/validation.ts`
- **Action**: Create validateEmail() using regex from validatePhone()
- **Verify**: Unit test passes for valid/invalid emails
- **Complexity**: Small
#### Step 2.3: Update API endpoint
- **Files**: `src/routes/users.ts:45-60`
- **Action**: Add email field to user creation endpoint
- **Verify**: POST /users with email returns 201
- **Complexity**: Small
#### Step 1: Implement feature
- **Action**: Add the new feature
- **Complexity**: Large
Problem: Too vague, no verification, no file references
#### Step 1: Refactor authentication system
- **Action**: Update all auth code to use new pattern
- **Complexity**: Large
Problem: Too large, should be broken into multiple phases
Identify what could go wrong:
For external dependencies or security concerns, use the web-researcher agent to investigate known issues:
Task tool with subagent_type: "web-researcher"
Prompt: "Known issues, security vulnerabilities, or breaking changes in [library/API version]"
Include rollback strategy for high-stakes changes.
Create plan at: docs/plans/YYYY-MM-DD-$ARGUMENTS-plan.md
(Use today's date in YYYY-MM-DD format)
Use this structure:
# Plan: $ARGUMENTS (YYYY-MM-DD)
## Summary
[One paragraph describing what will be implemented]
## Stakes Classification
**Level**: Low | Medium | High
**Rationale**: [Why this classification]
## Context
**Research**: [Link to research document if exists]
**Affected Areas**: [Components, services, files]
## Success Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
## Implementation Steps
### Phase 1: [Phase Name]
#### Step 1.1: [Task Description]
- **Files**: `path/to/file.ts:lines`
- **Action**: [What to do]
- **Verify**: [How to confirm done]
- **Complexity**: Small
#### Step 1.2: [Task Description]
- **Files**: `path/to/file.ts:lines`
- **Action**: [What to do]
- **Verify**: [How to confirm done]
- **Complexity**: Small
### Phase 2: [Phase Name]
[Continue pattern...]
## Risks and Mitigations
| Risk | Impact | Mitigation |
| ------ | -------- | ---------------- |
| [Risk] | [Impact] | [How to address] |
## Rollback Strategy
[How to undo changes if needed]
## Status
- [ ] Plan approved
- [ ] Implementation started
- [ ] Implementation complete
Present plan summary and request explicit approval:
"Plan created for '$ARGUMENTS' at docs/plans/YYYY-MM-DD-$ARGUMENTS-plan.md.
Summary: [brief description] Stakes: [level] Steps: [count] steps in [count] phases
Ready to approve and begin implementation?"
Use AskUserQuestion with options:
If approved, invoke the Skill tool with skill "rpikit:implement-methodology" to begin implementation.
If a plan already exists at docs/plans/YYYY-MM-DD-$ARGUMENTS-plan.md:
(Search for files matching *-$ARGUMENTS-plan.md pattern)
When refining:
Wrong: "Update the code" Right: "Add error handling to fetchUser() in src/api/users.ts:23-45"
Wrong: Tasks without success criteria Right: Every task has "Verify:" with specific check
Wrong: Proceeding to implementation without confirmation Right: Explicit AskUserQuestion approval gate
Wrong: Spending hours planning a 10-minute fix Right: Match planning rigor to stakes level
Wrong: "We'll figure it out as we go" Right: Sufficient detail to enable disciplined execution
Before requesting approval:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.