comet-open

Creates and initializes OpenSpec change proposals with Comet state machine tracking.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill comet-open-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-open
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/comet-open
Command: npx skills add https://github.com/JhonMA82/api-starter --skill comet-open-jhonma82

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about comet-open

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an OpenSpec change proposal with Comet?▼

Invoke /comet-open with your change description. The skill clarifies goals and scope, creates the change skeleton through the comet classic openspec adapter, generates proposal.md, design.md, and tasks.md, and initializes .comet.yaml state tracking.

How do I split a large PRD into multiple OpenSpec changes?▼

The open phase runs a PRD split preflight when input contains multiple independent capabilities. It proposes a split list with names, scopes, and dependencies, persists the accepted split to .comet/batches/<batch-id>.json, and creates each item as an independent change.

What OpenSpec version does the Comet open phase require?▼

The flow requires OpenSpec CLI version 1.5.0 or higher. The skill runs a compatibility check before any status or instructions command and stops if the version is older, unparseable, or the command fails.

Can I resume an interrupted OpenSpec change creation?▼

Yes. On resume, the skill inspects the change's .comet.yaml, reinitializes state if missing, and reruns the OpenSpec status loop. Completed artifacts are kept, ready artifacts are generated, and blocked artifacts wait for their dependencies.

Why does the open phase stop before transitioning to design?▼

The phase requires explicit user confirmation of the change name, scope, and artifact content before running the phase guard. Only after confirmation does comet guard <change-name> open --apply transition the state to the design phase.