name	suggest-members
user-invocable	false
description	Recommends team composition based on outcomes and mode. Invoked by launch commands during team setup.

Suggest additional team members based on the user's outcomes and selected mode. The lead and facilitator are always included.

Mode guidance:

Code mode — suggest a mix of technical and domain-specific voices. Include at least one member who represents the customer or business perspective (Director of Customer Success, RevOps lead, BizOps expert).
Writing mode — suggest writing-domain voices: strategist, editor, and at least one domain expert relevant to the subject matter. Researcher as needed. Avoid engineering roles unless the subject requires them.
General mode (the fallback when outcomes fit no specific mode) — suggest domain-relevant voices that match what the outcomes actually require. Include at least one member who represents the broader qualitative or business perspective.
Triage mode — suggest investigators who can gather and weigh evidence from where the symptom points (code, logs, metrics, traces, issue history, user reports); keep roles tool-agnostic (no hardcoded observability vendor); include at least one voice attentive to blast radius — what a change at the breaking point would disturb downstream. Do not apply the Code-mode customer/business-perspective default unless the outcomes call for it.
No mode provided — default to Code mode guidance.

Keep teams to 3-5 members total. Up to 8 for complex multi-domain work. All members except the lead are read-only.

Present your suggestion.

Rules when suggesting team members:

Avoid constraining dynamic team members too much. Over-describing what their qualities are can result in constrainment
Be careful of introducing biases which weren't prompted by the user.

Más de este repositorio

mismo repositorio

independent-review-loop

DheerG/swarms

Independent review loop run before delivery in code work. An independent reviewer (Codex, or fresh Codex-style subagents) reads the whole PR against the approved outcome; the lead fixes in-scope functional findings and re-reviews until none remain. Its differentiator is independence and exhaustiveness — a reviewer that fails differently from the authors, run to clean — distinct from the recursive-refinement ladder. Invoked by the team lead from the unified pre-ship gate (code-mode and /swarm:refine) after the ship steps.

2026-07-1282

workflow-rules

DheerG/swarms

Returns the universal governance spec for swarm team runs — hard rules, briefing templates, gate presentation contract, launch mechanics, and pulse setup. The canonical source: invoked by launch.md at Step 1 and by user-authored shortcut commands that cannot read launch.md directly. Per-gate constants live in swarm:gate-presentation.

2026-07-0982

gate-presentation

DheerG/swarms

Returns the frozen gate constants — question, header, option labels and descriptions, digest field-list, and preview content — for every catalog gate. Invoked by the team lead fresh on arrival at each gate and on pulse re-emissions, in the same turn as the render. The transport contract, three renders, partition rule, and authoring rubric live in swarm:workflow-rules.

2026-07-0882

code-mode

DheerG/swarms

Code mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for code-mode teams.

2026-07-0682

general-mode

DheerG/swarms

General mode operational spec for the team lead. Returns lead identity, facilitator identity, suggest-members guidance, and phase arc for general-purpose teams. The silent fallback when outcomes fit no specific mode, and a wrapper base for custom workflows — it has no shortcut command.

2026-07-0682

triage-mode

DheerG/swarms

Triage mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for triage teams that diagnose an issue without changing it.

2026-07-0682

name	suggest-members
user-invocable	false
description	Recommends team composition based on outcomes and mode. Invoked by launch commands during team setup.

Suggest additional team members based on the user's outcomes and selected mode. The lead and facilitator are always included.

Mode guidance:

Code mode — suggest a mix of technical and domain-specific voices. Include at least one member who represents the customer or business perspective (Director of Customer Success, RevOps lead, BizOps expert).
Writing mode — suggest writing-domain voices: strategist, editor, and at least one domain expert relevant to the subject matter. Researcher as needed. Avoid engineering roles unless the subject requires them.
General mode (the fallback when outcomes fit no specific mode) — suggest domain-relevant voices that match what the outcomes actually require. Include at least one member who represents the broader qualitative or business perspective.
Triage mode — suggest investigators who can gather and weigh evidence from where the symptom points (code, logs, metrics, traces, issue history, user reports); keep roles tool-agnostic (no hardcoded observability vendor); include at least one voice attentive to blast radius — what a change at the breaking point would disturb downstream. Do not apply the Code-mode customer/business-perspective default unless the outcomes call for it.
No mode provided — default to Code mode guidance.

Keep teams to 3-5 members total. Up to 8 for complex multi-domain work. All members except the lead are read-only.

Present your suggestion.

Rules when suggesting team members:

Avoid constraining dynamic team members too much. Over-describing what their qualities are can result in constrainment
Be careful of introducing biases which weren't prompted by the user.