メニュー
Use before committing to architecture, interface, migration, rollout, or consequential decisions, especially for critic/red-team passes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | red-teaming-decisions |
| description | Use before committing to architecture, interface, migration, rollout, or consequential decisions, especially for critic/red-team passes. |
Rule: no major decision without a critic pass.
Log: .agent-reviews/redteam.md
Loop:
Stop when no high-impact objection remains, or issues repeat for 2 rounds without new evidence.
Output: decision, resolved objections, accepted risks, evidence, stalemate if any.
Use when managing per-project backlog folders, feature queues, async agent work items, lifecycle status updates, PR/done/blocked transitions, or status reviews inside an Obsidian vault.
Use when prototyping, authoring agent skills, or asking the agent to zoom out and map unfamiliar code before acting.
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
Use when reviewing architecture boundaries, hexagonal architecture, clean architecture layers, dependency direction, trust boundaries, uploads, parsers, redirects, or web security risks.
Use when configuring or running hexcheck in a Go repo for hexagonal architecture boundaries, adapter business-logic warnings, and mock discipline.
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
