28 lines
1.4 KiB
Markdown
28 lines
1.4 KiB
Markdown
|
---
|
||
|
|
description: Summon a Council of Experts to review the current planning artifact. Defaults to a phase-appropriate council; accepts an explicit council list. Use when you want a stress-test of what you've drafted before moving on.
|
||
|
|
arguments:
|
||
|
|
- name: artifact
|
||
|
|
description: Optional artifact name (e.g. "scope", "requirements", "architecture", "log-feeding"). Defaults to whatever Composer thinks the current phase is.
|
||
|
|
required: false
|
||
|
|
- name: council
|
||
|
|
description: Optional explicit comma-separated council member names (e.g. "Vera,Lena,Femi"). Overrides the phase default.
|
||
|
|
required: false
|
||
|
|
---
|
||
|
|
|
||
|
|
Invoke the `composer` skill in *review* mode with `$ARGUMENTS`.
|
||
|
|
|
||
|
|
The skill will:
|
||
|
|
|
||
|
|
1. Identify which artifact to review — the one named, or the current phase's artifact.
|
||
|
|
2. Pick a council. Defaults from the phase boundary (see `CLAUDE.md`); user
|
||
|
|
override accepted. Composer also auto-adds members when content suggests
|
||
|
|
their domain (PII → Camila, money → Ingrid, regulated data flows → Femi).
|
||
|
|
3. Read the artifact and any upstream context the council needs.
|
||
|
|
4. Hand off to the `council-of-experts:council` skill with the question framed
|
||
|
|
for the artifact under review.
|
||
|
|
5. Record the synthesis and suggested takeaways in
|
||
|
|
`docs/planning/reviews/<artifact>-<date>.md` so future phases see prior feedback.
|
||
|
|
|
||
|
|
The output is the council's standard format: each member in their own voice,
|
||
|
|
then agreements, disagreements, and prioritized takeaways.
|