一键导入
spec-archive-gate
Use when an OpenSpec change or GSD phase is claimed complete, ready to archive, ready to ship, ready to commit, or ready for pull request
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when an OpenSpec change or GSD phase is claimed complete, ready to archive, ready to ship, ready to commit, or ready for pull request
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when converting an OpenSpec change, proposal, design, specs, or tasks into implementation work before coding starts
Use when starting, planning, executing, verifying, archiving, or shipping development work that should coordinate GSD Core, OpenSpec, and Superpowers
Use when reviewing implemented code, completed tasks, test coverage, or diffs for an OpenSpec change before continuing, archiving, or shipping
| name | spec-archive-gate |
| description | Use when an OpenSpec change or GSD phase is claimed complete, ready to archive, ready to ship, ready to commit, or ready for pull request |
Archive only after evidence exists. A completed checklist without verification is not enough.
In no-GSD mode, skip GSD verification. That is not a missing gate.
Run node cli/bridge.mjs archive-readiness <change-id-or-path> when available.
This catches only mechanical blockers; still run spec compliance review.
Report:
If any required gate fails, do not archive, commit, ship, or open a ready PR.