@rpamis/comet

@rpamis/comet

 ██████╗ ██████╗ ███╗   ███╗███████╗████████╗
██╔════╝██╔═══██╗████╗ ████║██╔════╝╚══██╔══╝
██║     ██║   ██║██╔████╔██║█████╗     ██║
██║     ██║   ██║██║╚██╔╝██║██╔══╝     ██║
╚██████╗╚██████╔╝██║ ╚═╝ ██║███████╗   ██║
 ╚═════╝ ╚═════╝ ╚═╝     ╚═╝╚══════╝   ╚═╝

中文版：README-zh.md B站视频介绍

OpenSpec + Superpowers dual-star development workflow — one command from idea to archive.

OpenSpec handles WHAT (outlines, proposals, spec lifecycle, archiving).

Superpowers handles HOW (technical design, planning, execution, wrap-up).

Comet chains both into a five-phase automated pipeline.

Why Comet

OpenSpec excels at managing requirements, creating proposals, managing Spec lifecycles, and archiving, but its proposals and tasks lack the detail of Superpowers brainstorming.

Superpowers generates Spec documents after brainstorming, but these documents typically lack stateful design — after completing requirements, Specs only have tasks checked off in the document, and Agents even forget to check them off. This causes the Agent to re-examine documents and project code to verify on resumption, wasting many tokens.

Comet combines the strengths of both, integrating the core workflow into 5 phases

The main entry /comet supports current Spec state detection, suitable for long tasks — after completing and closing CC midway, just /comet continue and Comet will automatically read the active Spec (lists multiple for selection), dynamically identify which phase is currently executing, and continue.

At the same time, Comet provides full Spec lifecycle management. During execution, it links OpenSpec change/spec artifacts with Superpowers design and planning documents, then automates handoff, state updates, validation, and archive sync so users do not have to repeatedly remind the Agent to keep documents synchronized and connected.

What You'll Learn

Many excellent Skill projects exist in the current Skill market, but they generally have preference issues — users may only like some features. For example, when using both OpenSpec and Superpowers, one might only use OpenSpec's Spec management capabilities, but prefer Superpowers' TDD-driven approach for coding.

Long-term Skill users know these capabilities can be freely combined, but exactly how to do so still requires real practice. The Comet project can serve as a reference:

• How to reliably trigger nested Skills — Not letting the Agent rely on document descriptions to perform "look-alike Skill trigger" operations (like writing files based on Skill descriptions), but truly triggering Skills (key feature: Skill trigger prints on CC). Comet triggers many capabilities from OpenSpec and Superpowers. How is this Prompt written?

• How to make combined Skills flow automatically across phases — Not relying on manual intervention. Comet's 5-phase flow can automatically trigger Skills for the core process except for necessary user choices, while the state machine also protects state transition reliability.

• How to turn the Spec lifecycle into a resumable workflow — Comet links OpenSpec change/spec artifacts with Superpowers design and planning documents, then records phase, execution mode, verification results, and archive status in .comet.yaml, so the Agent can resume after interruption instead of rereading documents and guessing progress.

• How to turn document synchronization from "user reminders" into automation — Comet puts handoff, state updates, validation, and archive sync into scripted flows, reducing repeated prompts like "remember to update the design doc", "remember to sync the spec", and "remember to archive the change".

• How to design guard conditions that Agents can execute — Comet does not simply trust the Agent saying "done" at phase exits. Scripts such as comet-guard.sh, comet-yaml-validate.sh, and comet-state.sh check tasks, state fields, verification evidence, and archive conditions before allowing the workflow to advance.

• How to distribute and install Skills across platforms — Comet supports multiple AI coding platforms, project/global installation, Chinese/English Skill choices, and platform-specific directory differences such as Antigravity using different project-level and global paths. It can be a reference for CLI installers and Skill package structure.

• How to turn shell scripts into Agent workflow infrastructure — Comet's scripts need to work across macOS, Linux, and Windows Git Bash while handling hashes, YAML fields, state machines, and archive flows. It shows how to move fragile workflow control out of scattered Prompt text and into testable, reusable tools.

Install

npm install -g @rpamis/comet

Quick Start

cd your-project
comet init

comet init will:

• Prompt you to select AI platforms (auto-detects existing configs)
• Choose install scope: project-level (current directory) or global (home directory)
• Select language for Comet skills: English or 中文
• Install OpenSpec skills
• Install Superpowers skills
• Deploy Comet skills (in your chosen language) to selected platforms
• Create docs/superpowers/specs/ and docs/superpowers/plans/ working directories for project-scope installs

[!TIP] update version

comet update or npm install -g @rpamis/comet@latest to get the latest features and fixes.

Support for OpenClaw and Hermes, and other AI platforms

npx skills add rpamis/comet

Screenshots

Auto-install OpenSpec & Superpowers, one-click dev environment setup

Multi-phase Skill entry, auto-detects current Spec stage, auto-triggers core flow, manual review at key nodes

Commands

comet init [path] — Initialize Comet workflow

Initializes OpenSpec, Superpowers, and Comet skills for selected AI coding platforms.

Option	Description
--yes	Non-interactive mode, auto-select detected platforms (or all if none detected)
--scope <scope>	Install scope: project or global
--skip-existing	Skip already installed components
--overwrite	Overwrite already installed components
--json	Output structured JSON

When multiple existing components are found on the same platform, interactive init offers one bulk choice: overwrite all, skip all, or choose per component.

comet status [path] — Show active changes and next workflow command

Displays active changes, task progress, and the recommended next Comet workflow command.

Option	Description
--json	Output active changes with nextCommand

comet doctor [path] — Diagnose Comet installation health

Checks project/global installation health, working directories, installed skills, scripts, and Comet state files.

Option	Description
--json	Output structured diagnostic results
--scope <scope>	Diagnose auto, project, or global scope (default: auto)

comet update [path] — Update Comet package and skills

Updates the npm package and refreshes installed Comet skills in detected project/global targets.

Option	Description
--json	Output npm and skill update results as JSON
--language <lang>	Override detected skill language (en, zh)
--scope <scope>	Update only global or project scope

Command	Description
comet --help	Show help
comet --version	Show version

Supported Platforms

comet init supports 28 AI coding platforms:

View full platform list

Platform	Skills Dir	Platform	Skills Dir
Claude Code	.claude/	Cursor	.cursor/
Codex	.codex/	OpenCode	.opencode/
Windsurf	.windsurf/	Cline	.cline/
RooCode	.roo/	Continue	.continue/
GitHub Copilot	.github/	Gemini CLI	.gemini/
Amazon Q Developer	.amazonq/	Qwen Code	.qwen/
Kilo Code	.kilocode/	Auggie	.augment/
Kiro	.kiro/	Lingma	.lingma/
Junie	.junie/	CodeBuddy	.codebuddy/
CoStrict	.cospec/	Crush	.crush/
Factory Droid	.factory/	iFlow	.iflow/
Pi	.pi/	Qoder	.qoder/
Antigravity	.agents/	Bob Shell	.bob/
ForgeCode	.forge/	Trae	.trae/

Skills

After comet init, three groups of skills are installed to the selected platform's skills/ directory:

Comet Skills

View Comet skills

Skill	Description
/comet	Main entry — auto-detects phase and dispatches to sub-commands
/comet-open	Phase 1: Open a change (proposal, design, task breakdown)
/comet-design	Phase 2: Deep design (brainstorming, Design Doc)
/comet-build	Phase 3: Plan and build (implementation plan, code commits)
/comet-verify	Phase 4: Verify and finish (testing, verification report)
/comet-archive	Phase 5: Archive (delta spec sync, status annotation)
/comet-hotfix	Preset: Quick bug fix (skips brainstorming)
/comet-tweak	Preset: Small change (skips brainstorming and full plan)

Guard & Automation Scripts

View script list

Script	Purpose
comet-guard.sh	Phase transition guard — validates exit conditions, --apply auto-updates .comet.yaml
comet-handoff.sh	Design handoff — generates deterministic context packages from OpenSpec artifacts with SHA256 tracing
comet-archive.sh	One-command archive — validates state, syncs specs, moves to archive, updates status
comet-yaml-validate.sh	Schema validator — validates .comet.yaml structure and field values
comet-state.sh	Unified state management — init/set/get/check/scale, agents' exclusive YAML interface

OpenSpec Skills

Spec lifecycle management: propose, explore, sync, verify, archive, and more.

Superpowers Skills

Development methodology: brainstorming, TDD, subagent-driven development, code review, plan writing, and more.

Workflow

/comet
  ↓ auto-detect
/comet-open  -->  /comet-design  -->  /comet-build  -->  /comet-verify  -->  /comet-archive
(OpenSpec)         (Superpowers)       (Superpowers)       (Both)           (OpenSpec)

/comet-hotfix (preset path, skips brainstorming)
  open  -->  build  -->  verify  -->  archive

/comet-tweak (preset path, skips brainstorming and full plan)
  open  -->  lightweight build  -->  light verify  -->  archive

Five Phases

Phase	Command	Owner	Artifacts
1. Open	/comet-open	OpenSpec	proposal.md, design.md, tasks.md
2. Deep Design	/comet-design	Superpowers	Design Doc, delta spec
3. Plan & Build	/comet-build	Superpowers	Implementation plan, code commits
4. Verify & Finish	/comet-verify	Both	Verification report, branch handling
5. Archive	/comet-archive	OpenSpec	delta→main spec sync, archive

Core Principles

• Brainstorming is non-skippable — every change must go through deep design (except hotfix/tweak)
• Delta specs are living documents — freely editable during Phase 3, synced at archive
• Keep tasks.md in sync — check off each task as completed
• Commit frequently — one commit per task, message reflects design intent
• Verify before archive — /comet-verify must pass before /comet-archive

State Management

Comet uses a decoupled state architecture with separate YAML files:

File	Owner	Purpose
.openspec.yaml	OpenSpec	Spec lifecycle, change metadata
.comet.yaml	Comet	Workflow phase, execution mode, verification status

All states and execution phases are updated via scripts, and each phase verifies that tasks are truly complete before advancing. Compared to storing complex state rules only in Skill text, this script-backed state machine gives Comet more reliable phase transitions, correct YAML, and easier breakpoint recovery; agents can read the current Spec situation through Comet's built-in commands.

View key .comet.yaml fields

Key Fields in .comet.yaml:

workflow: full
phase: build
build_mode: subagent-driven-development
isolation: branch
verify_mode: null
design_doc: docs/superpowers/specs/YYYY-MM-DD-topic-design.md
plan: docs/superpowers/plans/YYYY-MM-DD-feature.md
verify_result: pending
verification_report: null
branch_status: pending
verified_at: null
archived: false
direct_override: false
build_command: null
verify_command: null
handoff_context: openspec/changes/<name>/.comet/handoff/design-context.json
handoff_hash: <sha256>

In full workflow, build_mode, isolation, and verify_mode may temporarily be null; build_mode and isolation must be resolved before build → verify. verification_report stays null until verification writes a report, and verify-pass requires that report to exist plus branch_status: handled. Fields after archived in the example are optional or script-derived: direct_override is only needed for full-workflow direct builds, project commands may be absent unless configured, and handoff_context / handoff_hash are recorded by comet-handoff.sh before leaving design. Projects can configure build_command / verify_command in the change or repo root, and guard will run those commands first and print failure output.

Reliability Features

Comet ensures agent execution reliability through automated state transitions:

View reliability features

• Entry Verification — Each phase validates preconditions before execution

  • Checks file existence, state consistency, and phase transitions
  • Outputs [HARD STOP] with actionable suggestions if validation fails

• Automated State Transitions — comet-guard.sh --apply updates .comet.yaml automatically

  • All phase transitions (open → design/build → verify → archive) use guard --apply
  • No manual state editing required — eliminates write-verification errors
  • comet-state.sh is the agents' exclusive interface for state operations
  • Guard and archive scripts use comet-state.sh internally for state management

• Schema Validation — comet-yaml-validate.sh ensures data integrity

  • Validates required and optional fields
  • Validates enum values, including direct_override
  • Validates design_doc, plan, and handoff_context paths exist, plus handoff_hash format
  • Detects unknown/typos fields

• Build Decision Enforcement — Guard and state transitions both block skipped build choices

  • isolation must be branch or worktree
  • build_mode must be selected before leaving build
  • Full workflow build_mode: direct requires direct_override: true

• Verification Evidence — Guard enforces proof before phase advance

  • verify-pass transition requires verification_report pointing to an existing report file
  • branch_status must be handled before verify can pass
  • Guard checks verification_report exists and branch_status=handled as hard prerequisites
  • Prevents false phase advances when verification or branch handling was skipped

• Archive Automation — comet-archive.sh handles the full archive flow in one command

  • Validates entry state, syncs delta specs to main specs
  • Annotates design doc and plan frontmatter
  • Moves change to archive directory and updates archived: true
  • Supports --dry-run for preview

Project Structure

your-project/
├── .claude/skills/              # Platform skills dir (Comet + OpenSpec + Superpowers)
│   ├── comet/SKILL.md
│   │   └── scripts/
│   │       ├── comet-guard.sh       # Phase transition guard (--apply auto-updates state)
│   │       ├── comet-handoff.sh     # Design handoff (OpenSpec → Superpowers context tracing)
│   │       ├── comet-archive.sh     # One-command archive automation
│   │       ├── comet-yaml-validate.sh # Schema validator
│   │       └── comet-state.sh       # Unified state management (init/set/get/check/scale)
│   ├── comet-*/SKILL.md
│   ├── openspec-*/SKILL.md
│   └── brainstorming/SKILL.md
├── openspec/                    # OpenSpec — WHAT
│   ├── config.yaml
│   └── changes/
│       └── <name>/
│           ├── .openspec.yaml       # OpenSpec state
│           ├── .comet.yaml          # Comet workflow state (decoupled)
│           ├── proposal.md
│           ├── design.md
│           ├── specs/<capability>/spec.md
│           └── tasks.md
└── docs/superpowers/            # Superpowers — HOW
    ├── specs/                   # Design documents
    └── plans/                   # Implementation plans

Development

See CONTRIBUTING.md for development setup, commit conventions, PR process, and guidance for adding platforms or skills.

See CHANGELOG.md for version history and updates.

Roadmap

Track our development progress and upcoming features on the Comet Roadmap.

Star History

License

MIT

Reference

LINUX DO - 新的理想型社区