Council Review¶

All changes must be reviewed by the LLM Council before merging.

Overview¶

The LLM Council is a multi-model consensus system that reviews code changes, architectural decisions, and documentation for quality and correctness.

Council Skills¶

Council skills are available in .agent/skills/:

Skill	Purpose
`council-gate`	CI/CD quality gate checks
`council-review`	Code review and feedback
`council-verify`	Verification against rubrics

Review Process¶

1. Create Feature Branch¶

git checkout -b feature/my-feature

2. Implement with TDD¶

Follow TDD Workflow.

3. Submit for Council Review¶

Use the council-review skill with reasoning tier for thorough analysis:

Review this change using reasoning tier:
- Files changed: [list files]
- Purpose: [describe intent]
- Tests: [list new/modified tests]

4. Address Feedback¶

Incorporate council recommendations
Re-run review if significant changes made
Document decisions in ADRs if architectural

5. Merge¶

Only merge after:

Reasoning Tier¶

For complex changes, use reasoning tier review:

More thorough analysis
Multiple perspectives considered
Higher confidence scores
Required for:
- ADRs
- Architectural changes
- Security-sensitive code
- Blog posts

Review Rubrics¶

Council reviews against documented rubrics in .agent/skills/*/references/:

Code Review Rubric - Code quality, patterns, testing
CI/CD Rubric - Pipeline correctness, security
General Rubric - Documentation, completeness

Example Review Request¶

Please review ADR-003 using reasoning tier:

## Context
Adding MkDocs documentation site for arbiter-bot.

## Files
- mkdocs.yml
- docs/adrs/003-documentation-site.md
- .github/workflows/docs.yml

## Review Criteria
1. Completeness - Does the ADR address the problem?
2. Alternatives - Were alternatives considered?
3. Security - Any concerns for public docs?
4. Maintainability - Long-term sustainability?