メニュー
Review release-truth and additive public-readiness governance changes without confusing tag objects, warning lanes, or closeout guidance.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Perform a Specrew human-verdict boundary stop on the Claude host. Renders the FULL Rule 46 six-section human re-entry packet AND the verdict options as one Markdown message, with the AskUserQuestion picker disabled so the packet cannot collapse into the picker's short header/option fields. Invoke at EVERY human-judgment boundary stop (specify, clarify, plan, tasks, before-implement, implement, review, retro, feature-closeout, lifecycle-end). Triggers: boundary stop, verdict, approve / redirect / send back, why I stopped, human re-entry packet, gate stop.
{what this skill teaches agents}
Run Specrew's per-lens design workshop and collaborative design-analysis. Use whenever you work the design lenses for a feature: at specify/intake (the lens workshop) and at the design-analysis stop (co-design the architecture), and RE-INVOKE at the start of EACH new lens (architecture, data, ui-ux, security, integration, devops, requirements/NFR, observability, component). Triggers: design, design lens, lens workshop, design-analysis, architecture, trade-offs, co-design, explore options, decompose, or moving from one lens to the next. Tells you to facilitate each lens as a discussion, surface diagrams the human can actually SEE (console ASCII inline; mermaid/html to a file with a clickable file:/// link), co-design components/responsibilities/flows WITH the human instead of handing over finished options, capture the agreements, and which per-lens md to load.
| name | public-readiness-release-review |
| description | Review release-truth and additive public-readiness governance changes without confusing tag objects, warning lanes, or closeout guidance. |
| domain | review |
| confidence | high |
| source | earned |
| tools | [{"name":"view","description":"Read the version surfaces, coordinator guidance, and review artifacts.","when":"When verifying release truth across docs, config, and iteration artifacts."},{"name":"rg","description":"Find tag commands, force flags, and closeout-rule text quickly.","when":"When checking for destructive tag handling or incomplete version-management wording."},{"name":"powershell","description":"Run validator lanes and git tag verification commands.","when":"When additive-warning behavior and local/origin tag anchors need live proof."}] |
Use this when a feature changes versioning surfaces, retroactive changelog/tag history, public-readiness validator warnings, or future closeout governance. The review question is not just whether the docs read well; it is whether every release-truth surface and every validator lane tells the same story without rewriting history or promoting advisory checks into blockers.
.specrew\config.yml as the source of truth, then verify README.md, docs\versioning.md, CHANGELOG.md, the product/spec status surface, and annotated tags all mirror that same version.git for-each-ref plus remote git ls-remote --tags origin refs/tags/<tag> refs/tags/<tag>^{} and compare the peeled commit to the required ship anchor.--force, --force-with-lease, or equivalent destructive rewrite language. Accept duplicate-tag handling only when it fails or stays advisory; never accept a review that rewrites existing tags.extensions\specrew-speckit\scripts\validate-governance.ps1tests\unit\fixtures\015-public-readiness-pass\public-readiness-clean\tests\unit\fixtures\015-public-readiness-pass\public-readiness-drift\docs\versioning.mdCHANGELOG.md--force-style tag creation or rewrite behavior in a historical release workflow.