agentleFS
June74June74/agentic-workflow/skills/convene/SKILL.md

convene

Skill0 starsChanged 3 months agoMITView on GitHub

Use when flag-check says a step convenes. Runs the blind-draft, critique, converge loop across a team and emits a decision record. Never used for unflagged work.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before dispatching anything, write down the criteria the drafts will be judged on, and put them in the brief.

    line 13
  2. Very specific:

    Never a bare task name like write-state-model shared across members, and never a title already used in this run for anything else.

    line 39
  3. Distinctive:

    A returned session is not proof the brief arrived: Put a short echo token in the brief — the DR id plus the number of named criteria — and …

    line 45
  4. Distinctive:

    Check the echo before counting anything as a draft:

    line 53
  5. Very specific:

    Do not batch the writes until the end.

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Convene

Four steps, in order. Skipping step 1's isolation destroys the point of the whole exercise.

0. Name the criteria FIRST

Before dispatching anything, write down the criteria the drafts will be judged on, and put them in the brief. Criteria invented after the drafts arrive get reverse-engineered to favor whichever draft you already liked.

1. Blind draft

Dispatch each member with sys_session_send as a separate session carrying the same brief. They must not receive each other's drafts, summaries of each other's drafts, or hints about who else is drafting.

This isolation is the anti-deference mechanism. It is structural: a member cannot defer to a stronger peer it cannot see. Members will infer each other's identity from writing style eventually — that is fine, because by then the drafts are already committed.

Titles are continuation keys — make them unique

sys_session_send does spawn-or-continue keyed on title. Reusing a title continues that conversation rather than starting a new one. So every dispatch gets a title unique to that decision and that member:

DR-0002-draft-sm-a      DR-0002-critique-sm-a
DR-0002-draft-sm-b      DR-0002-critique-sm-b

Never a bare task name like write-state-model shared across members, and never a title already used in this run for anything else. Prefer sys_session_create when you need a guaranteed-fresh session.

Validate that each draft answers the brief

A returned session is not proof the brief arrived. Put a short echo token in the brief — the DR id plus the number of named criteria — and require each draft to open with it:

DR-0002 / 5 criteria

Check the echo before counting anything as a draft:

  • Echo matches → a real draft.
  • Echo missing or wrong → the dispatch was misbound. That is not a draft and not an agent error. Discard it, re-dispatch on a fresh session with a new unique title, and record that it happened.
  • Misbinds twice for the same member → halt. The session layer is broken and continuing will silently shrink the council below its threshold.

This guard is deliberately mechanism-independent. It catches a misbound brief whatever the cause — title collision, duplicated conversation, replayed completion signal — because it tests the only thing that matters: did this member answer this question?

Collect with sys_read_inbox. Never busy-poll.

Failure mode to avoid: helpfully passing draft A into B's context to "save a round trip." That converts three independent positions into one position with two endorsements.

Write each draft to disk the moment it arrives

Do not batch the writes until the end. Write draft-a.md when A returns, before collecting anything else. An interrupted convene that wrote nothing loses every draft it paid for — a session transcript is not durable storage, and it is the layer most likely to have failed in the first place.

2. Reveal and critique

Reveal all drafts under neutral labels — SM-A / SM-B / SM-C, UX-A / UX-B. Never name models, at any point, in any artifact.

Each member critiques every draft including its own, against the named criteria and only those. A critique names what breaks, under what input, with what consequence. "I prefer B" is a vote, not a critique.

3. Converge

Apply merge-guard. Pick one draft as-is, or merge only if a criterion can be named on which the merged idea beats every input.

Two full rounds without convergence is a deadlock — run escalate. Do not run a third round hoping it resolves; it will produce the average you were trying to avoid.

4. Record

Emit a Decision Record with decision-record, and write the convene's artifacts to .agentic/convenes/<id>/:

.agentic/convenes/<id>/
  brief.md          the task and the criteria, as sent
  draft-a.md  draft-b.md  draft-c.md
  critiques.md
  decision.md       the Decision Record

The record is the durable output. Six months from now the code will have moved and the reasoning will not be recoverable from it. If a convene produced no record, it produced nothing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.