57 lines
2.9 KiB
Markdown
57 lines
2.9 KiB
Markdown
---
|
|
name: council-review
|
|
description: Structured three-reviewer brainstorming and review through a bundled orch CLI. Use when an agent needs a high-level council workflow on top of orch to launch reviewer roles, wait for their outputs, tally grouped recommendations, and report consensus, majority, and minority findings.
|
|
---
|
|
|
|
# Council Review
|
|
|
|
Use the bundled `./assets/orch` CLI to run the high-level `orch council ...` workflow.
|
|
|
|
## Quick Start
|
|
|
|
- Invoke `./assets/orch` relative to this skill directory.
|
|
- Pass `--db` explicitly for every command.
|
|
- Prefer `--json` whenever another agent or script will read the output.
|
|
- Treat this skill as a high-level workflow on top of `orch`, not as a separate infrastructure layer.
|
|
|
|
## Reviewer Roles
|
|
|
|
- `architecture-reviewer`
|
|
- `implementation-reviewer`
|
|
- `risk-reviewer`
|
|
|
|
## Rules
|
|
|
|
- Use this skill when the user explicitly wants a multi-reviewer brainstorm or review.
|
|
- Treat the workflow as analysis-first unless the user explicitly asks for patch proposals or code-change recommendations.
|
|
- Use `orch council` as the execution surface for start, wait, tally, and report.
|
|
- Default to the fixed reviewer roles architecture, implementation, and risk.
|
|
- Collect all three reviewer outputs before tallying.
|
|
- Use `normal` similarity unless the user asks for stricter grouping.
|
|
- If the user asks for unanimous-only output, rely on `--only-unanimous` and expect default report output to show only `consensus`.
|
|
- Otherwise present `consensus` first, then `majority`, and include `minority` when requested.
|
|
- Support text, repository, mixed, or task-target context when available.
|
|
|
|
## Typical Commands
|
|
|
|
```bash
|
|
./assets/orch --db ./coord.db --json council start --run council_blog_001 --target-file brief.md --target-type mixed --mode brainstorm --output both
|
|
./assets/orch --db ./coord.db --json council wait --run council_blog_001 --timeout-seconds 900
|
|
./assets/orch --db ./coord.db --json council tally --run council_blog_001 --similarity normal
|
|
./assets/orch --db ./coord.db --json council report --run council_blog_001 --show consensus,majority
|
|
```
|
|
|
|
## Command Map
|
|
|
|
- `council start`: create the council run and dispatch the three reviewer tasks
|
|
- `council wait`: block until all reviewers finish or timeout is reached
|
|
- `council tally`: parse reviewer outputs, group similar findings, and count support
|
|
- `council report`: render the final grouped council output and persist report metadata
|
|
|
|
## Notes
|
|
|
|
- This skill depends on the underlying `orch` orchestration model and persists its run state, grouped findings, and report metadata there.
|
|
- Use `council wait` before `council tally`, and `council tally` before `council report`.
|
|
- `council report` defaults to `consensus,majority`, except unanimous-only runs where the default is `consensus`.
|
|
- If the bundled binary cannot execute on the current host, stop and report the compatibility issue instead of guessing a replacement path or workflow.
|