comet-design
Complete the Classic technical design and obtain user confirmation. Use when the user invokes /comet-design or Classic Runtime enters Design.
- License 许可
- MIT
- 所属仓库
- rpamis/comet
- 最近更新
- 2026-11-15
- Stars
- ★ 3.3k
- Forks
- 314
01 前言 Front Matter
- name
- comet-design
- description
- Complete the Classic technical design and obtain user confirmation. Use when the user invokes /comet-design or Classic Runtime enters Design.
02 资源文件 2
- 参考文档agents/openai.yaml187 B
- 参考文档reference/compat.md14.2 KB
03 SKILL.md 正文
Comet Phase 2: Design
On first entering a phase, handing off to a new Agent, or restoring context, read and follow Task Context and Artifact Language. Prefer the current continuation or claimed Action's contextRequest; do not retrieve repeatedly during uninterrupted work in the same phase.
After the entry returns layout, follow the shared phase entry when receiving a phase for the first time or when its binding changes. Reuse the valid layout; do not run an extra root show first. When edits require judgement, load edit continuation through the shared entry.
SDK Run path
On first entering the current SDK phase, handing off to a new Agent, or restoring context, read phase entry and recovery and the current phase's section in that reference. Reuse them when already available and still valid in this session. Continue with the phase below; recovery routes based on nextAction.kind apply only to older responses without a continuation mode.
Reuse the latest valid response for the same change, workspace, and Run: agent.continuation, data.nextAction, phase, revision, and path summaries. Run comet state next <change-name> --json only for cold recovery, workspace or external state changes, a stale response version, or missing information needed for the current step; loading the next Skill is not a reason to query again. Runtime still validates current versions and evidence on writes; cached context cannot bypass checks or approval. For data.runtimeFormat: sdk, use this section for state changes; use the Design section of SDK execution methods for exploration, questions, and formal document requirements. data.phase must be design. If Build has begun, return to its entry. For nextAction.kind: reconcile, run comet state check <change-name> design --recover --json and establish the claimed Action's original outcome before proposing or redispatching.
- At
full.design.handoff, reuse layout and references from the current response; runcomet state check <change-name> design --jsononly when they are missing. Read the current OpenSpec proposal, tasks, delta specs, and relevant existing design.md. Develop candidate solutions under the Design section of SDK execution methods and keepbrainstorm-summary.mdcurrent, marking unapproved content as a candidate. There is no SDK handoff packet yet; do not call legacycomet handoff ... --writeor substitute a handwritten summary. - For a needed Spec Patch, explain it and obtain explicit agreement under the Design confirmation rules in SDK execution methods before editing the delta spec. Reclarify material scope changes. When sources are stable, run
comet state propose-design <change-name> --proposal "<candidate-summary>"; the summary must cover the proposed design, tradeoffs, risks, and Spec Patch. Savedata.wait.proposalHashas<proposalHash>. This creates the traceable handoff. Usedata.configuration.handoffContextfrom the proposal response, queryingcomet state next <change-name> --jsononly if it is missing, and verify the Markdown packet matches the candidate and source files. Reuse an existing pending Wait on recovery. - Check current design against existing authority under
comet-classic/reference/decision-point.md. Record the basis and continue when authority covers it. When a new decision is needed, explain the effects under reconfirmation after requirement changes, present the current proposal, and wait for the answer. Use the current proposal hash withcomet state decide-design <change-name> --proposal-hash <proposalHash> --choice <approved|rejected>: chooseapprovedwhen valid approval or delegated authority covers the proposal; chooserejectedand propose again when the user requests changes; retain the Wait when deferred. If source changes invalidate an old hash, inspect the differences and record the decision against the current proposal rather than reusing an expired hash. - After approval, write the single Design Doc with required frontmatter. If recovery already points to
full.design.document, continue here. Run directlycomet state complete-design <change-name> --design-doc <design-doc-ref> --approval-hash <proposalHash>. On failure preserve the Run and address the specific cause. Runtime synchronizes the actual state file; the Agent does not manually advance its phase. Route to the Build Action and continuation from the same successful response; runcomet state next <change-name> --jsononly if continuation information is missing.
Compat path
The remaining original Runtime steps apply only to runtimeFormat: compat. Read Compat operations and continue its current phase. SDK does not load that reference.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes