Intermediate artifacts - Comet Docs

Comet creates intermediate artifacts so the workflow can survive context loss, phase transitions, model switches, and later review. These files are not noise; they are the evidence trail that lets /comet resume from facts instead of memory.

Xiaoyu sorts Comet intermediate artifacts by context, recovery, handoff, and verification evidence

Main artifact categories

Category	Examples	Purpose
Requirements facts	`proposal.md`, delta `spec.md`, `tasks.md`	Define what is being changed.
Design and plan	Design Doc, implementation plan	Preserve how the work should be built.
Handoff context	`.comet/handoff/design-context.`, `spec-context.`	Move OpenSpec evidence into later phases.
Runtime state	`run-state.json`, `state-events.jsonl`, checkpoints	Support deterministic recovery.
Verification evidence	verify reports, test output, branch status	Prove completion before archive.

What to edit

Edit user-readable artifacts such as proposal, design, tasks, Design Doc, Plan, and configuration. Do not hand-edit machine-owned runtime state unless a recovery guide instructs it.

Recovery anchors

Files such as brainstorm-summary.md and subagent-progress.md let an agent reload context after compaction. Keep them with the change. In SubAgent mode, subagent-progress.md is maintained by the coordinator session, not implementer or reviewer subagents.

Next steps

Last modified on July 15, 2026