implementation-planning

Generate executable implementation plans with file paths, code, and tests.

3|1|Updated Jan 4, 2026

Search Tags:#planning #TDD #refactoring #tests #files #implementation-plan

Ready to run

npx skills add https://github.com/jagreehal/jagreehal-claude-skills --skill implementation-planning-jagreehal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-planning
Source: https://github.com/jagreehal/jagreehal-claude-skills/tree/main/skills/implementation-planning
Command: npx skills add https://github.com/jagreehal/jagreehal-claude-skills --skill implementation-planning-jagreehal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams plan multi-step implementations before coding by documenting every required file, test, and verification step in a clear, executable plan that minimizes ambiguity and rework.

Core Features & Use Cases

Generates granular, executable implementation plans with exact file paths, proposed code, and corresponding tests.
Enforces a strict TDD workflow by outlining failing tests, steps to implement code, run tests, and verify outcomes.
Supports complex refactors and features that span multiple files, ensuring coordination and traceability.

Quick Start

Create a plan for a new feature by specifying the feature name, goal, and a sequence of two to five tasks. For each task, describe the files to create or modify, the tests to add, and the verification steps. Save the plan and follow the outlined steps in order.

Frequently Asked Questions about implementation-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I plan multi-step refactoring tasks to avoid ambiguity and drift?▼

To plan multi-step refactoring tasks, you document every required file, test, and verification step in a clear, executable plan before coding begins. This minimizes ambiguity and rework by ensuring coordinated file changes and traceability.

What is the best way to structure a TDD workflow before writing any code?▼

The best way to structure a TDD workflow is to outline exact file paths, failing tests, implementation steps, and commit points before development starts. This enforces a strict test-first sequence and verifies outcomes at each step.

How do I coordinate complex feature implementations spanning multiple files?▼

To coordinate complex features across multiple files, generate a granular implementation plan specifying exact file paths, proposed code, and corresponding tests. This ensures changes remain synchronized and traceable throughout the process.

Can I specify exact file paths and code changes when planning a new feature?▼

Yes, you can specify exact file paths and code changes when planning a new feature. You define the feature goal, sequence two to five tasks, and outline the files to modify, tests to add, and verification steps for each.

When do I need an executable implementation plan for software engineering tasks?▼

You need an executable implementation plan for design-driven tasks, complex refactors, and features demanding coordinated file changes. It eliminates drift by documenting explicit test and verification steps before implementation begins.

Why does my multi-step implementation drift from the original design?▼

Multi-step implementation drifts from the original design when exact file paths, tests, and verification steps are not documented beforehand. Creating an executable plan with explicit TDD steps eliminates this ambiguity and rework.