system-review
System Review
Perform a meta-level analysis of how well the implementation followed the plan and identify process improvements.
Purpose
System review is NOT code review. You're not looking for bugs in the code - you're looking for bugs in the process.
Your job:
- Analyze plan adherence and divergence patterns
- Identify which divergences were justified vs problematic
- Surface process improvements that prevent future issues
- Suggest updates to Layer 1 assets (CLAUDE.md, plan templates, skills)
Philosophy:
- Good divergence reveals plan limitations → improve planning
- Bad divergence reveals unclear requirements → improve communication
More from giladresisi/ai-dev-env
code-review-fix
Use when fixing bugs found during a code review, processing each issue with explanation and test verification
11acceptance-criteria-validate
Use when an agent executing an implementation plan claims to have finished, to validate that all acceptance criteria were actually met. Locates acceptance criteria from the plan file, acceptance_criteria.md, or the request itself, then investigates the codebase and surfaces a pass/fail verdict per criterion.
11acceptance-criteria-define
Use when an agent is asked to define, review, or write acceptance criteria for a request or plan. Derives acceptance criteria from the current request context, confirms them with the user, and writes them into the plan file or a standalone acceptance_criteria.md file.
10commit
Use when the user asks to commit changes, create a commit, or save work to git
9create-prd
Use when creating a Product Requirements Document from a conversation or feature request through structured context gathering
9execute
Use when implementing a feature plan file, choosing between sequential and team-based parallel execution with mandatory validation gates
8