implement-feature

Automating end-to-end feature development workflow orchestration requires coordinating micro-skills across the lifecycle, enforcing mandatory gates from spec-editor to report-writer, and routing blocked stages back to origin. You define SPEC.md to let the orchestrator execute the flow.

A gated workflow in software feature development is a canonical process that blocks progress when prerequisites are unmet. It enforces non-skipping stages like spec-validator and quality-gate, routing BLOCKED gates back to the origin stage for secure handoffs.

To resume an incomplete feature development flow, the orchestrator analyzes existing artifacts to determine the correct starting point. It supports resume-from-current-stage logic to continue the workflow seamlessly without repeating completed steps.

Preflight checks in feature lifecycle orchestration enforce mandatory gates before progressing. They verify prerequisites are met, activate conditional micro-skills like spec-clarify or security-review when triggered, and ensure secure handoffs across the canonical workflow.

Yes, you need a SPEC.md file to coordinate feature cycles. Defining SPEC.md allows the orchestrator to execute the end-to-end feature workflow from spec-editor to report-writer, enforcing gates and handoffs consistently.

You should avoid automated workflow orchestration for feature development when your project requires skipping mandatory gates or bypassing preflight checks. The orchestrator enforces non-skipping stages, so it limits flexibility for rapid prototypes lacking formal specs.