feature-implement

Executes a staged feature plan with test-driven development, committing one green stage at a time.

Updated May 26, 2026
One-click install
npx skills add https://github.com/cagriy/dev-skills --skill feature-implement-cagriy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-implement
Source: https://github.com/cagriy/dev-skills/tree/main/skills/feature-implement
Command: npx skills add https://github.com/cagriy/dev-skills --skill feature-implement-cagriy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a written implementation plan into working code often drifts: stages get skipped, tests go unrun, and half-finished work lands on a red test suite. This Skill executes an existing feature plan stage-by-stage with strict TDD discipline, so every stage is tested, reviewed, and committed before the next begins. ## Core Features & Use Cases - Stage-by-stage TDD execution: Reads the plan and design files from the feature folder, then implements each plan stage test-first — write the test, watch it fail, implement, watch it pass — with one commit per green stage. - Red-baseline protection: Baselines existing test, lint, and type failures before writing code and refuses to build on an already-failing test suite, offering to investigate, file a bug, or halt instead. - Adaptive execution strategy: Runs serial batches as chunked subagent units by default, executes parallel batches concurrently in throwaway git worktrees (up to four at a time), and falls back to direct execution for small or non-delegatable runs. - Use Case: After running /feature-plan for a new reminders feature, invoke /feature-implement to build all staged work on the current branch, resuming automatically from the lowest uncommitted stage if a previous run was interrupted. ## Quick Start Run /feature-implement to build the latest feature that already has a plan, or /feature-implement v3 to target a specific version.

Frequently Asked Questions about feature-implement

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

FAQPage Schema
How do I implement a feature plan with test-driven development?

Run /feature-implement after creating a plan with /feature-plan. It reads the plan and design files, then builds each stage test-first: write the test, confirm it fails, implement, confirm it passes, and commit. Each green stage produces exactly one commit on the current branch.

What happens if tests are already failing before implementation starts?

The skill stops before writing any code and asks how to proceed: investigate the failures together, file a bug via the bug-submit skill, or halt entirely. It never builds new stages on top of a red test baseline, even under autonomous-run instructions.

Can feature-implement resume an interrupted implementation run?

Yes. It scans git history for prior stage commits matching the plan version and resumes at the lowest uncommitted stage. Stages blocked by unmet external prerequisites are excluded and reported as blocked in the strategy announcement.

Does feature-implement create branches or push to remote?

No. It works strictly on the current branch, syncs with the remote via fetch and fast-forward pull only, and never creates branches or pushes. Parallel batch stages build in throwaway detached git worktrees, then commits are cherry-picked onto the current branch in stage order.

When does feature-implement use subagents instead of running directly?

Subagent units are the default when more than two stages remain and at least two are delegatable. It runs directly when the user explicitly asks, when two or fewer stages remain, or when a pre-scan finds almost nothing delegatable, such as stages requiring live UI verification.