duck-plan
SolidPlan-review session with the rubber duck — verify the user understands decisions and trade-offs before execution. Use after a plan/spec/RFC was produced, or when they say "duck plan", "이 플랜 검수해". Not for plan authoring or code review.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- LeeJuOh
- Repository
- LeeJuOh/claude-code-zero
- Created
- 4 months ago
- Last Updated
- 4 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
duck-verify
Code-verification session with the rubber duck — user explains code just written, finds edge cases, fixes planted bugs. Use after implementing a feature, or when they say "duck verify", "재확인해줘". Not for plan review (/duck-plan) or PR review (/duck-review).
duck-review
PR/change-review session with the rubber duck — user justifies every change and predicts consequences. Use before commit/push/PR, or when they say "duck review", "리뷰 전에 점검". Not for code-level explanation (/duck-verify) or plan review (/duck-plan).
duck
Rubber duck tutor — auto-detects which review mode to run. Use when the user says "duck", "tutor", "quiz me", "do I understand this", or mentions rubber-stamping or learning while coding. For a specific phase use /duck-design, /duck-plan, /duck-verify, /duck-review, or /duck-orient.