comet-build

Creates implementation plans and executes tasks for the Comet build phase.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill comet-build-shrek-abaper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-build
Source: https://github.com/shrek-abaper/sap-nexus-agent/tree/main/.comet/skills/skills/comet-build
Command: npx skills add https://github.com/shrek-abaper/sap-nexus-agent --skill comet-build-shrek-abaper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns an approved design document into a concrete implementation plan and then executes every task with enforced workflow governance, eliminating ad-hoc coding sessions that lose track of state, branches, and review requirements. ## Core Features & Use Cases - Plan Creation via Subagent: Offloads implementation planning to a subagent using the Superpowers writing-plans skill, producing a plan file with change, design-doc, and base-ref metadata. - Governed Execution Configuration: Collects workspace isolation (current branch, new branch, or git worktree), execution method (subagent-driven-development or executing-plans), TDD mode, and code review mode in one joint decision, enforced by comet state guards. - Recovery and Idempotency: Supports safe resume after context compaction or interruption by parsing tasks.md checkboxes and verifying entry state with comet CLI commands. - Use Case: After finishing a design doc for a new feature, invoke /comet-build to generate the plan, choose a feature branch with TDD and standard review, and let subagents implement each task until the build guard passes. ## Quick Start Invoke /comet-build after the design phase completes and confirm the plan, isolation, execution, TDD, and review settings when prompted.

Frequently Asked Questions about comet-build

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

FAQPage Schema
How do I run the Comet build phase after design?▼

Invoke /comet-build once the design doc exists and an active change is present. The skill verifies entry state with comet state check, creates a plan via a subagent, then asks you to confirm isolation, execution method, TDD, and review mode before executing tasks.

How do I resume an interrupted comet-build session?▼

Rerun /comet-build and it performs entry verification and context recovery, then parses tasks.md checkboxes to resume from the first unchecked task. Already-committed tasks are never re-committed, making the build phase idempotent.

What is the difference between executing-plans and subagent-driven-development?▼

executing-plans runs tasks directly in the main session and suits simple tasks with few dependencies. subagent-driven-development dispatches each task to an isolated implementer subagent and is recommended when there are three or more tasks or higher complexity.

Can comet-build work without creating a new branch?▼

Yes, choosing the current isolation option binds the existing Git branch via comet state set isolation current. It fails on a detached HEAD, so you must check out a real branch first for auditable branch binding.

Why does the build to verify guard fail?▼

The guard fails when required state fields are missing: isolation, build_mode, tdd_mode, or review_mode not written, subagent_dispatch not confirmed for subagent-driven-development, or build evidence not recorded. Run the failing command output and set the missing fields before retrying.