メニュー
Identify edge cases, security/privacy issues, operational risks, and delivery risks in a spec.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Safely sync a branch with origin/main using fetch + rebase, with an optional "accept current" conflict policy.
Improve acceptance criteria so they are testable, unambiguous, and complete.
Add an MCP integration section (tools, auth, error handling, observability, tests) to an existing spec.
Extract MUST/SHOULD/MAY requirements, constraints, flows, and open questions from long epic/PRD text (PDF/TXT export).
Propose a safe rollout/migration plan with monitoring and rollback steps.
Produce a clear, review-ready SDD specification skeleton in Markdown.
| name | risk-review |
| description | Identify edge cases, security/privacy issues, operational risks, and delivery risks in a spec. |
Find gaps before implementation: edge cases, security/privacy risks, operational risks.
Perform a risk review of this spec.
Sections to produce:
- Edge cases we might be missing
- Security & privacy considerations (authn/authz, secrets, data exposure, abuse)
- Operational risks (timeouts, retries, rate limiting, observability)
- Delivery risks (dependencies, migrations, rollout, backward compatibility)
For each item:
- describe impact,
- likelihood (low/med/high),
- mitigation,
- how to verify.
Keep it short but actionable.