Architect Reviewer Agent
File: .github/agents/tsh-plan-reviewer.agent.md
The Architect Reviewer is an internal sub-agent that stress-tests implementation plans before code is written. It challenges the plan for likely failure modes, hidden assumptions, sequencing traps, integration mismatches, migration and data risks, and false confidence in testing.
Responsibilities
- Stress-testing the plan against the research context to expose likely failure modes.
- Checking that referenced files, functions, classes, integrations, and patterns actually exist in the codebase.
- Surfacing hidden assumptions, sequencing traps, dependency order issues, and migration or data risks.
- Challenging integration boundaries, rework risk, and false confidence in test coverage.
- Producing a structured approval or revision report for the Engineering Manager.
What It Produces
- A failure-oriented review report with a binary verdict, top risks, assumptions, rework triggers, and any blocking gaps.
- The report is saved as
{task-name}.plan-review.mdalongside the plan inspecifications/<task-name>/.
Tool Access
| Tool | Usage |
|---|---|
| Context7 | Verify framework or library assumptions when the plan references them |
| Sequential Thinking | Evaluate trade-offs, phase ordering, and over-engineering risk |
| File Read/Search | Inspect the plan, research file, instructions, and referenced code |
| Todo | Track review checklist progress |
Skills Loaded
tsh-architecture-designing— Evaluate architectural shape, phase coherence, and trade-offs.tsh-codebase-analysing— Verify plan references against the actual codebase.tsh-technical-context-discovering— Check project conventions and existing patterns.tsh-implementation-gap-analysing— Compare what exists with what the plan proposes.tsh-sql-and-database-understanding— When the plan includes database schema, migration, or query changes.
How It Is Used
- It is not invoked directly by users.
- The Engineering Manager runs it through the internal
/tsh-review-planprompt after the Architect produces or updates a plan. - If the reviewer returns revisions, the plan goes back to the Architect and is re-reviewed until approved or escalated.