| name | agentic-system-reviewer |
| description | Use when reviewing agent PRDs, implementation plans, unfinished ideas, or agent code against the Production-grade agentic systems course, especially when scope, archetype, chapter relevance, or course-aligned design quality is uncertain. |
Agentic System Reviewer
Overview
Review the provided docs and code against the course, but only after reconstructing the user's goal, project scope, risk level, and archetype. The review must be course-grounded, scope-aware, and evidence-backed.
Core principle: do not grade a weekend prototype like an enterprise workflow control plane, and do not wave through production autonomy like a toy.
When To Use
Use this skill for:
- PRDs, design docs, implementation plans, or idea files for agentic systems.
- Codebases or diffs implementing agent loops, tools, memory, planning, delegation, connectors, proactive triggers, or self-improvement.
- Requests like "review this against the course", "is this agent design good?", "what chapters does this miss?", "check my PRD/code", or "is this production-ready?"
Do not use this skill for ordinary code review with no agent-system concern. Use the normal code-review workflow for that.
Required Resources
Resolve these paths relative to this SKILL.md. Load only what is needed:
references/scope-intake.md - mandatory before review.references/chapter-rubric.md - mandatory after scope is known; read the relevant chapter rows.references/report-template.md - mandatory before writing the final report.scripts/suggest-chapters.mjs - optional helper to seed chapter selection from files; never treat it as authoritative.
Review Flow
Follow this order: read provided docs, inspect provided code, write the scope ledger, ask or assume explicitly for material unknowns, select up to 6 primary chapters, open those course files, then write the findings-first report.
