junior-to-senior

Reviews agent-generated plans against codebase reality and current best practices, then rewrites them.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/ZimriJahdai/HaircutFiveFriends-Full --skill junior-to-senior-zimrijahdai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: junior-to-senior
Source: https://github.com/ZimriJahdai/HaircutFiveFriends-Full/tree/main/.claude/.agents/skills/junior-to-senior
Command: npx skills add https://github.com/ZimriJahdai/HaircutFiveFriends-Full --skill junior-to-senior-zimrijahdai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agent-generated plans often fail at two altitudes: they are either too vague ("add caching", "handle auth") or lost in low-level detail with no product vision, and they rely on training-cutoff knowledge that may be outdated. This Skill performs an adversarial senior-engineer review grounded in live codebase research and current web sources, then rewrites the plan into a scoped, evidence-backed version. ## Core Features & Use Cases - Altitude Diagnosis: Classifies each plan section as fog (too vague), tunnel (too granular), or mixed using concrete tests like the start-tomorrow test and a vague-word blacklist. - Evidence-Based Adversarial Review: Every finding cites a file and line or a dated web source, with blocker/major/minor severities and concrete fixes; unverifiable claims are labeled [training-data, unverified]. - Plan Promotion: Produces a rewritten plan with goals and non-goals, versioned decisions with rejected alternatives, sequencing with verifiable milestones, rollback strategy, and open questions for humans. - Use Case: Before committing to an agent-written migration plan, run a senior review that checks pinned dependency versions in the lockfile, searches current release notes for deprecations, flags a missing data migration as a blocker, and returns a promoted v2 plan. ## Quick Start Ask the assistant to review the current plan like a staff engineer using the junior-to-senior skill before implementing it.

Frequently Asked Questions about junior-to-senior

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a senior engineer review of an AI-generated plan?

Invoke the junior-to-senior skill on the plan the agent just produced or a pasted design doc. It freezes the artifact, researches the codebase and current best practices, then returns a severity-ranked review plus a rewritten senior version of the plan.

What makes a software plan too vague or too detailed?

A vague plan fails the start-tomorrow test: an engineer would still need to make architecture decisions themselves. A too-detailed plan lacks goals, non-goals, success criteria, and alternatives. The skill diagnoses each section as fog, tunnel, or mixed.

Does the review work without web access?

Yes. It runs full codebase research (versions, conventions, prior decisions) and marks every best-practice claim as [training-data, unverified]. It also names the decisions most likely to have shifted so you can spot-check them manually.

Can the review change my product decisions automatically?

No. The senior reviewer scopes and upgrades the technical plan but never invents product direction. Genuine product choices are listed as open questions for a human, and the original plan is never silently replaced.

What happens if the plan is already good?

A review with zero blockers and zero majors is a valid result. The skill explicitly says the plan holds and stops, rather than manufacturing findings to appear rigorous.