What problem does it solve? Software delivery work often loses track of which stage an initiative is actually at, who approved what, and whether a document was audited before anyone built from it. This Skill acts as the entry point for the SDLC flow: it checks the recorded state of an initiative first, then routes work to the correct stage so nothing proceeds on an unrecorded agreement. ## Core Features & Use Cases - Status-driven routing: Calls initiative_status before anything else and routes to explore, spec, audit, plan, execute, or review based on what the document store actually records. - Stage orchestration: Coordinates seven stages — parallel fan-out exploration, person-owned spec and plan gates, sequential evidence-routed audits, per-item execution subagents, and independent code review. - Recorded close: Ends every initiative with initiative_close (finished, accepted, or abandoned) so the outcome reaches the team ledger, with optional handover to zz-handover. - Use Case: A stakeholder brings a brain dump for a new feature. The Skill checks initiative status, fans out explore workers to establish the ground, walks the spec and plan through their agreement and audit gates, dispatches execution and review, then closes the initiative with the outcome on the record. ## Quick Start Ask the agent to start or resume a software delivery initiative and let it check the initiative status to decide which SDLC stage runs next.
