Plan
Start non-trivial work with a clean plan. Understand → Plan → Estimate → Execute → Verify.From its SKILL.md
npx -y skills add RhythmMittal19/claude-config --skill planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 229 tokens by cl100k_base, as published. Nobody here has run it
Current Project Context
!basename $(pwd)
!cat package.json 2>/dev/null | head -5 || cat pyproject.toml 2>/dev/null | head -5 || cat Cargo.toml 2>/dev/null | head -5 || echo "No manifest found"
Current Branch & Status
!git branch --show-current 2>/dev/null
!git status --short 2>/dev/null | head -10
Task
$ARGUMENTS
Instructions
- Understand: Read relevant files using subagents. Don't guess at architecture — explore first.
- Plan: Create a numbered step-by-step plan. Each step should be independently verifiable.
- Estimate: How many files will change? Any risky areas?
- Ask: If anything is ambiguous, ask ONE clarifying question before proceeding.
- Execute: Only after plan is approved, implement step by step.
- Verify: Run tests after each significant change. Show me the results.
Present the plan and wait for my approval before coding.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.