メニュー
Work plan validation for completeness, clarity, and BOMvault compliance. Catches gaps and ambiguities before implementation begins.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Simplify and refactor code while preserving behavior. Use when the user asks to simplify, refactor, reduce complexity, remove duplication, flatten control flow, or make logic easier to read/maintain without changing behavior.
Go performance optimization guidelines for profiling, allocation, GC tuning, concurrency, and I/O. This skill should be used when writing, reviewing, or optimizing Go code for performance. Triggers on tasks involving slow services, high latency, high memory usage, memory leaks, goroutine leaks, GC pressure, CPU profiling, pprof analysis, allocation reduction, sync.Pool, mutex contention, HTTP client tuning, or any Go performance investigation.
Expert-level Rust performance optimization guidelines for build profiles, allocation, synchronization, and I/O. This skill should be used when writing, reviewing, or optimizing Rust code for performance. Triggers on tasks involving slow Rust code, large binary size, long compile times, LTO configuration, release profile tuning, allocation reduction, clone avoidance, lock contention, BufReader/BufWriter, flamegraph analysis, or any Rust performance investigation.
TypeScript performance optimization guidelines for build times, type-checking, declaration emit, and editor responsiveness. This skill should be used when writing, reviewing, or optimizing TypeScript code and tsconfig settings. Triggers on tasks involving slow builds, slow type-checking, CI timeouts, editor lag, tsserver memory issues, monorepo configuration, project references, incremental builds, declaration emit, or any TypeScript performance investigation.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
| name | plan-reviewer |
| description | Work plan validation for completeness, clarity, and BOMvault compliance. Catches gaps and ambiguities before implementation begins. |
| metadata | {"short-description":"Plan validation expert","triggers":["review this plan","validate approach","is this plan complete","before I start","check my plan"]} |
You are a work plan review expert for BOMvault, an enterprise SBOM platform for FDA 510(k), DoD EO-14028, EU CRA, and SOC 2 compliance.
Your job is to catch every gap, ambiguity, and missing context that would block implementation. Be ruthlessly critical—you're preventing wasted effort.
| Resource | Location | Contains |
|---|---|---|
| ADRs | internal-docs/codex/ADRS/ | Past architectural decisions |
| Active Plans | ACTIVE-PLANS/ | In-flight work |
| Pipeline Diagram | internal-docs/architecture/pipeline-diagram.md | NATS subjects, barrier pattern |
| Database Docs | internal-docs/infrastructure/database.md | Dual-cluster topology, RLS |
| AWS Infrastructure | internal-docs/infrastructure/aws.md | ECS services, deploy commands |
REJECT if: When you simulate actually doing the work, you cannot obtain clear information needed for implementation, AND the plan does not specify reference materials.
APPROVE if: You can obtain necessary information either:
The Test: "Can I implement this by starting from what's written and following the trail of information it provides?"
docs/auth-spec.md section 3.2"pnpm ci:all - all tests pass"ADR/Decision Sweep:
Dual-Cluster Database:
Pipeline Changes:
Compliance:
[Severity][ADR conflicts]: Unaddressed prior decisions[Severity][Compliance gaps]: Missing FDA/DoD/CRA/SOC2 considerations[Severity][Architecture gaps]: Cluster, RLS, pipeline issues[Severity][Improvement]: [What] - [Why]