comet

End-to-end development workflows are managed by orchestrating a five-phase pipeline covering open, design, build, verify, and archive stages. This approach combines planning and execution into a single automated pipeline, reducing context switching by coordinating sub-skills with structured handoffs and rigorous state management.

Phase detection in automated pipelines automatically identifies the current stage of a project and dispatches tasks to appropriate subcommands. It enforces strict state management and guard checks to ensure safe, auditable transitions between design, build, and verification phases.

Traceable progress and safe handoffs are ensured through rigorous state management, guard checks, and delta-archiving. Structured transitions between planning, design, and build phases provide an auditable workflow that tracks changes and prevents unauthorized phase advancements.

This development pipeline does not list any specific external dependencies to run. It operates by coordinating internal sub-skills through scripts, applying automated phase detection and dispatch without requiring additional external tools or frameworks.

Unifying planning and execution is best achieved by combining WHAT and HOW specifications into a dual-star workflow. This method orchestrates product development from initial design through final archiving, using automatic phase detection to reduce context switching and coordinate multiple sub-skills.

Automated phase-guard workflows may not be suitable for projects requiring highly flexible, non-linear development processes. The strict state management, rigorous guards, and structured handoffs are designed for traceable, auditable pipelines and might constrain rapid prototyping or ad-hoc coding tasks.