staged-implementation

Implements coding changes in engineer-approved stages with test-first execution and confirmation gates.

Updated Feb 26, 2025
One-click install
npx skills add https://github.com/adschill/dev-config --skill staged-implementation-adschill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: staged-implementation
Source: https://github.com/adschill/dev-config/tree/main/skills/staged-implementation
Command: npx skills add https://github.com/adschill/dev-config --skill staged-implementation-adschill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large coding changes delivered all at once are hard to review, easy to get wrong, and difficult to course-correct mid-way. This Skill breaks implementation into small, reviewable stages so an engineer can inspect, modify, and approve each increment before work continues. ## Core Features & Use Cases - Stage Map Planning: Proposes a fixed-total stage plan (e.g., 1/4 through 4/4) where each stage has one primary deliverable, an explicit scope, exclusions, and a test target, and waits for approval before starting. - Test-First Stage Execution: For each stage, writes or updates the narrowest relevant test first, implements only that stage's behavior, runs focused verification, and reports results in a structured format. - Approval Gates and Engineer Edits: Pauses after every stage for explicit confirmation, and on resumption inspects the working tree to preserve and account for engineer changes, revising the stage map when needed. - Use Case: When asked to add a new API endpoint with persistence and client changes, the Skill proposes a 3-5 stage plan, implements each vertical slice with its tests, and stops for your review between stages instead of dumping one large diff. ## Quick Start Ask the assistant to use $staged-implementation to implement your requested change in reviewed stages.

Frequently Asked Questions about staged-implementation

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

FAQPage Schema
How do I implement a large coding change in reviewable stages?▼

Invoke staged-implementation explicitly and it will propose a fixed-total stage map before editing any code. Each stage delivers one reviewable outcome with its tests, and work pauses for your approval before the next stage begins.

How does staged implementation handle test-first development?▼

Each stage creates or updates the narrowest relevant test first when practical, runs it to establish the expected failure, then implements only that stage's behavior. When test-first is impractical, the reason is documented in the stage report.

When should I not use staged implementation?▼

Avoid it for trivial single-step edits where stage overhead adds no review value. It is designed for multi-concern changes and only activates on explicit invocation, not automatically for every coding request.

What happens if I edit code between stages?▼

On resumption, the Skill inspects the working tree and diff before editing, preserves your changes, and summarizes their impact on completed and remaining stages. If your edits invalidate the plan, it publishes a revised stage map before continuing.

How many stages should an implementation plan have?▼

The Skill defaults to three to five stages, using two only when both are genuinely narrow end-to-end vertical slices. Each stage must have exactly one primary deliverable that an engineer can review without mentally completing unfinished work.