agentsclimarketplace
Sign in

Implementation planning

Skill jagreehal/jagreehal-claude-skills/skills/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).From its SKILL.md

Install
npx -y skills add jagreehal/jagreehal-claude-skills --skill implementation-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, as published. Nobody here has run it

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.

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

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.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.