メニュー
Write implementation-ready opForge specifications with explicit goals, non-goals, invariants, acceptance criteria, and validation expectations. Use when behavior needs to be designed before planning or coding begins.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create execution-ready opForge plans from specs, reviews, or explicitly scoped user requests. Use when implementation or remediation work needs ordered, commit-sized slices with checkboxes, validations, and definition-of-done rules.
Verify and document that claimed review fixes actually close the original opForge findings. Use when remediation work claims to resolve prior review items and closure evidence must be recorded.
Create normalized opForge review reports with findings-first structure, stable finding IDs, evidence-based severity, and explicit testing gaps. Use when a code review needs to be written, cleaned up, or merged from multiple reviewers.
| name | opforge-spec-authoring |
| description | Write implementation-ready opForge specifications with explicit goals, non-goals, invariants, acceptance criteria, and validation expectations. Use when behavior needs to be designed before planning or coding begins. |
Use templates/spec-template.md without changing its validator-facing headings.
A valid spec states:
scripts/workflow/check_workflow_artifact_bundle.pyscripts/workflow/run_spec_workflow.sh