plan
Create a detailed implementation plan for a feature or task. Use when user wants to plan before coding.
pinned to #d5a3918updated 2 weeks ago
Ask your AI client: “install skills/plan”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/planmetahub onboarded this repo on the author's behalf.
If you own github.com/DeL-TaiseiOzaki/claude-code-orchestra on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
184
Last commit
2 weeks ago
Latest release
published
About this skill
Pulled from SKILL.md at publish time.
Create an implementation plan for $ARGUMENTS.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.d5a3918· 2 weeks ago
Documentation
41Description quality
18 words · 103 chars — "Create a detailed implementation plan for a feature or task. Use when user wants…"
README is present and substantial
18,894 chars · 9 sections · 21 code blocks
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
README has usage / example sections
found: Quick Start
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrentd5a3918warn2 weeks ago
Contents
Create an implementation plan for $ARGUMENTS.
Planning Process
1. Requirements Analysis
First clarify:
- Purpose: What to achieve
- Scope: What to include, what to exclude
- Constraints: Technical, time, dependencies
2. Current State Investigation
Investigate the codebase:
- Related existing code
- Files affected
- Libraries/patterns to use
- Existing tests
3. Break Down Implementation Steps
Break into small steps:
- Each step is independently testable
- Consider dependency order
- High-risk steps first
4. Output Format
## Implementation Plan: {Title}
### Purpose
{1-2 sentences}
### Scope
- New files: {list}
- Modified files: {list}
- Dependencies: {list}
### Implementation Steps
#### Step 1: {Title}
- [ ] {Specific task}
- [ ] {Specific task}
**Verification**: {Completion criteria for this step}
#### Step 2: {Title}
...
### Risks & Considerations
- {Potential issues and mitigations}
### Open Questions
- {Items to clarify before implementation}
Notes
- Plans should be at actionable granularity
- Include verification method for each step
- Ask questions at planning stage for unclear points
- Don't over-detail (adjust during implementation)
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/plan