Automated summary
Creates comprehensive implementation plans with bite-sized tasks to guide step-by-step development.
Strengths
- Breaks work into 2-5 minute tasks
- Includes full TDD steps with code and commands
- Outputs a persistent, reusable plan file
Limitations
- Requires clear requirements upfront
- Can be overly rigid for exploratory tasks
- Assumes familiarity with TDD
Before coding a multi-step feature when requirements are well understood.
For quick fixes or very simple tasks that only need a single change.
Security analysis
SafeThe skill only instructs the AI to generate a markdown plan. It does not execute any commands or access external services, and it contains no destructive or exfiltration instructions.
No concerns found
How this analysis is madeExamples
I need to add a new GET endpoint /api/users/:id to return user details. Create an implementation plan with bite-sized tasks following the planning-work skill.We are adding a 'role' column to the users table. Generate a detailed implementation plan including TDD steps and migration script.I want to refactor the authentication module to use JWT instead of session-based auth. Please create a plan with tasks and exact file paths.name: planning-work description: Creates comprehensive implementation plans with bite-sized tasks. Use when you have clear requirements and need a step-by-step guide for execution.
Planning Work (Writing Plans)
When to use this skill
- After requirements are clear (e.g., post-brainstorming).
- Before modifying any code for a multi-step task.
- When you need to generate a
docs/plans/YYYY-MM-DD-feature.mdfile.
Workflow
- [ ] Analyze Context: Understand codebase and questionable taste.
- [ ] Create Header: Start plan with the required header and goal.
- [ ] Define Architecture: Summarize approach in 2-3 sentences.
- [ ] Break Down Tasks: Create bite-sized (2-5 min) tasks.
- [ ] Write Task Steps: For each task, define files, tests, and step-by-step TDD instructions.
- [ ] Save Plan: Save to
docs/plans/YYYY-MM-DD-<feature-name>.md. - [ ] Confirm: Present options for execution.
Instructions
1. Plan Philosophy
- Assume the executor has zero context.
- Bite-Sized: Each task should be 2-5 minutes of work.
- Micro-Steps: "Write failing test" -> "Verify failure" -> "Implement minimal code" -> "Verify pass" -> "Commit".
- DRY, YAGNI, TDD.
2. Plan Header Template
Every plan MUST start with:
# [Feature Name] Implementation Plan
**Goal:** [One sentence describing what this builds]
**Architecture:** [2-3 sentences about approach]
**Tech Stack:** [Key technologies/libraries]
---
3. Task Structure Template
### Task N: [Component Name]
**Files:**
- Create: `exact/path/to/file.py`
- Modify: `exact/path/to/existing.py:123-145`
- Test: `tests/exact/path/to/test.py`
**Step 1: Write the failing test**
[Code Block]
**Step 2: Run test (Expect Fail)**
`command to run test`
**Step 3: Write minimal implementation**
[Code Block]
**Step 4: Run test (Expect Pass)**
`command to run test`
**Step 5: Commit**
`git commit -m "feat: ..."`
4. Execution Handoff
After saving the plan, offer:
- Subagent-Driven: You iterate task-by-task in this session.
- Parallel Session: User opens a new session/window to execute.
Key Principles
- Exact file paths always.
- Complete code snippets (no "add validation logic", write the logic).
- Exact commands for running tests.
- Reference other skills if needed.
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-work-mmbizki3/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-work-mmbizki3' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/planning-work-mmbizki3/download' --output '.skill-downloads/planning-work-mmbizki3/SKILL.md.part' && mv '.skill-downloads/planning-work-mmbizki3/SKILL.md.part' '.skill-downloads/planning-work-mmbizki3/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-work-mmbizki3/SKILL.md' && test -s '.skill-downloads/planning-work-mmbizki3/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/planning-work' && cp -R '.skill-downloads/planning-work-mmbizki3' '.claude/skills/planning-work'Cursor
test -f '.skill-downloads/planning-work-mmbizki3/SKILL.md' && test -s '.skill-downloads/planning-work-mmbizki3/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/planning-work' && cp -R '.skill-downloads/planning-work-mmbizki3' '.cursor/skills/planning-work'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-work-mmbizki3'openskills read 'planning-work-mmbizki3'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-work-mmbizki3/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.