plan-review-rules

Apply predefined rules to evaluate architecture, dependencies, and risk in multi-part plans.

47|2|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/hex0xdeadbeef/claude-kit --skill plan-review-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review-rules
Source: https://github.com/hex0xdeadbeef/claude-kit/tree/main/.claude/skills/plan-review-rules
Command: npx skills add https://github.com/hex0xdeadbeef/claude-kit --skill plan-review-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines plan-review by applying standardized rules to evaluate architecture, dependencies, and risk, ensuring consistent and auditable decision-making.

Core Features & Use Cases

  • Enforces architecture compliance (import matrix, layer order) and domain purity
  • Applies a formal decision matrix with auto-escalation for minor issues
  • Generates structured verdicts and actionable notes for coders
  • Provides on-demand references and troubleshooting guidance to reviewers

Quick Start

Load a plan from .claude/prompts and execute the plan-review workflow to generate a verdict.

Frequently Asked Questions about plan-review-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate architecture compliance checks for software plan reviews?

Automated plan-review governance applies predefined rules to evaluate architecture, dependencies, and risk in complex software plans. It enforces slot-driven checks from PROJECT-KNOWLEDGE.md to validate structure before approval.

How do I apply a formal decision matrix to evaluate software architecture risk?

Applying a formal decision matrix evaluates software architecture risk by enforcing governance rules and auto-escalating minor issues. It produces structured verdicts and actionable notes for coders based on dependency and risk analysis.

Can I use automated rules to review complex multi-part software plans?

Automated rules can review complex multi-part software plans by validating structure, dependencies, and risk. The system loads plans from prompts and executes workflow checks to generate structured verdicts for reviewers.

What is the best way to enforce governance rules before approving software architecture plans?

Enforcing governance rules before approval requires applying standardized checks to evaluate architecture, dependencies, and risk. This approach ensures consistent and auditable decision-making through structured verdict outputs and actionable notes.

How do I auto-escalate minor issues found during code or plan review?

Auto-escalating minor issues during plan review uses a formal decision matrix to evaluate severity and enforce governance. The system automatically escalates minor architectural or dependency issues to ensure compliance before approval.

How do I generate structured verdicts for software project plan approvals?

Generating structured verdicts for plan approvals involves executing plan-review workflows that apply predefined rules to architecture and dependencies. The system produces formal verdicts and actionable notes for coders to resolve.