Skip to main content
comet status gives you a snapshot of your project’s Comet workflow state — showing active changes, how many tasks are complete, and which command to run next.

​
Usage

comet status [path]
path defaults to . (the current directory) when omitted. The command reads change state from openspec/changes/ inside the target directory.

​
Example Output

Active Changes:

  1. my-feature [phase: build [3/7 tasks]]
     workflow: full | build_mode: subagent-driven-development
     plan:   docs/superpowers/plans/2024-06-01-my-feature.md
     next: /comet-build

  2. quick-fix [phase: verify [5/5 tasks]]
     workflow: full | build_mode: direct
     verify_result: pending
     next: /comet-verify
Each entry shows:
FieldDescription
phaseCurrent workflow phase (open, design, build, verify, archive).
tasksCompleted / total task count from tasks.md, e.g. [3/7 tasks].
workflowWorkflow preset (full, hotfix, tweak).
build_modeBuild execution mode (e.g. subagent-driven-development, direct).
designPath to the Superpowers Design Doc, if generated.
planPath to the implementation plan, if generated.
verify_resultVerification outcome (pending, pass, fail) — shown only in the verify phase.
nextThe Comet skill command to run next.
Only non-archived changes appear. Changes where .comet.yaml is missing or archived: true are excluded.

​
Flags

​
--json
boolean
Output active changes as structured JSON, including a nextCommand field for each change. Useful for scripting and automation.

​
JSON Output

comet status --json

{
  "changes": [
    {
      "name": "my-feature",
      "workflow": "full",
      "phase": "build",
      "buildMode": "subagent-driven-development",
      "isolation": "branch",
      "verifyMode": "null",
      "verifyResult": "pending",
      "designDoc": null,
      "plan": "docs/superpowers/plans/2024-06-01-my-feature.md",
      "tasksCompleted": 3,
      "tasksTotal": 7,
      "nextCommand": "/comet-build"
    }
  ]
}
The nextCommand field maps each phase to its corresponding Comet entry point:
PhaseNext command
open/comet-open
design/comet-design
build/comet-build
verify/comet-verify
archive/comet-archive

​
Use Cases

  • Quick workflow check — Glance at all in-flight changes and where each one stands.
  • Know what to run next — The next field tells you exactly which Comet command to invoke to continue.
  • Scripting and automation — Pipe --json output into CI scripts or shell tooling to conditionally trigger workflow commands based on phase or task completion.
  • Resume after interruption — After closing an AI coding session, run comet status to orient yourself before typing /comet in your AI platform.