What problem does it solve? Starting a new specification-driven change often produces inconsistent proposals, missing design or task artifacts, and untracked workflow state. This Skill standardizes the open phase of the Comet workflow by creating or recovering an OpenSpec change with its proposal.md, design.md, tasks.md, and .comet.yaml state file. ## Core Features & Use Cases - Guided Requirements Clarification: Explores goals, non-goals, scope boundaries, key unknowns, and acceptance scenarios before any artifact is written. - PRD Split Preflight: Detects large PRDs or multi-capability plans and proposes splitting them into independent, ordered changes tracked in a batch manifest. - State-Machine-Tracked Artifact Generation: Initializes .comet.yaml, drives the OpenSpec status/instructions loop until every required artifact is done, and enforces a blocking user review before phase transition. - Use Case: A developer pastes a large product roadmap and invokes /comet-open; the Skill proposes a split into three changes, creates each change's proposal, design, and tasks artifacts, and asks which one to advance into the design phase. ## Quick Start Invoke /comet-open with a description of the change you want to plan, and confirm the generated proposal, design, and tasks artifacts when prompted.