skills.rest
rpamis
rpamisOFFICIAL
Explore all skills by this author →
GitHub

comet-classic

Orchestrates OpenSpec and Superpowers phases for structured coding change workflows.

2.9k|284|Updated May 14, 2026
Search Tags:#change management#coding workflow#openSpec#phase detection#subagent dispatch#State Machine#Workflow orchestration
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-classic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-classic
Source: https://github.com/rpamis/comet/tree/main/assets/skills/comet-classic
Command: npx skills add https://github.com/rpamis/comet --skill comet-classic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Long-running coding changes lose track of phase, state, and user decisions when context is compressed or sessions restart. This Skill routes every request through a deterministic open → design → build → verify → archive pipeline backed by a .comet.yaml state file, so work resumes correctly and no required user decision point is skipped.

Core Features & Use Cases

  • Automatic phase detection and resume: Probes the repository with comet resume-probe, reads .comet.yaml, and routes to the correct sub-skill (/comet-open, /comet-design, /comet-build, /comet-verify, /comet-archive) without trusting conversation history.
  • Intent-based workflow routing: Classifies requests into full, hotfix, or tweak workflows using a CometIntentFrame and runtime scorer, with blocking user decision points at scope, workspace, build-mode, and archive confirmations.
  • State machine enforcement: Guards phase transitions with hard constraints on isolation mode, build mode, TDD mode, and review mode, plus dirty-worktree attribution and context-recovery protocols.
  • Use Case: A developer returns to a half-finished feature after a week; the Skill detects the active change, recovers the exact build-phase checkpoint, and continues subagent-dispatched task execution from where it stopped.

Quick Start

Ask the assistant to start or resume a Comet Classic change for your feature request, for example by invoking /comet-classic with a short description of the change you want to make.

Frequently Asked Questions about comet-classic

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

FAQPage Schema
How do I resume an interrupted Comet Classic change?▼

Run /comet-classic or let the ambient resume probe detect the active change via `comet resume-probe`. The Skill re-reads the change's .comet.yaml state file and routes to the correct phase skill instead of trusting conversation history.

How does Comet Classic choose between full, hotfix, and tweak workflows?▼

It builds a CometIntentFrame from your request and active changes, then the runtime scorer routes it. Bug fixes on existing behavior favor hotfix, lightweight single-change edits favor tweak, and new capabilities, API, or schema changes favor full.

What is the difference between OpenSpec and Superpowers in this workflow?▼

OpenSpec handles the WHAT: proposals, delta specs, task lists, and archiving. Superpowers handles the HOW: brainstorming, design docs, implementation plans, and subagent-driven execution. Comet coordinates both through one state machine.

Can Comet Classic skip user confirmation at decision points?▼

No. Decision points such as workflow selection, design confirmation, build-mode choice, and archive delivery are blocking. The Skill must present explicit options and wait for the user's choice before writing state or continuing.

What happens when the worktree has uncommitted changes during resume?▼

The dirty-worktree protocol attributes each diff as belonging to the current change, unrelated, or unclear. Matching changes are incorporated as evidence; unrelated or ambiguous changes pause the workflow for a user decision before any phase advances.

When should I upgrade a hotfix or tweak to the full workflow?▼

Upgrade when qualitative signals appear: cross-module changes, new capabilities, schema or public API changes, or deep architecture issues. The `preset-escalate` transition rewinds the change to the design phase so a full design doc is produced.

Related Skills

Explore More Software Engineering Skills→
rpamisrpamis
2.7k

comet-build

Generate executable build plans from OpenSpec designs and select execution methods.

Official
Advanced
coreoscoreos
231

prepare-release

Create a pre-release branch, update Cargo dependencies, draft release notes, and open a pull request.

Official
Intermediate
KirillKlemKirillKlem
1

minimal-validation

Run the smallest credible set of tests for code changes.

Community
Intermediate
ssd-mkdocs-platformssd-mkdocs-platform
1

openspec-sync-specs

Merge delta specs into main specs for ADDED, MODIFIED, REMOVED, and RENAMED changes.

Official
Advanced