Validate constitution quality with checklists, anti-pattern detection, and version bump rules. Use after writing constitution content, when reviewing constitutions, or when you see "constitution review", "quality check", "version bump", "anti-patterns", or "constitution audit".
Validates constitution quality with checklists, anti-pattern detection, and version bump rules.
/plugin marketplace add deepeshBodh/human-in-loop/plugin install deepeshbodh-humaninloop-plugins-humaninloop@deepeshBodh/human-in-loopThis skill inherits all available tools. When active, it can use any tool Claude has access to.
ANTI-PATTERNS.mdQUALITY-CHECKLIST.mdVerify 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.
Vague language MUST be replaced with measurable criteria:
| Vague | Quantified |
|---|---|
| "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" |
| Bump | Trigger | Example |
|---|---|---|
| MAJOR | Principle removed | Removing "Test-First" principle |
| MAJOR | Incompatible redefinition | Changing coverage from 80% to 50% |
| MINOR | New principle added | Adding "Observability" principle |
| MINOR | Significant expansion | Adding 5 new rules to existing principle |
| PATCH | Clarification | Rewording for clarity, typo fixes |
| PATCH | Non-semantic change | Formatting, comment updates |
Before finalizing a constitution, verify all items in QUALITY-CHECKLIST.md.
Summary of checks:
[PLACEHOLDER])See ANTI-PATTERNS.md for common mistakes and fixes.
Quick reference:
| Anti-Pattern | Fix |
|---|---|
| Vague principle | Define specific metrics |
| Missing enforcement | Add CI check, code review rule, or audit |
| Untestable rule | Define layer rules with import constraints |
| Cargo-cult rule | Add rationale explaining the "why" |
| Over-engineering | Start with 5-7 core principles |
| No escape hatch | Define exception registry |
| Placeholder syndrome | Use detected tools or industry defaults |
| Generic thresholds | Specify numeric values |
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.