comet-build
Plan, implement, and accept Classic tasks. Use when the user invokes /comet-build or Classic Runtime enters Build or returns to Build for repairs.
- License 许可
- MIT
- 所属仓库
- rpamis/comet
- 最近更新
- 2026-11-15
- Stars
- ★ 3.3k
- Forks
- 314
01 前言 Front Matter
- name
- comet-build
- description
- Plan, implement, and accept Classic tasks. Use when the user invokes /comet-build or Classic Runtime enters Build or returns to Build for repairs.
02 资源文件 2
- 参考文档agents/openai.yaml189 B
- 参考文档reference/compat.md21.6 KB
03 SKILL.md 正文
Comet Phase 3: Plan and Build
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 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
First follow ordinary commands and checks. New and upgraded Runs use platform tools and submit actual reports to the original Run. Automatic upgrades do not restore old check executors. Phase preparation, user choices, task completion, and acceptance requirements remain in force.
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 current valid result's agent.continuation / data.nextAction and bound state. Run comet state next <change-name> --json only on a cold resume, after external state changes, or when necessary information is missing. For data.runtimeFormat: sdk, advance only this Run; the implementation methods, plan content, and reviews are in SDK execution methods; submit state and evidence through this section. data.phase must be build. Reuse valid layout and configuration already in context; use comet state check <change-name> build --json only when they are missing. For nextAction.kind: reconcile, run comet state check <change-name> build --recover --json and establish the original outcome before repeating external work.
First check workflow in the valid configuration or the current nextAction.stepId. For tweak.build.* / workflow: tweak, Immediately execute: Use the Skill tool to load the comet-tweak skill. Skipping this step is prohibited. For hotfix.build.* / workflow: hotfix, Immediately execute: Use the Skill tool to load the comet-hotfix skill. Skipping this step is prohibited. After the skill loads, pass the same change, workspace, phase, Run revision, and continuation and resume its SDK Build step. Do not require a full Design Doc or implementation plan, or repeat Open. Older Runs may still store comet-build as the raw Action reference; route them the same way. After an approved upgrade, use the full path in SDK execution methods when the current step is full.build.*.
- At
full.build.configure, present values, meanings, and confirmation status under Build configuration guidance. Ask only for missing, invalid, or explicitly changed decisions about execution, TDD, and review. Put confirmedbuild_mode,tdd_mode,review_mode,subagent_dispatch, and, when required,direct_overridein a temporary JSON file inside the repository. If the user already explicitly chose this complete configuration, runcomet state propose-build <change-name> --file <configuration-json> --confirmedto save proposal and approval together. Otherwise runcomet state propose-build <change-name> --file <configuration-json>. Only for a remaining pending Wait, savedata.wait.proposalHash, show the actual configuration, and await confirmation under decision-point.md. Then runcomet state decide-build <change-name> --proposal-hash <proposalHash> --choice <approved|rejected>. Propose revised choices after rejection. Reuse an existing pending Wait on recovery without asking again or creating another configuration Action. After saving approval, briefly echo the result and continue without another confirmation to proceed. - At
full.build.plan, create or inspect the plan under SDK execution methods. Refer to the current Design Doc and tasks.md, mapping tasks with<!-- comet-task-authority: <classic-task-authority-ref> -->and<!-- comet-task-ref:<task-id> -->, not another checkbox list. Runcomet state submit-plan <change-name> --plan <plan-ref>. Add--pauseonly if the user explicitly requested a pause after planning. For aplan-readyWait, await an explicit instruction to proceed and use its current hash incomet state continue-plan <change-name> --proposal-hash <proposalHash>. Do not reuse approval after plan or task requirements change. - At
full.build.execute, implement using the chosen method, review tasks or segments, and run relevant checks. Check off the same tasks.md only after actual completion and satisfactory review. Use the sharedstate tasks,state task-complete, andstate checkpointtools for task IDs, completion, and coordination progress; they do not advance the SDK Run. SDK must not call legacycomet handoff --write. Once plan, tasks, and workspace agree, runcomet state complete-build <change-name> --session <builder-execution-ref> --checks <checks-json-file>to enter Verify. Resolve drift before submission.
After each advance, use that result's agent.continuation / data.nextAction. Do not repeat next, select, or check while state is valid and complete; read again only on a cold resume, after external state changes, or for missing information. Load the next Skill only for an action in the next phase; resolve decision, evidence, and reconcile within the current Run.
Use the actual --session <builder-execution-ref> for SDK Build; do not repeat it when already supplied.
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.
Optional change walkthrough
At Build completion and before presenting Verify results, check the project .comet/config.yaml field change_walkthrough (enabled by default; only explicit false disables it). When enabled, read and execute Change walkthrough, use the shared template to generate or update the same walkthrough.html, and provide an opening link. When disabled, skip extra explanation, detailed instructions and rendering; retain the existing summary. Archive preserves existing pages with the materials and links to their actual archived location; it does not generate missing pages, add confirmation or rerun code checks for page updates.
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