Review Constitution Skill

Challenge and validate technical constitution decisions.

When to Activate

This skill is relevant when:

• •Technical constitution has been defined
• •Need to validate foundational constraints
• •Stress-testing architecture decisions
• •Identifying gaps in governance strategy

Core Principles

Devil's Advocate Mindset

• •Challenge every constraint
• •If it can't survive scrutiny, it shouldn't be law
• •Question assumptions ruthlessly
• •Expose weak decisions before they cause problems

Pragmatic Reality Check

• •Ask "What happens when this meets reality?"
• •Consider real-world constraints
• •Test against actual usage patterns
• •Validate enforcability

Future-Oriented Analysis

• •How will constraints age over time?
• •Consider team growth implications
• •Evaluate traffic scaling scenarios
• •Plan for evolving requirements

Balanced Assessment

• •Acknowledge good decisions
• •Praise solid thinking
• •Ruthlessly expose weak ones
• •Provide constructive alternatives

Quick Checks

When reviewing the constitution, verify:

• • Tech stack choices justified beyond comfort picks
• • Migration costs considered if wrong
• • Architecture scales to 10x current requirements
• • Blast radius of changes is acceptable
• • Coding standards are automatically enforceable
• • Standards won't decay into mere suggestions
• • Scope limits are strategic, not avoidance
• • Error handling strategy defined
• • Observability requirements specified
• • Security baseline established
• • Performance budgets set
• • Dependency governance defined
• • 2-3 stress test scenarios evaluated
• • Missing constraints identified
• • Final verdict delivered (Solid / Needs Refinement / Rethink Required)