home/dot_claude/exact_skills/impl-plan/SKILL.md
Creates task-based implementation plans using Prompt-Driven Development to refine ideas into actionable plans with dependency mapping, risk registers, and demoable increments. Use when user mentions implementation plan, impl plan, create plan, build plan, development plan, breakdown tasks, task plan, sprint plan, or plan implementation. Do NOT use for general conversation about plans, scheduling, or project management without implementation context.
npx skillsauth add guicaulada/dotfiles impl-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Section | Purpose | |--------------------|-------------------------------------------------------| | Overview | Sets context and defines the goal | | Requirements | Consolidated requirements from clarification | | Architecture Notes | Key technical decisions informing the plan | | Task Breakdown | Ordered tasks with objectives and acceptance criteria | | Dependency Map | Task dependencies and critical path | | Risk Register | Identified risks and mitigations |
The skill follows the Prompt-Driven Development methodology — iterative refinement through requirements clarification, research, and checkpoint reviews before generating the implementation plan. The full process is embedded in the create workflow.
Trigger: "impl plan", "implementation plan", "create plan", "build plan", "development plan", "breakdown tasks", "task plan", "sprint plan", "plan implementation"
Read and follow create.md.
testing
Fetches GitHub issues, pull requests, reviews, notifications, and project board data for the user and optionally teammates, then analyzes their state and produces a prioritized work plan. Use when prioritizing work, triaging GitHub activity, planning what to work on next, assessing current workload, checking sprint status, or reviewing project board items. Supports teammate usernames and focus areas via arguments. Do NOT use for creating, modifying, or closing issues, PRs, or other GitHub resources.
testing
Transforms text into exhaustive structured bullet-point summaries for studying and test preparation. Use when user mentions summarize, create a summary, bullet point this, give me the key points, study notes, help me study, prepare for exam, create study guide, or make flashcard content.
development
Reviews pull requests with detailed code analysis and feedback. Use when user mentions review pr, pr review, review pull request, check pr, analyze pr, code review, review prs, batch review. Not for dependency bump PRs (use /review-deps instead).
testing
Reviews dependency bump PRs with focus on compatibility and security issues. Use when user mentions review deps, review dependencies, dependency review, check deps, dependency prs, dep bumps, review deps prs, batch dep review.