aops-core/skills/strategic-review/SKILL.md
Unified multi-agent review of any artifact — a document, plan, proposal, or pull request. The calling agent deploys rbg, pauli, and marsha in parallel, then @james reconciles their findings into one verdict. Pass `comment` and/or `fix` to write the result back to the review surface. Use `--critic` for a fast pauli-only pre-hoc critique.
npx skillsauth add nicsuzor/academicops strategic-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Review any artifact — a document, plan, proposal, or pull request — from several expert perspectives and return one reconciled verdict. Owned by james (reconciliation), but you, the invoking agent, own the orchestration: you deploy the reviewers yourself, because a subagent cannot spawn its own subagents. James is called only at the end, to reconcile.
rbg + pauli + marsha in parallel, then @james reconciles.--critic — solo pauli: one fast adversarial critique, no reconciliation. For a pre-hoc
sanity check on a plan or proposal before work starts.owner/repo#N ref or URL).comment, fix, or both. With no flag the review is advisory —
you return the verdict to the caller and change nothing.Identify and load the artifact. If it is a PR, load the diff, description, and any prior
unresolved review comments (gh pr view, gh pr diff). Select the matching review-context
descriptor from review-contexts/ and pass it to every reviewer:
review-contexts/pr-code.md — code PRs.review-contexts/pr-framework.md — framework PRs (skills, agents, hooks, specs).Spawn all three in a single message (concurrent Agent calls). Give each the artifact, the
context, and the descriptor. You spawn them — not james. Subagents cannot spawn subagents, so
this fan-out must happen here, at the top level.
When all three return, dispatch @james with the original artifact plus all three reviewer outputs. James does not re-spawn anyone — it reconciles only. It carries the contradictions, resolves them honestly, and returns one verdict with a synthesis table:
| Agent | Issue | Feedback | Severity |
Severity ladder: REJECT (fundamental — close/redesign) · REVISE (substantial rework, in scope) · FIX (clear correct resolution exists) · TRIVIAL (cosmetic) · ADVISORY (non-blocking follow-up). Overall verdict: APPROVE / REVISE / REJECT.
Agent(subagent_type="aops-core:james",
prompt="Reconcile these three reviews into one verdict. Do NOT spawn subagents — synthesise only. [artifact + rbg/pauli/marsha outputs]")
comment: post james's synthesis to the artifact's natural review surface — a PR comment for
a PR, an inline note or PKB entry for a document. Scrub all personal info (names, private paths).fix: apply every FIX- and TRIVIAL-grade finding directly, without returning to the
author. If a fix is substantial, re-run the affected reviewer(s) and fold any new findings into
the table. REVISE/REJECT findings are reported, not silently reworked.Whatever the flags, never silently exit: if a write-back action fails, report it and print the full verdict to chat.
--critic modeDeploy pauli alone for a fast pre-hoc critique (premise test + the 10 cognitive moves). No parallel roster, no james reconciliation. Return pauli's verdict directly to the caller. Use this to pressure-test a plan or proposal before committing effort to it.
tools
Streamlit implementation of the analyst presentation layer. Use when building or updating a Streamlit dashboard that displays pre-computed research data. This is the Streamlit-specific HOW for the tech-agnostic principles in the aops-tools analyst skill — display only, never transform.
tools
Python plotting and statistical-modelling libraries (matplotlib, seaborn, statsmodels) for the analyst presentation and statistical-methodology layers. Use when producing publication-quality figures or fitting statistical models in Python. Library-specific HOW for the tech-agnostic principles in the aops-tools analyst skill.
tools
dbt (data build tool) implementation of the analyst transformation layer. Use when a project has a dbt/ directory or you need to build, test, or document SQL transformations as version-controlled, reproducible dbt models. This is the dbt-specific HOW for the tech-agnostic principles in the aops-tools analyst skill.
development
Core academicOps skill — institutional memory, strategic coordination, workflow routing, and framework governance. Merges butler (chief-of-staff) with framework development conventions.