brooks

Review plans and designs adversarially to identify flaws and complexity.

1|Updated Jun 4, 2026
One-click install
npx skills add https://github.com/m16khb/agent-harness --skill brooks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brooks
Source: https://github.com/m16khb/agent-harness/tree/main/skills/brooks
Command: npx skills add https://github.com/m16khb/agent-harness --skill brooks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides an adversarial review of plans and designs before implementation, ensuring conceptual integrity, identifying accidental complexity, and challenging schedule optimism.

Core Features & Use Cases

  • Devil's Advocate Review: Independently review a plan or design, identifying flaws and weaknesses before implementation.
  • Essential vs. Accidental Complexity: Classify complexity and suggest simplifications.
  • Conceptual Integrity: Ensure the design is coherent and consistent.
  • Second-System Effect: Avoid over-engineering by focusing on essential features.
  • Schedule & Effort Honesty: Challenge optimistic assumptions about time and resources.
  • Use Case: Use this Skill to review the architecture of a new software project, ensuring it is not overly complex and that the schedule is realistic.

Quick Start

Invoke Brooks as a sub-agent to review the architecture design document for the upcoming project.

Frequently Asked Questions about brooks

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

FAQPage Schema
What is an adversarial design review for software architecture?

An adversarial design review independently analyzes software architecture to identify flaws, ensure conceptual integrity, and challenge schedule optimism before implementation begins. It acts as a devil's advocate to strengthen your project plans.

How do I review a project plan to identify accidental complexity?

To review a project plan and identify accidental complexity, you classify complexity types and suggest simplifications. This ensures the design focuses only on essential features, avoiding over-engineering and the second-system effect.

When do I need a devil's advocate review for project planning?

You need a devil's advocate review for project planning when you must ensure conceptual integrity and challenge optimistic assumptions about time and resources. It is highly suitable for evaluating new software architecture designs prior to implementation.

What is the best way to challenge schedule optimism in software design?

The best way to challenge schedule optimism in software design is through an independent adversarial analysis. This approach directly challenges optimistic assumptions about time and effort, ensuring schedule and effort honesty before development starts.

Can I use an adversarial review to avoid the second-system effect?

Yes, you can use an adversarial review to avoid the second-system effect by focusing on essential features and preventing over-engineering. It evaluates your design to ensure it is not overly complex and remains feasible.

What are the limitations of automated design analysis for project plans?

Automated design analysis for project plans requires an independent, adversarial perspective to be effective. It relies entirely on the provided architecture documents and cannot discover flaws outside the scope of the submitted design materials.