القائمة
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.
