dev-cycle-cycle-chief

Dev cycle orchestration runs a six-phase pipeline from PRD or Epic entry points to validated output by resolving entries, creating stories, researching the stack, executing waves, consolidating, and running product validation.

Sequential wave execution processes stories in dependency order using subagents, applies conditional gates between waves, and stops pipeline execution automatically when wave integrity validation fails.

Yes, you can run end-to-end dev pipelines with strict phase dependencies by activating the SKILL entrypoint with YAML-defined command loading, enforcing ordered phase completion, and verifying QA gates.

Pipeline-grade reporting produces consolidated artifacts including stack context research, sequential wave execution results, and a final dev-cycle report summarizing the validated feature delivery.

Yes, you need a PRD, Epic, or Story entry point to start the dev cycle pipeline, which detects the entry type and resolves it to generate stories and research the current stack.

You should avoid automated dev cycle orchestration for feature delivery scenarios outside end-to-end dev pipelines, or when your workflow cannot support strict ordered phase completion and wave gate verification.