implement-feature

Coordinate a spec-driven workflow to implement tested Clean Architecture code.

41|7|Updated Jan 30, 2026

Search Tags:#tdd #spec-driven #orchestration #clean-architecture #planner #feature-implementation

Ready to run

npx skills add https://github.com/DGouron/review-flow --skill implement-feature-dgouron

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-feature
Source: https://github.com/DGouron/review-flow/tree/main/.claude/skills/implement-feature
Command: npx skills add https://github.com/DGouron/review-flow --skill implement-feature-dgouron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a spec-driven pipeline to transform a feature specification into tested, functional, Clean Architecture–compliant code without the user writing code directly.

Core Features & Use Cases

Orchestrates two specialized agents: a feature-planner and a feature-implementer, enabling end-to-end feature delivery from spec to tests.
Supports multiple input sources (path to a spec, GitHub issue, or inline description) and a guided plan-vet-approve loop with user validation.
Generates artifacts, test plans, and progress reports, and updates the spec and tracker before commits.

Quick Start

Provide a feature spec via /product-manager or a path to a spec, then run the orchestrator to plan, implement, test, and update docs.

Frequently Asked Questions about implement-feature

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

FAQPage Schema

How do I turn Gherkin specs into tested Clean Architecture code automatically?▼

To turn Gherkin specs into tested code, you need a spec-driven orchestration workflow that coordinates planning and implementation agents. This process generates artifacts, test plans, and compliant code from your feature specification.

What is spec-driven feature implementation in a multi-agent workflow?▼

Spec-driven feature implementation is a coordinated pipeline where specialized planner and implementer agents transform a feature specification into tested, functional code. It uses a guided plan-vet-approve loop to ensure user validation before execution.

Can I use a GitHub issue as input for feature planning and implementation?▼

Yes, you can use a GitHub issue as input for feature planning and implementation. The workflow supports multiple input sources including paths to specs, GitHub issues, and inline descriptions to start the orchestration.

Do I need a preloaded planner and implementer to run spec-driven orchestration?▼

Yes, you need a preloaded planner and implementer configured with Clean Architecture patterns to run spec-driven orchestration. These specialized agents are required to execute the end-to-end feature delivery pipeline.

How do I automate updating docs and issue trackers before code commits?▼

To automate updating docs and issue trackers before commits, the spec-driven orchestrator interfaces with the product manager role and issue trackers. It automatically updates the spec and tracker as part of the workflow before finalizing commits.

When should I not use an automated orchestrator for feature implementation?▼

You should not use an automated orchestrator for feature implementation if your project lacks Gherkin specs, Clean Architecture patterns, or the required planner and implementer agents. It is designed specifically for spec-driven, multi-agent software projects.