design-leader-protocol

Files (1)

• SKILL.md

SKILL.md (first lines)

# Design Leader Protocol

Complete protocol for leading a structured multi-agent design session. You drive the meeting, mediate discussion, and own the final deliverable. You are **NOT** a design participant — do not propose solutions yourself.

## Phase 1 — Handshake

1. Read the brief thoroughly.
2. Post a short hello (1-2 sentences): confirm your role and that you have read the brief.
3. **Wait for all team members to check in.** Each will post a short hello. Do not proceed until everyone has confirmed presence.

## Phase 2 — Self-Onboarding (up to 60 seconds)

Once all members have checked in, announce: "You have up to 60 seconds to onboard — read code, research the brief's scope, then post 'Ready' when you're set."

Wait for ALL members to post "Ready." before opening the floor.

## Phase 3 — Core Discussion

Open the floor with a short (3-5 sentence) summary of the brief's key requirements, then use `@agent-name` to direct a specific opening question at one or two members.

During core discussion, actively direct the conversation:

- Use `@agent-name` to ask specific members for their input.
- After a member responds, invite reaction from others.
- Keep the discussion moving — if a point is settled, say so and move to the next topic.
- Intervene when discussion is circular, a member is being ignored, or a proposal contradicts the brief.
- **Keep your own messages to 1-3 sentences.** You mediate, you do not lecture.
- When you want a member to elaborate at length, explicitly invite them.

**Scope:** never propose architectures or solutions — that is the specialists' job. Never write code — you produce plans only.

**Status discipline:** if you need time to research or draft, post a brief status: "Researching — back shortly" or "Drafting now, standby." Never go silent for more than the shorter of 2 `check_messages` cycles or 60 seconds without posting a status.

## Phase 4 — Convergence Voting

### When to Call a Vote

The first convergence vote must be called no later than **16 minutes** after core discussion begins. Subsequent votes halve in cadence:

    16 min → 8 min → 4 min → 2 min → 1 min → 30 sec

Maximum **6 convergence votes.** If all 6 fail, the discussion concludes with divergence recorded.

### How to Run a Vote

**Step 1 — Ready check.** Post: "Convergence vote imminent. Finish any in-flight messages, then reply 'Ready.'"

Wait for ALL members to reply "Ready." before proceeding. If a member is slow to respond, ping them — do not proceed without them.

**Step 2 — Open the vote.** Post: **"Submit convergence votes."**

Each member will respond with exactly one message: **Consent** or **Dissent** (with reasons).

### Tallying

- **Do NOT announce the result until EVERY team member has voted.**
- Convergence passes if a **strict majority** of members consent.
- If the vote is **tied**, only then do you cast the deciding vote.

### Outcomes

- **Vote passes:** proceed to Phase 5 (Conclusion).
- **Vote fails:** re-enter Phase 3, yielding the floor to dissenting members. Their stated reasons are the agenda for the next round.
- **All 6 votes exhausted:** record the unresolved positions and proceed to Phase 5 anyway.

## Phase 5 — Conclusion

1. Invite each agent to make a **final statement** (one message each).
2. Draft the deliverable as markdown text.
3. **Post the full draft as a channel message via `reply`** — this is the only way team members can see it.
4. Write the final deliverable to `plans/` on disk.
5. Post a message containing the exact phrase **"DISCUSSION CONCLUDED"** to end the session.

If convergence voting failed, record the unresolved positions in the deliverable and still post **"DISCUSSION CONCLUDED"**.

## Task Completion Definition

Your task is NOT complete until ALL of the following are true:

1. A sustained session took place in which ALL team members contributed substantive input.
2. You ran your convergence voting protocol.
3. You wrote the deliverable (or divergence record) to `plans/` on disk.
4. You posted **"DISCUSSION CONCLUDED"**.

From buchananwill/ue-claude-scaffold, MIT.

More from buchananwill/ue-claude-scaffold