comet-open

Creates and recovers OpenSpec change proposals, designs, and task artifacts through the Comet state machine.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill comet-open-shrek-abaper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-open
Source: https://github.com/shrek-abaper/sap-nexus-agent/tree/main/.comet/skills/skills/comet-open
Command: npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill comet-open-shrek-abaper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new OpenSpec change involves clarifying requirements, splitting large PRDs, generating proposal/design/tasks artifacts, and initializing recoverable state; this Skill orchestrates that entire open phase with enforced checks so changes enter the Comet workflow consistently. ## Core Features & Use Cases - Guided clarification and PRD splitting: Explores goals, non-goals, scope, and acceptance scenarios, and splits large PRDs into independently deliverable changes tracked in a batch manifest. - Status-driven artifact generation: Uses the OpenSpec CLI status and instructions loop to generate proposal.md, design.md, and tasks.md in dependency order without hard-coded templates. - Recoverable state management: Initializes and validates .comet.yaml state, supports idempotent recovery of interrupted runs, and enforces a blocking user review before the phase guard transitions to design. - Use Case: A product owner pastes a large roadmap PRD; the Skill clarifies scope, proposes a split into three changes, creates OpenSpec artifacts for each, and hands the chosen change off to the design phase. ## Quick Start Invoke /comet-open and describe the change or PRD you want to turn into an OpenSpec change with proposal, design, and tasks artifacts.

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 with proposal, design, and tasks?▼

Invoke /comet-open with your requirement or PRD. The skill clarifies goals and scope, derives a kebab-case change name, then generates proposal.md, design.md, and tasks.md through the OpenSpec status and instructions loop before asking for your confirmation.

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

The open phase runs a PRD split preflight that proposes independent changes with goals, scope, and acceptance scenarios. After you confirm, each item is created as its own change and tracked in a batch manifest under .comet/batches.

What OpenSpec CLI version is required for the comet open phase?▼

OpenSpec version 1.5.0 or higher is required. The skill runs a compatibility check first and stops if the CLI is older, unparseable, or missing the applyRequires, artifactPaths, changeRoot, or resolvedOutputPath contracts.

Can I resume an interrupted OpenSpec change creation?▼

Yes, the open phase is idempotent. On recovery it inspects .comet.yaml, reruns status, keeps done artifacts, regenerates ready ones, and resolves blocked artifacts by completing their missing dependencies first.

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

User review is a blocking point. The skill must present the change name, scope, and artifact summary for confirmation, and only after approval runs the phase guard with --apply to transition to the design phase.