[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72VZJ406P402SFKPWQ75H9G":3,"skill-same:01M72VZJ406P402SFKPWQ75H9G":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M72VZJ406P402SFKPWQ75H9G","comet-build",null,"Plan, implement, and accept Classic tasks. Use when the user invokes \u002Fcomet-build or Classic Runtime enters Build or returns to Build for repairs.","rpamis\u002Fcomet","rpamis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153429891?v=4","01M72VXBR7EQYMM7KN8C19244V","01M72VXBRYC06QG0ZH0JBGV09V",3298,"MIT","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fcomet-build\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: comet-build\ndescription: 'Plan, implement, and accept Classic tasks. Use when the user invokes \u002Fcomet-build or Classic Runtime enters Build or returns to Build for repairs.'\n---\n\n# Comet Phase 3: Plan and Build\n\nOn first entering a phase, handing off to a new Agent, or restoring context, read and follow [Task Context and Artifact Language](..\u002Fcomet-classic\u002Freference\u002Fscripts.md#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.\n\nAfter entry returns layout, follow the [shared phase entry](..\u002Fcomet-classic\u002Freference\u002Fscripts.md#shared-phase-entry) when receiving a phase for the first time or when its binding changes. Reuse the valid [layout](..\u002Fcomet-classic\u002Freference\u002Fclassic-layout.md); do not run an extra root show first. When edits require judgement, load edit continuation through the shared entry.\n\n## SDK Run path\n\nFirst follow [ordinary commands and checks](..\u002Fcomet\u002Freference\u002Fplatform-execution.md). 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.\n\nOn first entering the current SDK phase, handing off to a new Agent, or restoring context, read [phase entry and recovery](..\u002Fcomet-classic\u002Freference\u002Fsdk-methods.md#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.\n\nReuse the current valid result's `agent.continuation` \u002F `data.nextAction` and bound state. Run `comet state next \u003Cchange-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 \u003Cchange-name> build --json` only when they are missing. For `nextAction.kind: reconcile`, run `comet state check \u003Cchange-name> build --recover --json` and establish the original outcome before repeating external work.\n\nFirst check `workflow` in the valid configuration or the current `nextAction.stepId`. For `tweak.build.*` \u002F `workflow: tweak`, **Immediately execute:** Use the Skill tool to load the comet-tweak skill. Skipping this step is prohibited. For `hotfix.build.*` \u002F `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.*`.\n\n1. At `full.build.configure`, present values, meanings, and confirmation status under [Build configuration guidance](..\u002Fcomet-classic\u002Freference\u002Fsdk-methods.md#build). Ask only for missing, invalid, or explicitly changed decisions about execution, TDD, and review. Put confirmed `build_mode`, `tdd_mode`, `review_mode`, `subagent_dispatch`, and, when required, `direct_override` in a temporary JSON file inside the repository. If the user already explicitly chose this complete configuration, run `comet state propose-build \u003Cchange-name> --file \u003Cconfiguration-json> --confirmed` to save proposal and approval together. Otherwise run `comet state propose-build \u003Cchange-name> --file \u003Cconfiguration-json>`. Only for a remaining pending Wait, save `data.wait.proposalHash`, show the actual configuration, and await confirmation under decision-point.md. Then run `comet state decide-build \u003Cchange-name> --proposal-hash \u003CproposalHash> --choice \u003Capproved|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.\n2. 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 `\u003C!-- comet-task-authority: \u003Cclassic-task-authority-ref> -->` and `\u003C!-- comet-task-ref:\u003Ctask-id> -->`, not another checkbox list. Run `comet state submit-plan \u003Cchange-name> --plan \u003Cplan-ref>`. Add `--pause` only if the user explicitly requested a pause after planning. For a `plan-ready` Wait, await an explicit instruction to proceed and use its current hash in `comet state continue-plan \u003Cchange-name> --proposal-hash \u003CproposalHash>`. Do not reuse approval after plan or task requirements change.\n3. 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 shared `state tasks`, `state task-complete`, and `state checkpoint` tools for task IDs, completion, and coordination progress; they do not advance the SDK Run. SDK must not call legacy `comet handoff --write`. Once plan, tasks, and workspace agree, run `comet state complete-build \u003Cchange-name> --session \u003Cbuilder-execution-ref> --checks \u003Cchecks-json-file>` to enter Verify. Resolve drift before submission.\n\nAfter each advance, use that result's `agent.continuation` \u002F `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.\nUse the actual `--session \u003Cbuilder-execution-ref>` for SDK Build; do not repeat it when already supplied.\n\n## Compat path\n\nThe remaining original Runtime steps apply only to `runtimeFormat: compat`. Read [Compat operations](reference\u002Fcompat.md) and continue its current phase. SDK does not load that reference.\n\n## Optional change walkthrough\n\nAt Build completion and before presenting Verify results, check the project `.comet\u002Fconfig.yaml` field `change_walkthrough` (enabled by default; only explicit `false` disables it). When enabled, read and execute [Change walkthrough](..\u002Fcomet\u002Freference\u002Fchange-walkthrough.md), 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.\n","# Comet Phase 3: Plan and Build\n\nOn first entering a phase, handing off to a new Agent, or restoring context, read and follow [Task Context and Artifact Language](..\u002Fcomet-classic\u002Freference\u002Fscripts.md#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.\n\nAfter entry returns layout, follow the [shared phase entry](..\u002Fcomet-classic\u002Freference\u002Fscripts.md#shared-phase-entry) when receiving a phase for the first time or when its binding changes. Reuse the valid [layout](..\u002Fcomet-classic\u002Freference\u002Fclassic-layout.md); do not run an extra root show first. When edits require judgement, load edit continuation through the shared entry.\n\n## SDK Run path\n\nFirst follow [ordinary commands and checks](..\u002Fcomet\u002Freference\u002Fplatform-execution.md). 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.\n\nOn first entering the current SDK phase, handing off to a new Agent, or restoring context, read [phase entry and recovery](..\u002Fcomet-classic\u002Freference\u002Fsdk-methods.md#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.\n\nReuse the current valid result's `agent.continuation` \u002F `data.nextAction` and bound state. Run `comet state next \u003Cchange-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 \u003Cchange-name> build --json` only when they are missing. For `nextAction.kind: reconcile`, run `comet state check \u003Cchange-name> build --recover --json` and establish the original outcome before repeating external work.\n\nFirst check `workflow` in the valid configuration or the current `nextAction.stepId`. For `tweak.build.*` \u002F `workflow: tweak`, **Immediately execute:** Use the Skill tool to load the comet-tweak skill. Skipping this step is prohibited. For `hotfix.build.*` \u002F `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.*`.\n\n1. At `full.build.configure`, present values, meanings, and confirmation status under [Build configuration guidance](..\u002Fcomet-classic\u002Freference\u002Fsdk-methods.md#build). Ask only for missing, invalid, or explicitly changed decisions about execution, TDD, and review. Put confirmed `build_mode`, `tdd_mode`, `review_mode`, `subagent_dispatch`, and, when required, `direct_override` in a temporary JSON file inside the repository. If the user already explicitly chose this complete configuration, run `comet state propose-build \u003Cchange-name> --file \u003Cconfiguration-json> --confirmed` to save proposal and approval together. Otherwise run `comet state propose-build \u003Cchange-name> --file \u003Cconfiguration-json>`. Only for a remaining pending Wait, save `data.wait.proposalHash`, show the actual configuration, and await confirmation under decision-point.md. Then run `comet state decide-build \u003Cchange-name> --proposal-hash \u003CproposalHash> --choice \u003Capproved|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.\n2. 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 `\u003C!-- comet-task-authority: \u003Cclassic-task-authority-ref> -->` and `\u003C!-- comet-task-ref:\u003Ctask-id> -->`, not another checkbox list. Run `comet state submit-plan \u003Cchange-name> --plan \u003Cplan-ref>`. Add `--pause` only if the user explicitly requested a pause after planning. For a `plan-ready` Wait, await an explicit instruction to proceed and use its current hash in `comet state continue-plan \u003Cchange-name> --proposal-hash \u003CproposalHash>`. Do not reuse approval after plan or task requirements change.\n3. 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 shared `state tasks`, `state task-complete`, and `state checkpoint` tools for task IDs, completion, and coordination progress; they do not advance the SDK Run. SDK must not call legacy `comet handoff --write`. Once plan, tasks, and workspace agree, run `comet state complete-build \u003Cchange-name> --session \u003Cbuilder-execution-ref> --checks \u003Cchecks-json-file>` to enter Verify. Resolve drift before submission.\n\nAfter each advance, use that result's `agent.continuation` \u002F `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.\nUse the actual `--session \u003Cbuilder-execution-ref>` for SDK Build; do not repeat it when already supplied.\n\n## Compat path\n\nThe remaining original Runtime steps apply only to `runtimeFormat: compat`. Read [Compat operations](reference\u002Fcompat.md) and continue its current phase. SDK does not load that reference.\n\n## Optional change walkthrough\n\nAt Build completion and before presenting Verify results, check the project `.comet\u002Fconfig.yaml` field `change_walkthrough` (enabled by default; only explicit `false` disables it). When enabled, read and execute [Change walkthrough](..\u002Fcomet\u002Freference\u002Fchange-walkthrough.md), 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.\n",{"name":5,"description":7},"master","9b2c15a8cbb321ae4e36d48849676e14d90eba24","assets\u002Fskills\u002Fcomet-build",314,"https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet","https:\u002F\u002Fdocs.comet.rpamis.com","https:\u002F\u002Fgithub.com\u002Frpamis","More Efficient, Easier to Use, and Less Annoying","2026-11-15 00:26:58",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add rpamis\u002Fcomet --skill comet-build",{"tool":38,"command":39},"bunx","bunx skills add rpamis\u002Fcomet --skill comet-build",{"tool":41,"command":42},"pnpm","pnpm dlx skills add rpamis\u002Fcomet --skill comet-build","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fcomet-build\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",189,"https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fcomet-build\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Fcompat.md",22162,"https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fcomet-build\u002Freference\u002Fcompat.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M72W3K6F0C2FKZ8DHABM49R7","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M72W3HCPQ3GVMACX61QJTD4B","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M72W3F8EVD3EK4NXJG40P84K","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","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M72W3CA9YM0Y6CSXXTNCV1CA","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","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M72W3AEH0F548GTPRNYRR3H3","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M72W38EN8NEKX1YN4W9G19Y2","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fsystematic-debugging\u002FSKILL.md",[],[]]