review_plan
Review the technical implementation plan against the specification.
12 stars
Best use case
review_plan is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Review the technical implementation plan against the specification.
Teams using review_plan should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/review_plan/SKILL.md --create-dirs "https://raw.githubusercontent.com/lionbenjamin/agent-templates/main/skills/review_plan/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/review_plan/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How review_plan Compares
| Feature / Agent | review_plan | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Review the technical implementation plan against the specification.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Review Plan Skill Skeptical technical review of implementation plans. ## When to Activate This skill is relevant when: - Reviewing technical implementation plans - Validating architecture decisions - Checking for security or performance issues - Ensuring plan completeness ## Core Principles ### Security Mindset - Where are the injection points? - Is auth checked everywhere? - Are secrets exposed? - Input validation comprehensive? ### Breaking Changes - Will this break production? - Are migrations backward compatible? - Rollback plan exists? - Safe deployment strategy? ### Redundancy - Why rewrite this? - Can we use existing components? - Maximize code reuse - Avoid duplication ### Performance - N+1 queries spotted? - Unindexed lookups? - Heavy bundles? - Scalability concerns? ## Quick Checks When reviewing plans, verify: - [ ] Plan covers all spec requirements - [ ] No missing requirements - [ ] Proposed schema changes are valid - [ ] Relations handled correctly - [ ] Component changes are modular - [ ] Code reuse maximized - [ ] Security gaps identified (RLS, validation) - [ ] Performance bottlenecks flagged - [ ] Breaking changes documented - [ ] Verification plan is detailed - [ ] Tests prove correctness - [ ] Migration strategy safe - [ ] Rollback plan included - [ ] No obvious architectural flaws - [ ] Follows existing patterns
Related Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.