council

Files (1)

• SKILL.md

SKILL.md (first lines)

# council

Karpathy-style three-stage deliberation, run on real, different-vendor lanes. Read the harvest scorecard + assumptions first. Do not re-research.

The graph gives each seat its own card on its own vendor's lane. A seat with no available lane is written as `Verdict: ABSENT` by hbs. **Never impersonate a seat.** Your card's `Args` tell you the stage and your seat.

## Stage 1 — independent opinion (`stage: 1`, one card per seat)

- Do not read other seats' files.
- Write `build/06-council/<seat>.md` from `~/.build-framework/templates/build/06-council/vote.md`:
  Verdict (Approve / Concern / Block), three bullets, and "would change my vote if".

## Stage 2 — anonymized peer review (`stage: 2`, one card per seat)

1. `hbs council anonymize --repo <repo>` (idempotent; the first reviewer creates it).
2. Read only `build/06-council/anon/Response-*.md`. Skip the one that is yours.
3. Write `build/06-council/review-<seat>.md`: rank the others by letter for accuracy and insight, and "what others got wrong".

## Stage 3 — chairman (`stage: 3`)

1. `hbs council unmask --repo <repo>` → writes `peer-review.md` with the label map in its footer.
2. Write `build/06-council/chairman.md`:
   - Agreements
   - Tensions
   - Blocks (a single seat's Block is carried, not outvoted)
   - Recommended path
   - What would reopen the decision
   - ABSENT seats, named
   - `- Verdict: Approve | Concern | Block` (merged)
3. The chairman merges; the chairman does not campaign for its own seat's view.
4. Merged verdict **Block** → `kanban_block(reason="COUNCIL BLOCK: <what would reopen it>")`. hbs re-harvests once (the decision loop), then leaves it to the human.
   Otherwise complete the card.

## Manual council (no harness lanes yet)

You are the router: paste the scorecard into each vendor's app, save each answer as `build/06-council/<seat>.md`, then run stages 2 and 3 above in any tool.

From Kshintak/new-build-framework, MIT.

More from Kshintak/new-build-framework