review_constitution
Review and stress-test the technical constitution after /constitute.
Best use case
review_constitution is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Review and stress-test the technical constitution after /constitute.
Teams using review_constitution 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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/review_constitution/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How review_constitution Compares
| Feature / Agent | review_constitution | 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 and stress-test the technical constitution after /constitute.
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 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)
Related Skills
tech_review
Senior Principal Engineer performing thorough technical review of implementation plans before development.
skeptical_review
Perform a critical, skeptical code review of the project from the perspective of a Principal Engineer.
review_plan
Review the technical implementation plan against the specification.
review_domain
Perform a thorough architectural review of a domain model.
code_review
Thorough code review focusing on security, quality, and maintainability. Reviews implementation against plan and best practices.
wireframe
Create markdown wireframes with detailed UX descriptions from a product specification. Senior UX Designer perspective inspired by Notion and Linear.
ux_redesign
Redesign a feature or page from a Principal UX Designer's perspective.
tasks
Break down an approved implementation plan into specific, actionable tasks.
specify
Create a product specification that defines what to build and why, without prescribing how.
security_agent
Perform a full security review of the codebase (Node.js & React focus).
retro
Reflect on the completed feature, document lessons learned, and improve workflows.
release_gate
Final Go/No-Go check and release preparation.