feature-impl

Phased feature implementation is coordinated by a central orchestrator that enforces workflow stages including investigation, design, implementation, validation, and integration. It manages multi-agent coordination by specifying inputs like spawn context and capturing evidence during phase transitions.

Orchestration governance in multi-agent feature delivery provides traceability and risk management across teams. It enforces design approvals, implementation quality checks, and integration validation through configurable phased workflows with clear phase transitions and evidence capture.

To start a phased workflow for end-to-end feature work, submit a feature description and spawn context to the orchestrator. This initiates the configurable workflow that adapts to project needs and progresses through investigation, clarifying questions, design, implementation, validation, and integration.

Yes, phased workflows are configurable to adapt to different project needs. The orchestrator adjusts the progression through investigation, design, implementation, validation, and integration phases based on the feature description and spawn context provided as inputs.

Yes, worker-base is a required dependency for running orchestrated feature workflows. It provides the foundational environment needed for the multi-agent coordination and phased governance that the orchestrator enforces during feature delivery.

Orchestration for feature implementation is designed for multi-agent, model-driven environments where governance and traceability are critical. It relies on spawn context and verification specs as inputs, meaning feature work outside this structured phased workflow model may not be suitable for this approach.