Back to list
deepeshBodh

validation-constitution

by deepeshBodh

SPEC-first multi-agent framework for Claude Code.

7🍴 0📅 Jan 24, 2026

SKILL.md


name: validation-constitution description: This skill should be used when the user asks to "review constitution", "validate principles", "check quality", or mentions "constitution review", "quality check", "version bump", "anti-patterns", or "constitution audit". Provides checklists, anti-pattern detection, and version bump guidance.

Validating Constitution

Purpose

Verify constitution quality before finalization. This skill provides checklists, anti-pattern detection, and version bump guidance. Use after authoring with authoring-constitution or brownfield-constitution skills.

Quantification Requirements

Vague language MUST be replaced with measurable criteria:

VagueQuantified
"Code should be clean""Zero lint warnings from configured rules"
"Functions should be short""Functions MUST NOT exceed 40 lines"
"Tests should cover the code""Coverage MUST be ≥80% for new code"
"Response should be fast""API MUST respond in <200ms p95"
"Secure by default""All inputs MUST be validated; auth required on all endpoints"

Version Bump Rules

BumpTriggerExample
MAJORPrinciple removedRemoving "Test-First" principle
MAJORIncompatible redefinitionChanging coverage from 80% to 50%
MINORNew principle addedAdding "Observability" principle
MINORSignificant expansionAdding 5 new rules to existing principle
PATCHClarificationRewording for clarity, typo fixes
PATCHNon-semantic changeFormatting, comment updates

Quality Checklist

Before finalizing a constitution, verify all items in QUALITY-CHECKLIST.md.

Summary of checks:

  • Principle Quality (Enforcement, Testability, Rationale present)
  • Structure Quality (all mandatory sections)
  • No Placeholders Rule (actual tools, not [PLACEHOLDER])
  • Governance Quality (versioning, amendment process)

Anti-Patterns to Avoid

See ANTI-PATTERNS.md for common mistakes and fixes.

Quick reference:

Anti-PatternFix
Vague principleDefine specific metrics
Missing enforcementAdd CI check, code review rule, or audit
Untestable ruleDefine layer rules with import constraints
Cargo-cult ruleAdd rationale explaining the "why"
Over-engineeringStart with 5-7 core principles
No escape hatchDefine exception registry
Placeholder syndromeUse detected tools or industry defaults
Generic thresholdsSpecify numeric values

Workflow

  1. After authoring: Run through the Quality Checklist
  2. Review each principle: Verify three-part rule (Enforcement/Testability/Rationale)
  3. Check for anti-patterns: Compare against common mistakes
  4. Determine version bump: Use Version Bump Rules table
  5. Final sign-off: All checklist items pass

Score

Total Score

65/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon