Automated summary
Creates a structured implementation plan for a feature or task by exploring the codebase and breaking work into sequenced steps.
Strengths
- Produces a detailed, phased plan with trade-off analysis
- Integrates existing codebase discovery for context-aware recommendations
- Uses TDD approach by suggesting tests before implementation
- Includes risk assessment and success criteria
Limitations
- Requires a clear feature description to be effective
- May be limited by ability to deeply explore very large codebases
- Does not write any code until the user confirms the plan
When implementing a complex feature that requires careful planning and understanding of the existing codebase.
For trivial fixes or very simple tasks that do not warrant a formal planning phase.
Security analysis
CautionThe skill instructs a planner agent to explore codebases and create implementation plans. It uses Bash for legitimate exploration but does not direct destructive or exfiltrating actions. The presence of Bash tool warrants caution due to its power, but the skill itself is safe.
No concerns found
How this analysis is madeExamples
Create an implementation plan for adding user authentication with JWT tokens. Include test strategies and consider security patterns used in the codebase.Plan the migration of REST API endpoints from v1 to v2, preserving backward compatibility and updating documentation.Create a structured plan to refactor the payment processing module, focusing on separating concerns and improving testability.name: my-plan description: "Create a structured implementation plan for a feature or task" allowed-tools:
- Read
- Grep
- Glob
- Bash
- WebSearch
- WebFetch
- TaskCreate
- TaskUpdate
- TaskList
- TaskGet
- AskUserQuestion context: fork agent: planner
You are now in planning mode. Your goal is to create a thorough implementation plan.
Instructions
-
Understand the Request
- Read CLAUDE.md for project conventions
- Read relevant rules/ files for the domain
- If the requirement is ambiguous, ask clarifying questions via AskUserQuestion
-
Explore the Codebase
- Search for existing patterns similar to the requested feature
- Identify all files that will need changes
- Check existing tests for conventions and patterns
- Look for reusable utilities, types, and components
-
Design the Solution
- Propose an architecture with trade-off analysis
- Identify dependencies between components
- Plan the TDD approach: which tests to write first
- Consider edge cases and error handling
-
Create the Plan
- Use TaskCreate to build a sequenced implementation list
- Each task should be small enough to complete in <50% context
- Include test files in the sequence (RED before GREEN)
- Note file paths for every change
-
Output the Plan
- Analysis of what exists
- Recommended approach with rationale
- Step-by-step implementation tasks (phased)
- Trade-off analysis for key decisions
- Risks and mitigation strategies (with severity)
- Success criteria checklist
-
Wait for Confirmation
- End with:
**WAITING FOR CONFIRMATION**: Proceed? (yes / no / modify) - Do NOT write any code until the user explicitly confirms
- If user says "modify", revise the plan accordingly
- End with:
Arguments
The user will provide a feature description or requirement as the command argument.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/structured-implementation-planning-mm78noh6/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/structured-implementation-planning-mm78noh6' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/structured-implementation-planning-mm78noh6/download' --output '.skill-downloads/structured-implementation-planning-mm78noh6/SKILL.md.part' && mv '.skill-downloads/structured-implementation-planning-mm78noh6/SKILL.md.part' '.skill-downloads/structured-implementation-planning-mm78noh6/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/structured-implementation-planning-mm78noh6/SKILL.md' && test -s '.skill-downloads/structured-implementation-planning-mm78noh6/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/my-plan' && cp -R '.skill-downloads/structured-implementation-planning-mm78noh6' '.claude/skills/my-plan'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/structured-implementation-planning-mm78noh6'openskills read 'structured-implementation-planning-mm78noh6'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/structured-implementation-planning-mm78noh6/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.