comet-open

Original：🇨🇳 Chinese

Translated

Comet Phase 1: Open. Invoke with /comet-open. Explore ideas and create change structure (proposal + design + tasks) via OpenSpec.

3installs

Sourcerpamis/comet

Added on2026-05-26

NPX Install

npx skill4agent add rpamis/comet comet-open

SKILL.md Content (Chinese)

View Translation Comparison →

Comet Phase 1: Open

Prerequisites

No active change, or the user wishes to create a new change

Steps

1. Explore Ideas

Immediate Action: Use the Skill tool to load the

openspec-explore

skill. Skipping this step is prohibited.

After loading the skill, freely explore the problem space following its guidance.

2. Create Change Structure + Initialize State

Immediate Action: Use the Skill tool to load the

openspec-new-change

skill. If the user's intent is unclear and a proposal needs to be formed first, load

openspec-propose

instead. Skipping this step is prohibited.

Confirm the following artifacts have been created:

openspec/changes/<name>/
├── .openspec.yaml
├── .comet.yaml
├── proposal.md       # Why + What: Problem, Objectives, Scope
├── design.md         # How (high-level): Architectural Decisions, Solution Selection
└── tasks.md          # Task List (checkboxes)

Create the

.comet.yaml

state file:

bash

COMET_SEARCH_ROOTS=("." "$HOME/.claude/skills" "$HOME/.codex/skills" "$HOME/.cursor/skills")
COMET_STATE="${COMET_STATE:-$(find "${COMET_SEARCH_ROOTS[@]}" -path '*/comet/scripts/comet-state.sh' -type f -print -quit 2>/dev/null)}"
COMET_GUARD="${COMET_GUARD:-$(find "${COMET_SEARCH_ROOTS[@]}" -path '*/comet/scripts/comet-guard.sh' -type f -print -quit 2>/dev/null)}"

if [ -z "$COMET_STATE" ] || [ -z "$COMET_GUARD" ]; then
  echo "ERROR: Comet scripts not found. Ensure the comet skill is installed." >&2
  return 1
fi

bash "$COMET_STATE" init <name> full

3. Entry State Validation

Verify the state machine has been initialized correctly:

bash

bash "$COMET_STATE" check <name> open

Proceed to Step 4 after successful verification. The script will output specific failure reasons if verification fails.

4. Content Completeness Check

Confirm the three documents are fully populated:

proposal.md: Problem background, objectives, scope, out-of-scope items
design.md: High-level architectural decisions, solution selection, data flow
tasks.md: Task list with clear descriptions for each task

Exit Criteria

proposal.md, design.md, and tasks.md have all been created and are content-complete
Phase Guard: Run
```
bash "$COMET_GUARD" <change-name> open --apply
```
; automatically transition to the next phase after all checks PASS

You must use

--apply

before exiting, otherwise

.comet.yaml

will remain in

phase: open

, and the entry check for the next phase will fail.

bash

bash "$COMET_GUARD" <change-name> open --apply

The full workflow will automatically update to

phase: design

; hotfix/tweak presets will automatically update to

phase: build

.

Automatic Transition

After meeting the exit criteria, do not wait for user input again; directly execute the next phase:

REQUIRED NEXT SKILL: Invoke the
comet-design
skill to enter the deep design phase.

comet-open

NPX Install

Tags

SKILL.md Content (Chinese)

Comet Phase 1: Open

Prerequisites

Steps

1. Explore Ideas

2. Create Change Structure + Initialize State

3. Entry State Validation

4. Content Completeness Check

Exit Criteria

Automatic Transition