Claude-code-customes plan
Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code.
install
source · Clone the upstream repo
git clone https://github.com/sc30gsw/claude-code-customes
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sc30gsw/claude-code-customes "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/plan" ~/.claude/skills/sc30gsw-claude-code-customes-plan && rm -rf "$T"
manifest:
.claude/skills/plan/SKILL.mdsource content
Plan Command
This skill invokes the planner agent to create a comprehensive implementation plan before writing any code.
What This Skill Does
- Restate Requirements - Clarify what needs to be built
- Identify Risks - Surface potential issues and blockers
- Create Step Plan - Break down implementation into phases
- Wait for Confirmation - MUST receive user approval before proceeding
When to Use
Use
/plan when:
- Starting a new feature
- Making significant architectural changes
- Working on complex refactoring
- Multiple files/components will be affected
- Requirements are unclear or ambiguous
How It Works
The planner agent will:
- Analyze the request and restate requirements in clear terms
- Break down into phases with specific, actionable steps
- Identify dependencies between components
- Assess risks and potential blockers
- Estimate complexity (High/Medium/Low)
- Present the plan and WAIT for your explicit confirmation
Example Output
# Implementation Plan: Real-Time Notifications ## Requirements Restatement - Send notifications when markets resolve - Support multiple channels (in-app, email, webhook) - Ensure reliable delivery ## Implementation Phases ### Phase 1: Database Schema - Add notifications table - Add user_notification_preferences table - Create indexes for performance ### Phase 2: Notification Service - Create notification service - Implement notification queue - Add retry logic ## Risks - HIGH: Email deliverability - MEDIUM: Performance with many users - LOW: Real-time subscription overhead ## Estimated Complexity: MEDIUM **WAITING FOR CONFIRMATION**: Proceed with this plan? (yes/no/modify)
Important Notes
CRITICAL: The planner agent will NOT write any code until you explicitly confirm the plan with "yes" or "proceed".
If you want changes, respond with:
- "modify: [your changes]"
- "different approach: [alternative]"
- "skip phase 2 and do phase 3 first"
Integration with Other Commands
After planning:
- Use
to implement with test-driven development/tdd - Use
if build errors occur/build-fix - Use
to review completed implementation/code-review