comet-native

Orchestrates resumable long-running coding changes through Shape, Build, Verify, and Archive phases.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-native
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-native
Source: https://github.com/rpamis/comet/tree/main/assets/skills/comet-native
Command: npx skills add https://github.com/rpamis/comet --skill comet-native

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Long-running coding tasks lose context, progress, and verification state when sessions end or devices change. This Skill drives the Comet Native workflow, which persists requirements, target specifications, progress, and verification conclusions on disk so a change can be resumed reliably across sessions and machines.

Core Features & Use Cases

  • Resumable change lifecycle: Start or resume a change via comet native status, then advance through Shape, Build, Verify, and Archive phases using Runtime-returned continuations.
  • Structured clarification and specs: Maintains a decision tree, records confirmed decisions in brief.md, and writes complete target specifications with observable acceptance criteria.
  • Bounded Build-Verify loop: The Builder submits candidates with a review summary, and a fresh read-only Verifier marks every acceptance scenario as passed, failed, or blocked before Archive.
  • Supervisor decomposition: Large requirements can be split into child changes with dependency tracking, multi-session or single-session coordination, and final integration verification.
  • Use Case: Ask the agent to implement a multi-day feature; the workflow stores state in comet-state.yaml, so after an interruption you simply resume and the Runtime tells the agent exactly which phase and action to continue.

Quick Start

Ask the agent to start a Comet Native change for your feature request, for example by saying "use /comet-native to start a change that adds OAuth login to the app".

Frequently Asked Questions about comet-native

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

FAQPage Schema
How do I resume an interrupted coding task with Comet Native?

Run comet native status <change-name> --json to query the persisted state, then enter the returned workspace and follow the Runtime continuation. The workflow state lives in comet-state.yaml, so progress survives session restarts and device changes.

How does the Build and Verify loop work in Comet Native?

The Builder implements the change and submits a handoff with a passing review summary. A fresh read-only Verifier then marks every acceptance scenario as passed, failed, or blocked, and failed items return to Build until all checks pass.

Can Comet Native split a large requirement into subtasks?

Yes, a Supervisor Change can decompose work into child changes tracked in children.yaml with dependencies and acceptance ownership. Coordination runs either multi-session with independent agents or single-session in order, followed by final integration verification.

What happens if the comet CLI command is unavailable?

The Skill treats a missing comet native command as an incomplete Comet installation and stops. All workflow advancement goes through the public CLI on PATH, and comet native <command> --help is authoritative for arguments.

When should I not decompose a requirement into child changes?

Avoid decomposition when the goal is tightly coupled, repeatedly edits one core area, or coordination costs more than the split saves. Text length and task count alone must not trigger decomposition.