菜单
Brutally honest external-CTO assessment of project direction versus the stated goal. Use when the user asks where the project stands, whether it has drifted, what to cut, or for a state-of-the-project evaluation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | strategic-review |
| description | Brutally honest external-CTO assessment of project direction versus the stated goal. Use when the user asks where the project stands, whether it has drifted, what to cut, or for a state-of-the-project evaluation. |
| argument-hint | ["focus-area","optional"] |
| allowed-tools | Read, Grep, Glob |
I am requesting a STRATEGIC PROJECT ASSESSMENT. $ARGUMENTS
Act as an External CTO and Lead Architect. I need a "brutally honest" evaluation of where Ranvier Core stands today versus our stated goal: a Layer 7+ LLM traffic controller with prefix-affinity routing that measurably reduces GPU KV-cache thrashing.
Ref:
.dev-context/claude-context.mdfor architecture and the Hard Rules. Also consultBACKLOG.md(current work),CHANGELOG.md(trajectory), anddocs/internals/(what's actually built).
tests/integration/benchmark-baseline.json, docs/benchmarks/) still support the headline claim (~48% faster TTFT)?route_scorer.hpp.)Provide a "State of the Project" scorecard (A-F) for Architecture, Reliability, and Progress-to-Goal, followed by the prioritized analysis. Every claim cites evidence (file, benchmark number, BACKLOG item) — no vibes.
Actionable outcomes go to BACKLOG.md as [STRATEGIC] items; systemic code findings feed /audit or /adversarial-audit.
Hostile security and robustness audit of src/ assuming malicious traffic and 100x load. Use before releases, after large feature merges, or when the user asks for a security audit, adversarial review, or "what breaks under attack".
Holistic system audit for architecture drift, Hard Rules compliance, and async integrity across recently changed code. Use after completing a batch of tasks, before a release, or when the user asks for a health check or audit.
Semantic-correctness audit of hot-path code - enumerate the invariants a component must maintain, then hunt code paths that violate them (wrong answers, not crashes). Use after changing routing, eviction, accounting, or counter logic, before a release, or when metrics drift without any crash.
Orientation for a session starting work on this codebase - reading order, where things live, which skill to use for which task, and the non-negotiable constraints. Use at the start of a session, when unsure where to look, or when the user asks how to approach a task here.
Plan, run, and interpret Locust load benchmarks (mock-backend and real-GPU) including A/B routing experiments. Use when the user wants to measure cache-hit ratio, TTFT, or throughput, compare routing modes, chase a benchmark regression, or design a benchmark experiment.
Triage build or runtime failures. Use when the user pastes a compile error, link error, runtime crash, test failure, or error log, or mentions a build failure.