implement-feature

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.

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.

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.

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.

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.

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.