comet

Orchestrate OpenSpec and Superpowers into a five-phase development pipeline.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Comet unifies planning, design, build, verify, and archiving into a single automated pipeline, reducing context switching and coordinating multiple sub-skills with guardrails and handoffs.

Core Features & Use Cases

  • OpenSpec + Superpowers dual-star workflow for end-to-end product development
  • Automatic phase detection and dispatch to subcommands
  • Rigorous state management, guard checks, and delta archiving to ensure traceability

Quick Start

Run the /comet command to start automatic phase detection and dispatch through the five phases (open → design → build → verify → archive).

Frequently Asked Questions about comet

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

FAQPage Schema
How do I manage end-to-end development workflows from idea to archive?▼

End-to-end development workflows are managed by orchestrating a five-phase pipeline covering open, design, build, verify, and archive stages. This approach combines planning and execution into a single automated pipeline, reducing context switching by coordinating sub-skills with structured handoffs and rigorous state management.

What is phase detection in automated software development pipelines?▼

Phase detection in automated pipelines automatically identifies the current stage of a project and dispatches tasks to appropriate subcommands. It enforces strict state management and guard checks to ensure safe, auditable transitions between design, build, and verification phases.

How do I ensure traceable progress and safe handoffs between development phases?▼

Traceable progress and safe handoffs are ensured through rigorous state management, guard checks, and delta-archiving. Structured transitions between planning, design, and build phases provide an auditable workflow that tracks changes and prevents unauthorized phase advancements.

Does this development pipeline require any specific dependencies to run?▼

This development pipeline does not list any specific external dependencies to run. It operates by coordinating internal sub-skills through scripts, applying automated phase detection and dispatch without requiring additional external tools or frameworks.

What is the best way to unify planning and execution in software engineering?▼

Unifying planning and execution is best achieved by combining WHAT and HOW specifications into a dual-star workflow. This method orchestrates product development from initial design through final archiving, using automatic phase detection to reduce context switching and coordinate multiple sub-skills.

When should I not use an automated phase-guard workflow for my project?▼

Automated phase-guard workflows may not be suitable for projects requiring highly flexible, non-linear development processes. The strict state management, rigorous guards, and structured handoffs are designed for traceable, auditable pipelines and might constrain rapid prototyping or ad-hoc coding tasks.