comet-design

Generates deep technical Design Docs from OpenSpec change artifacts via scripted handoff and brainstorming.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill comet-design-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-design
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/comet-design
Command: npx skills add https://github.com/JhonMA82/api-starter --skill comet-design-jhonma82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It bridges the gap between a high-level OpenSpec change proposal and implementation by producing a deep technical Design Doc with traceable, script-generated context instead of ad-hoc agent summaries. ## Core Features & Use Cases - Script-Generated Handoff Packages: Runs comet handoff to create hash-traceable design-context or spec-context packages from proposal.md, design.md, tasks.md, and delta specs. - Guided Brainstorming with Blocking Confirmation: Loads the Superpowers brainstorming skill, iterates on technical approach, risks, and test strategy, and blocks until the user explicitly confirms the design proposal. - State and Guard Enforcement: Records the Design Doc path in .comet.yaml, regenerates handoff hashes when delta specs change, and runs comet guard design --apply to auto-transition to the build phase. - Use Case: After drafting an OpenSpec change for a new API capability, invoke this phase to produce a confirmed, frontmatter-compliant Design Doc under docs/superpowers/specs/ before any build work begins. ## Quick Start Invoke /comet-design for the active change and follow the brainstorming flow to confirm and persist the technical Design Doc.

Frequently Asked Questions about comet-design

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

FAQPage Schema
How do I create a technical Design Doc from an OpenSpec change?▼

Run the comet-design phase with an active change containing proposal.md, design.md, and tasks.md. It generates a script-built handoff package, runs guided brainstorming, and writes the confirmed Design Doc to docs/superpowers/specs/.

What is the difference between the open-phase design.md and the Design Doc?▼

The open-phase design.md captures the high-level solution framework such as architecture direction and approach selection. The Design Doc is its deep technical refinement covering detailed implementation design, technical risks, test strategy, and edge cases.

Can I skip the brainstorming step in the comet design phase?▼

No. Loading the Superpowers brainstorming skill is mandatory, and proceeding without it is prohibited. If the skill is unavailable, the process stops and prompts you to install or enable Superpowers skills.

What happens if the OpenSpec delta spec is missing acceptance scenarios?▼

You may propose Spec Patches limited to supplementing acceptance scenarios, correcting ambiguity, or adding boundary conditions, written back to the delta spec. Major changes are flagged as design findings and returned to brainstorming for confirmation.

How does context compaction recovery work during the design phase?▼

The agent incrementally updates brainstorm-summary.md as a recovery checkpoint during brainstorming. After compaction, it reloads that file plus the handoff context files to resume brainstorming or Design Doc creation.

When should I not use the comet-design skill?▼

Do not use it unless explicitly invoked as /comet-design or routed by the root Comet runtime, and only when an active change exists without an existing Design Doc. It is not a standalone design writing tool.