junior-to-senior
Adversarial senior-engineer review for agent-generated plans, designs, and architectures. Treats the current output as junior work, constructs a senior reviewer whose domain expertise comes from live codebase research plus web research of current best practices, diagnoses altitude failures (too vague or too granular), then rewrites the plan into a scoped, state-of-the-art version. Use when the user says "junior to senior", "senior review", "review this like a staff engineer", when a plan feels h
Security Assessment
About junior-to-senior
junior-to-senior is an adversarial review skill that treats any agent-generated plan, design, or architecture as "junior" work and constructs a rigorous "senior" reviewer to tear it down and rebuild it. It exists to catch the two ways AI-written plans fail: "fog" (high-level hand-waving with no interfaces, data shapes, failure handling, or named libraries) and "tunnel" (diving into function signatures while missing product vision, scope, and rationale). The core discipline is evidentiary: every finding must cite a file and line for codebase claims, or a dated primary source for best-practice claims, and any claim that cannot be verified via web research is explicitly labeled as unverified training data.
The workflow runs in phases. Phase 0 freezes the artifact under review so critique targets a fixed text. Phase 1 builds the senior reviewer by extracting 2-5 load-bearing technical domains, doing live code research (conventions, lockfile versions, prior art, real constraints) and web research for deprecations, supersessions, and hard-won lessons, ideally in a context-isolated subagent so the review is adversarial rather than self-confirming. Phase 2 diagnoses altitude (fog, tunnel, or mixed), and Phase 3 delivers findings graded as blocker, major, or minor, each with evidence and a concrete fix. Supporting reference files provide the review rubric, a vague-word blacklist, and a research playbook.
The skill targets engineers and teams using AI agents to produce technical plans who want a staff-level sanity check before committing. Typical use is invoked by phrases like "senior review" or "review this like a staff engineer," or automatically before acting on any agent-written plan. It is process guidance rather than executable tooling, and its quality depends on available codebase and web access.
FAQ
What does this skill actually review?
Any plan, design doc, RFC, architecture, or issue description — most often a plan the agent just produced in the same conversation, but also pasted text or a planning document in the repo.
Do I need web access for it to work?
It works best with both codebase and web access. If web research is unavailable it proceeds on code research alone and labels every best-practice claim as unverified training data so stale knowledge is not presented as current truth.
How are findings prioritized?
Each finding is graded blocker (plan fails as written), major (works but meaningfully worse than state of the art or a misfit to the repo), or minor (polish), and every finding must carry concrete evidence.
Does it just criticize everything?
No. The rules require steelmanning the original choice first, and conceding when the evidence actually supports the junior plan is treated as a valid outcome, not a failure.
Is this executable tooling or guidance?
It is a structured review methodology (SKILL.md plus reference rubrics and a research playbook). It does not ship code; it directs the agent's research and critique process.
Install junior-to-senior
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
juliusbrussee/skills