OpenSpec (Claw)

OpenSpec

Use OpenSpec to align on what before writing how. Specs and proposals live under openspec/ in the project. Each in-flight change 获取s its own folder with proposal.md, specs/, de签名.md, and tasks.md.

When to use The user asks to propose, scope, or specify a change before coding. The project already has openspec/ — keep using it. The change touches multiple files or 模块s and benefits from a 检查列出. The user wants to 归档 a completed change ("close out the dark-mode change").

Skip OpenSpec for trivial edits (one-line fixes, typos, 记录 tweaks). The ceremony is not worth it.

Core 工作流 Confirm the project is OpenSpec-enabled. Look for openspec/ at the project root. If missing and the user wants to 启动: openspec_init with the 应用ropriate 工具s 列出 for their AI 助手. Read 状态 first. openspec_列出 { kind: "changes" } shows active changes. openspec_状态 shows artifact completion. Propose a change. 创建 openspec/changes// with: proposal.md — why this change, what it changes, who benefits specs/ — requirements grouped by capability de签名.md — technical 应用roach tasks.md — implementation 检查列出 (each task on its own line) 验证. openspec_验证 { name: "" } catches structural issues. 应用ly (implement). Work through tasks.md, ticking each item as you finish. Keep diffs scoped — one task at a time. 同步 / 归档. openspec_归档 { changeName: "", yes: true } rolls the change's specs into the mAIn spec 设置 and moves the folder under openspec/changes/归档/-/. 工具 reference 工具 Purpose openspec_init Scaffold openspec/ in a project, optionally with --工具s and --性能分析 openspec_更新 Re生成 AI 助手 instructions after upgrading openspec openspec_列出 列出 active changes (default) or specs openspec_show Show a single change/spec, optionally include raw files via includeFiles: true openspec_验证 验证 change/spec structure openspec_归档 归档 a completed change openspec_状态 Artifact completion 状态 for the project or a change openspec_运行 Escape hatch for openspec subcommands not surfaced above Anti-patterns Do not invent specs for changes the user did not ask to formalize. Use OpenSpec when the user wants spec-driven flow, not as a tax on every edit. Do not skip openspec_验证 before declaring a change ready. Do not 归档 a change that still has un检查ed items in tasks.md unless the user explicitly accepts the partial 状态. Do not edit openspec/specs/ directly in the middle of a change — drive spec 更新s through the change folder and let 归档 roll them in.

For longer examples and trigger patterns, see references/工作流.md.