rpamis/comet - 2ページ

comet-open

Comet Phase 1: Open. Invoke with /comet-open. Explore ideas through OpenSpec, confirm requirements clarification, then create change structure (proposal + design + tasks).

原文の言語: 英語

comet

Comet — OpenSpec + Superpowers dual-star development workflow. Start with /comet for automatic phase detection and dispatch to subcommands. Five phases: open → design → build → verify → archive.

原文の言語: 英語

comet-tweak

Comet preset path: Non-bug small changes (tweak). Skip brainstorming and full plan, directly open → lightweight build → light verify → archive. Applicable for copy, configuration, documentation or prompt local optimization.

原文の言語: 英語

comet-verify

Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.

原文の言語: 英語

comet-archive

Use when Comet change 验证已通过，需要用户确认归档、合并 delta spec，或恢复 archive 阶段。

原文の言語: 中国語

comet-build

Use when full Comet change 已完成 design 阶段，需要创建/恢复实施计划、选择执行方式或继续 build 阶段任务。

原文の言語: 中国語

comet-design

Use when full Comet change 已完成 open 阶段但缺少 Superpowers Design Doc，或 design 阶段需要从 OpenSpec 交接包恢复。

原文の言語: 中国語

comet-hotfix

Use when 用户要修复已有行为 bug，且不新增 capability、不需要完整设计；也用于恢复 hotfix workflow。

原文の言語: 中国語

comet-open

Use when Comet 需要创建新的 OpenSpec change，或 active change 缺少 proposal/design/tasks/.comet.yaml 初始化产物。

原文の言語: 中国語

comet

Use when 用户要启动或恢复 Comet 工作流，需要根据 active change、.comet.yaml、hotfix/tweak 意图路由到对应阶段 Skill。

原文の言語: 中国語

comet-tweak

Use when 用户要进行可收敛为单一 OpenSpec change 的轻量或中等变更，且不需要完整设计；也用于恢复 tweak workflow。

原文の言語: 中国語

comet-verify

Use when Comet change 已完成 build 阶段，需要验证实现、处理验证失败决策或完成分支收尾。

原文の言語: 中国語

openspec-bulk-archive-change

Archive multiple completed changes at once. Use when archiving several parallel changes.

原文の言語: 英語

openspec-continue-change

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

原文の言語: 英語

openspec-ff-change

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

原文の言語: 英語

openspec-new-change

Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.

原文の言語: 英語

openspec-onboard

Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.

原文の言語: 英語

openspec-sync-specs

Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.

原文の言語: 英語

openspec-verify-change

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

原文の言語: 英語

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

原文の言語: 英語

dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

原文の言語: 英語

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

原文の言語: 英語

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

原文の言語: 英語

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

原文の言語: 英語

subagent-driven-development

Use when executing implementation plans with independent tasks in the current session

原文の言語: 英語

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

原文の言語: 英語

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

原文の言語: 英語

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

原文の言語: 英語

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

原文の言語: 英語

writing-skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment

原文の言語: 英語