Skip to content
Skills Library
Programming · Planning

implementation-planning

/implementation-planning

Creates bite-sized, TDD-ordered plans with exact paths, copy-pasteable code, and verification steps for a zero-context executor. Use this skill when an approved design or clear multi-step change is ready and coding is about to start. Do not use when/for exploring requirements (use design-exploration) or only listing high-level tasks (use create-tasks).

Licence
MIT
Last repository change
30.07.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Creates bite-sized, TDD-ordered plans with exact paths, copy-pasteable code, and verification steps for a zero-context executor. Use this skill when an approved design or clear multi-step change is ready and coding is about to start. Do not use when/for exploring requirements (use design-exploration) or only listing high-level tasks (use create-tasks).

Original author description

Creates bite-sized, TDD-ordered plans with exact paths, copy-pasteable code, and verification steps for a zero-context executor. Use this skill when an approved design or clear multi-step change is ready and coding is about to start. Do not use when/for exploring requirements (use design-exploration) or only listing high-level tasks (use create-tasks).

How it works

  1. Critical rules
  2. Workflow
  3. Resources
  4. Validation
  5. Constraints
Original SKILL.md headings · 36 lines, 218 words
SKILL.md preview
---
name: implementation-planning
description: >-
  Creates bite-sized, TDD-ordered plans with exact paths, copy-pasteable code,
  and verification steps for a zero-context executor. Use this skill when an
  approved design or clear multi-step change is ready and coding is about to
  start. Do not use when/for exploring requirements (use design-exploration) or
  only listing high-level tasks (use create-tasks).
version: 1.2.0
---

# Implementation Planning

## Critical rules

- `NO IMPLEMENTATION WITHOUT A PLAN FIRST` for multi-step work.
- Assume the executor has zero codebase context: exact paths, complete code, exact commands with expected output.
- Every task: test → fail → implement → pass → commit. One action per step (~2-5 min).
- Never vague steps, skipped verification, bundled multi-file "and" steps, or assumed knowledge.
- Save to `docs/plans/YYYY-MM-DD-<feature-name>.md`. Prefer `fn(args, deps)` and Result types.
- Before drafting task bodies, read [references/plan-structure.md](references/plan-structure.md).

## Workflow

1. Confirm design is approved (`design-exploration`) when requirements were ambiguous.
2. Write header: goal, architecture, tech stack.
3. Break into bite-sized TDD tasks with exact files and copy-pasteable code (see plan-structure).
4. Quality-check: one action, exact paths, complete code, expected command output, clear TDD, commit messages.
5. Save under `docs/plans/` and offer execution handoff (often inside `git-worktrees`).

## Resources

- [references/plan-structure.md](references/plan-structure.md) — header/task templates and handoff. Read before writing the plan.

## Validation

- [ ] Header has goal, architecture, tech stack
- [ ] Every task follows test → fail → implement → pass → commit
- [ ] Exact paths; commands state expected output; no bundled steps
- [ ] Plan saved to `docs/plans/` and ready for handoff

## Constraints

- Skip for single-file/single-function obvious scope.
- Related: `design-exploration`, `tdd-workflow`, `git-worktrees`, `parallel-agent-dispatch`, `create-tasks`.
Files in this package (2)
  • SKILL.md 2 KB
  • references/plan-structure.md 1 KB

Versions

RepositoryScoreLicence
This page · jagreehal/jagreehal-claude-skills90MIT
magnus919/agent-skills100MIT
raoofaltaher/science-ultrapowers100MIT
neuromechanist/research-skills100BSD-3-Clause
w7Pratham/planning-skills100MIT
forgivesam168/ai-dev-workflow100Apache-2.0
cbrock84/headcount90MIT
zeeshanhanif/agentic-sdlc-kit90Apache-2.0
anotb/management-consulting-plugin85MIT

Database snapshot: 13.11.2026 · package version ab1fef1e3bc9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100writing-plans
    Use when you have a spec or requirements for a multi-step task, before touching code. Creates detailed, bite-sized implementation plans with exact file paths, complete code, and verification steps.
  • 100plan
    Use when you have an approved design or requirements for a multi-step task, before touching code. Turns designs into implementation plans with bite-sized TDD-oriented tasks, exact file paths, and verification steps. Save to docs/plans/.
  • 100writing-plans
    Use when you have a spec or requirements for a multi-step task, before touching code. Triggers on: "create a plan", "write implementation steps", "break down the task", any planning request. Creates comprehensive implementation plans with bite-sized tasks and exact file paths.
  • 84writing-plans
    Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.
  • 100writing-plans
    Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.
  • 100writing-plans
    Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.