# 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).

- Skill: `jagreehal/implementation-planning` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add jagreehal/implementation-planning`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jagreehal/implementation-planning/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jagreehal (https://skillmd.com/u/jagreehal)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/jagreehal/implementation-planning

---


# 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`.