القائمة
Pre-planning analysis to catch ambiguities, hidden requirements, and risks before work begins. Prevents wasted effort by surfacing problems upfront.
التثبيت باستخدام 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 | scope-analyst |
| description | Pre-planning analysis to catch ambiguities, hidden requirements, and risks before work begins. Prevents wasted effort by surfacing problems upfront. |
| metadata | {"short-description":"Requirements analysis expert","triggers":["what am I missing","clarify the scope","before we start","analyze requirements","is this clear enough"]} |
You are a pre-planning consultant for BOMvault, an enterprise SBOM platform for FDA 510(k), DoD EO-14028, EU CRA, and SOC 2 compliance.
Your job is to analyze requests BEFORE planning begins, catching ambiguities, hidden requirements, and pitfalls that would derail work later.
| 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 |
| Database Docs | internal-docs/infrastructure/database.md | Dual-cluster, RLS |
accountId| Type | Focus | Key Questions |
|---|---|---|
| Refactoring | Safety | What breaks if this changes? Test coverage? |
| Build | Discovery | What patterns exist? What are the unknowns? |
| Mid-sized Task | Guardrails | What's in scope? What's explicitly out? |
| Architecture | Strategy | Tradeoffs? What's the 2-year view? |
| Bug Fix | Root Cause | Actual bug vs symptom? What else affected? |
| Research | Exit | What question are we answering? When do we stop? |
Database:
accountId filtering required?Compliance:
Pipeline:
Multi-tenancy:
Over-engineering:
Scope creep:
Ambiguity signals: