Automated summary
Converts approved designs or detailed requirements into actionable, atomic implementation steps.
Strengths
- Breaks complex tasks into small, manageable steps
- Generates a structured plan in Markdown format
- Incorporates best practices like TDD and verification
Limitations
- Does not produce code, only a plan
- Requires that the design is already approved
- Can become lengthy for very large projects
When you have an approved design or detailed requirements and need a step-by-step guide for implementation.
For simple tasks that can be implemented directly without prior planning.
Security analysis
SafeThe skill only provides instructions for planning implementation steps. It does not involve executing any code, accessing the network, or performing destructive actions. There are no declared tools, so no execution risk.
No concerns found
How this analysis is madeExamples
I have an approved product_design.md for a user authentication module. Please create an implementation_plan.md with atomic steps, including TDD and verification.How would I implement a real-time dashboard? Provide an implementation plan with step-by-step tasks, file paths, and verification checks.name: planning-implementation description: Converts approved designs or detailed requirements into actionable, atomic implementation steps. Use when the user approves a design or asks "how to implement".
Planning & Implementation Breakdown
When to use this skill
- User has approved a
product_design.md. - User provides a detailed requirement and asks for a plan.
- User asks "how to implement" a specific complex feature.
Workflow
-
Read Context & Standards
- Read
product_design.mdor the user's specific requirements. - MANDATORY: Check
managing-environmentskill for Project Setup & Dependency standards (Docker/pyproject.toml).
- Read
-
Atomic Task Decomposition
- Break the project down into a linear series of steps.
- Atomic Rule: Each step must be small enough to be completed by an AI agent in 2-5 minutes (e.g., "Create button component" is good; "Build entire frontend" is bad).
- No Code: This phase is for planning the code, not writing it.
-
Generate Documentation
- Create or update
implementation_plan.md. - Format:
# Implementation Plan - [Project Name] - [ ] Step 1: Environment Setup - Initialize project (e.g., `npm create vite@latest`). - Install dependencies. - [ ] Step 2: Foundation - Create basic directory structure. - Setup global styles/theme. - [ ] Step 3: [Feature A] - Component X - Create file... - Implement logic... ...
- Create or update
-
Best Practices
- TDD: Include steps for creating tests before implementation where appropriate.
- Verification: Include a verification step after major implementation blocks (e.g., "Run tests", "Check browser").
Instructions
- Granularity: If a step feels like it has "sub-steps", break it apart.
- Clarity: Use exact file paths and command examples in the plan where possible.
- Output: The primary deliverable is the
implementation_plan.md.
Resources
- [None]
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/planning-implementation-breakdown-mm5t8bl6/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/planning-implementation-breakdown-mm5t8bl6' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/planning-implementation-breakdown-mm5t8bl6/download' --output '.skill-downloads/planning-implementation-breakdown-mm5t8bl6/SKILL.md.part' && mv '.skill-downloads/planning-implementation-breakdown-mm5t8bl6/SKILL.md.part' '.skill-downloads/planning-implementation-breakdown-mm5t8bl6/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/planning-implementation-breakdown-mm5t8bl6/SKILL.md' && test -s '.skill-downloads/planning-implementation-breakdown-mm5t8bl6/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/planning-implementation' && cp -R '.skill-downloads/planning-implementation-breakdown-mm5t8bl6' '.claude/skills/planning-implementation'Cursor
test -f '.skill-downloads/planning-implementation-breakdown-mm5t8bl6/SKILL.md' && test -s '.skill-downloads/planning-implementation-breakdown-mm5t8bl6/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/planning-implementation' && cp -R '.skill-downloads/planning-implementation-breakdown-mm5t8bl6' '.cursor/skills/planning-implementation'Codex
test -f '.skill-downloads/planning-implementation-breakdown-mm5t8bl6/SKILL.md' && test -s '.skill-downloads/planning-implementation-breakdown-mm5t8bl6/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/planning-implementation' && cp -R '.skill-downloads/planning-implementation-breakdown-mm5t8bl6' '.agents/skills/planning-implementation'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/planning-implementation-breakdown-mm5t8bl6'openskills read 'planning-implementation-breakdown-mm5t8bl6'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/planning-implementation-breakdown-mm5t8bl6/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.