feature-dev

End-to-end feature development automation is achieved by invoking the pipeline with a feature brief to generate a phased plan, execute implementation, route workflows, and track artifacts through gate checks to production-ready code.

Coordinating feature delivery across UI and backend domains is handled through automatic workflow routing, which detects the target domain and composes appropriate skills to execute implementation, review, and cleanup tasks.

Automated gate checks ensure alignment and traceability during product initiative planning by tracking tasks, dependencies, and generated artifacts across docs/spec throughout the full feature lifecycle.

Parallel execution for feature implementation workflows is managed by the orchestrator, which routes independent tasks simultaneously across UI and backend domains while maintaining dependency tracking and gate enforcement.

A feature brief is required to start the feature delivery lifecycle, serving as the initial input for the pipeline to generate a full phased plan, route workflows, and orchestrate implementation through to documentation.

A plan-driven approach for feature delivery is not suited for isolated, single-domain code changes that bypass the full lifecycle, as it enforces phased plans, gate checks, and artifact generation designed for complex cross-team initiatives.