Planning
A battle-tested Claude Code skill collection that enforces Plan→Execute→Verify→Handoff workflow. Auto-triggers brainstorming, planning, debugging, UI/UX, security, and review skills.
npx -y skills add kjhk3082/master-assistant-skill --skill planningAssembled 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.
What its author says it does
Copied from the file, not written here
[EN] You MUST use this after brainstorming or when you have a clear design/spec but before writing any code. Breaks down work into actionable, verifiable steps. [KO] 브레인스토밍 후 또는 명확한 설계/사양이 있지만 코드를 작성하기 전에 반드시 사용해야 합니다. 작업을 실행 가능하고 검증 가능한 단계로 나눕니다.
SKILL.md
1.4 KB, 240 tokens by cl100k_base, as published. Nobody here has run it
Writing Implementation Plans
Turn approved designs into actionable implementation plans.
<HARD-GATE> Do NOT write any code until the user has approved the implementation plan. </HARD-GATE>Checklist
- Review Design - Read the approved design document
- Break Down Work - Create a step-by-step plan in
plan.md - Include Verification - Every step MUST have a way to verify it works (tests, visual check, etc.)
- Get Approval - Present the plan to the user and ask for approval
- Execute - Once approved, use the
EnterPlanModetool (if available) or proceed step-by-step
Plan Format
Your plan.md MUST follow this structure:
# Implementation Plan: [Feature Name]
## Prerequisites
- [ ] Check environment
- [ ] Install dependencies
## Steps
1. [ ] **[Component/Module]**: [Brief description]
- Files to modify: `path/to/file`
- Verification: Run `npm test` or specific command
2. [ ] **[Next Component]**: ...