What problem does it solve? Managing multi-phase software changes (proposal, design, build, verify, archive) across OpenSpec and Superpowers tooling is error-prone when agents lose track of state, skip design steps, or resume the wrong change. This Skill provides a deterministic routing and state machine that detects the active change, resolves user intent, and drives each phase with explicit decision points. ## Core Features & Use Cases - Intent routing and phase detection: Builds a CometIntentFrame from the user request and active changes, routes through the intent runtime to hotfix, tweak, full, resume, or ask_user paths. - State-driven workflow: Reads .comet.yaml to determine the current phase (open, design, build, verify, archive) and enforces hard constraints like isolation, build_mode, tdd_mode, and review_mode before transitions. - Blocking decision points: Pauses at ten defined user decision nodes (workflow selection, design confirmation, build settings, archive confirmation, preset upgrades) instead of auto-deciding. - Use Case: A developer says "/comet-classic add rate limiting to the API"; the Skill detects no active change, routes to the full workflow, invokes /comet-open to create OpenSpec artifacts plus .comet.yaml, then advances through design, build, verify, and archive with confirmations at each decision point. ## Quick Start Ask the assistant to start or resume the Comet Classic workflow for your change, for example by invoking /comet-classic with a short description of the change you want to make.