Weave Serene Bliss

Weave Serene Bliss

A three-lens aesthetic brainstorm-and-refine pipeline for DX, documentation, and developer-tooling UX work. Each of the three weave variant slots carries a different serene-DX lens, so a single invocation yields three independent aesthetic takes before the refine phase picks and polishes the strongest. Host-native sub-agents are the default; separate model CLIs are available by explicit choice.

When to Use

• Sphinx / MyST / docs site polish (badge styling, navigation, code fixture showcases, dark mode, mobile responsiveness)
• CLI / TUI output design — where logging and user-facing output need distinct visual channels
• Developer-tooling UX (error messages, empty states, onboarding flows)
• Component galleries, docs landing pages, and reference implementations where the output is consumed by humans reading docs

Do not use this for implementation work without a reference anchor named in the prompt — serene-DX prompts need something concrete to compare against.

The Three Serene Lenses

The lenses are exhaustive for serene-DX work — pick one aesthetic per invocation, not all four of the source-skill quality keywords. "Reader happiness" collapses into Serenity here; use it as a trigger phrase, not a fourth slot.

Context Packet Expectations

Weave builds a standard context packet for every invocation. For serene-DX work, make sure the host surfaces these fields before invoking, so each lens has something concrete to react to:

• Reference anchor — a file path, URL, or snippet of a known-good implementation to compare against (e.g., libtmux-mcp/custom.css, a reference Sphinx theme, a CLI whose output you admire).
• Current state — the file, markup, or screenshot description of what looks ugly or broken right now. Name the ugly element explicitly; "the badges look like an eyesore" beats "improve the badges."
• Constraint envelope — what must NOT change (branch, file scope, no mutations) and what must be preserved (accessibility, WCAG, dark mode, NO_COLOR / FORCE_COLOR handling, mobile responsiveness).
• Technology stack — Sphinx + MyST, Furo variables, React + Tailwind, Python stdlib-only, etc. Each lens responds differently to what's idiomatic in the stack.
• Known gaps / unknowns — open questions the participants should address rather than hand-wave past.

Anti-Patterns

• No reference anchor. Prompting for bliss / serenity / sublimity without a concrete comparison target produces generic advice from every lens. Always name a known-good implementation.
• No constraint envelope. Without explicit "do not modify files" and stack boundaries, models will start proposing edits instead of design critique.
• Mixing quality keywords in one invocation. The three slots already cover the range. Don't rephrase the prompt to ask for "bliss and serenity and sublimity at once" — that defeats the lens-differentiation that makes the brainstorm phase useful.
• Using this for implementation tasks. Serene-bliss is a design-research pattern. For actual code changes, run the weave-execute skill or the weave-prompt skill instead.

A first-class three-lens brainstorm-and-refine command for developer-experience, documentation, and tooling-UX design work. Three variant slots are fixed to three serene-DX aesthetic lenses — DX Bliss, DX Serenity, and DX Sublimity — and dispatched across independent adversarial workers in parallel. Host-native sub-agents are the default; separate model CLIs are optional. Each refine pass is judged by an adversarial worker panel, with verdicts merged via peer-only averaging to neutralize self-favoritism.

This is the only weave command that uses panel judging. For host or round-robin judging on user-defined variants, use the weave-brainstorm-and-refine skill instead.

This is a project-read-only command. Session artifacts land under $AI_AIP_ROOT, outside your repository.

The prompt comes from $ARGUMENTS. If no prompt is provided, ask the user what DX artifact, docs page, or tooling surface they want to brainstorm and refine under the serene lens.

Worker selection

Before any other unresolved configuration choice or operational step, read references/worker-backends.md. Resolve worker_backend from --workers=subagents|model-clis using that reference; if the flag is absent, ask its worker question first. If interactive choice is unavailable, honor its documented headless default.

The selected backend governs the whole session: dispatch, retry, judging, refinement, artifacts, session metadata, and presentation. The shared reference adapts provider-named examples across every later phase to that backend.

When worker_backend == subagents, use only the reference's native sub-agent path. Skip every model-CLI detection, timeout question, timeout resolution, retry, fallback, and dispatch instruction below. Every such instruction below is conditional on worker_backend == model-clis.

The Three Serene Lenses

The three slots are exhaustive for serene-DX work. "Reader happiness" collapses into Serenity; there is no fourth slot.

Compound Preamble (source of truth)

The compound preamble injected into each variant is a single paragraph (no embedded newlines) for shell-quoting safety. This file is the canonical location — the weave:serene-bliss skill references this block rather than duplicating it.

You are a developer-experience design expert. Apply the Serene DX aesthetic lens matching your variant slot. Variant 1 → DX Bliss: frictionless, delightful, zero-friction; make it feel effortless. Variant 2 → DX Serenity: calm, unhurried, information-architectural; make it feel like a quiet library. Variant 3 → DX Sublimity: awe, novel extensions, showcase-grade; make it feel like a first. Compare the current state to any concrete reference implementation named in the prompt, and name what is ugly or broken. Do NOT modify any files — research only.

Weave prepends "Variant N of M:" to this string automatically for each variant, so the compound preamble's slot directives route each model to the correct lens via its variant number.

Argument Handling

Scan $ARGUMENTS for --name=value flags anywhere in the text. Flags are stripped from the prompt text before sending to models, identical to brainstorm-and-refine's flag handling.

Reserved flags — if the user passed any of these, print one warning line at session start and strip them:

• --variants=* — serene-bliss locks --variants=3; the three-lens contract depends on it.
• --preamble=* — serene-bliss locks the compound preamble above.
• --judge=* — serene-bliss locks --judge=panel; users who want host or round-robin should run the weave-brainstorm-and-refine skill.

Warning line format (printed once, at the start of execution if any reserved flag was seen):

"Note: --variants, --preamble, and/or --judge were ignored — serene-bliss locks all three. Run the weave-brainstorm-and-refine skill directly for full control."

Passthrough flags — apply unchanged:

• --passes=N (default 2)
• --timeout=N|none
• --mode=fast|balanced|deep

Phase 1: Gather Context

Follow Phase 1 (Gather Context) of the weave-brainstorm-and-refine skill verbatim — read CLAUDE.md/AGENTS.md for project conventions, detect the trunk branch, capture the prompt from $ARGUMENTS. No serene-bliss-specific changes.

Phase 1b: Build Context Packet

Follow Phase 1b (Build Context Packet) of the weave-brainstorm-and-refine skill verbatim — assemble the structured context bundle that all models will receive.

For serene-DX work specifically, the host SHOULD ensure the context packet surfaces a reference anchor (a known-good implementation to compare against) and a constraint envelope (what must NOT change: files, branches, accessibility, dark mode, etc.). The compound preamble explicitly asks each model to compare against a reference, so this is load-bearing.

Phase 2: Configure and Detect Models

Follow Phase 2 (Configuration and Model Detection) of the weave-brainstorm-and-refine skill — flag parsing, mode/timeout/passes resolution, model detection (Claude, Antigravity, GPT), session directory setup — with these serene-bliss overrides applied after the standard parsing:

• Preserve the inherited worker_backend, participant artifact IDs, and executor mapping in session.json, plus worker_backend and participants in the session_start event. Record resolved models only for model-clis; omit the models field for subagents.
• variant_count = 3 (forced; override any --variants from $ARGUMENTS and emit the reserved-flag warning per the Argument Handling section above).
• user_preamble = <Compound Preamble block above> (forced; override any --preamble from $ARGUMENTS).
• judge_mode = panel (forced; override any --judge from $ARGUMENTS).
• pass_count default = 2 (matching brainstorm-and-refine's default).
• Session directory layout adds one path per pass: $SESSION_DIR/refine/pass-NNNN/judges/ for individual panel members' assessments, alongside the existing panel.md (the merged output) and woven.md (the weave-step result).

Panel Feasibility Check

After model detection completes, count the available models:

• 3 models available: Standard panel mode. Each output will be scored by 2 peer judges (its producing model is excluded by the peer-only rule). Proceed normally.
• 2 models available: Degraded panel. Print warning:

  "Warning: panel has 2 members ( not detected); scoring is single-peer rather than dual-peer." Each output will be scored by exactly 1 peer judge. Proceed.

• 1 model available (only Claude): Panel infeasible. Set judge_mode = host_fallback and print warning:

  "Warning: only Claude detected — panel is unavailable. Falling back to host judging for all passes." All judging will use the Host Judge Protocol from the weave-brainstorm-and-refine skill (Phase 5 Step 1, Host Judge Protocol).

Record the worker backend, participant artifact IDs, executor mapping, resolved models only for model-clis, resolved judge_mode, and panel member set in $SESSION_DIR/metadata.md.

Phase 3: Brainstorm — Dispatch Three Lens Variants Across All Models

Goal: Send the prompt to all available models simultaneously, with each model producing all three lens variants in parallel.

Variant Preambles (locked)

The variant preambles are FIXED for serene-bliss — the variant preamble table from brainstorm.md/brainstorm-and-refine.md does NOT apply. Instead, every variant receives the same compound preamble (above), prefixed by weave's standard "Variant N of M:" marker. The compound preamble's slot directives route each variant to its lens by variant number:

Prompt Preparation

For each variant N in {1, 2, 3}, write $SESSION_DIR/brainstorm/prompts/variant-<N>.md containing:

• Reasoning directive (first line): Think through the problem step-by-step and consider multiple angles before producing your final response.
• Variant N of 3: <Compound Preamble> (shell-safe single paragraph)
• The base user prompt (with reserved flags stripped)
• The context packet content

Create the prompts directory:

mkdir -p "$SESSION_DIR/brainstorm/prompts"

Also write $SESSION_DIR/brainstorm/prompt.md as a summary file listing the base prompt, the compound preamble, the three lens slot mappings, and a reference to the context packet.

Claude Variants (Task agents)

For each Claude variant N (1 through 3), launch a separate Task agent with subagent_type: "general-purpose":

Variant N of 3:

Respond to the following prompt about this codebase. Read any relevant files to give a thorough, original response. Read CLAUDE.md/AGENTS.md for project conventions.

Prompt: <user's prompt>

Read the context packet at $SESSION_DIR/context-packet.md for project context.

Provide a clear, well-structured response. Cite specific files and line numbers where relevant. CRITICAL: Do NOT write, edit, create, or delete any files in the repository. Do NOT use Write, Edit, or Bash commands that modify repository files. All session artifacts are written to $SESSION_DIR, which is outside the repository. This is a READ-ONLY research task.

Each Claude variant agent writes its output to $SESSION_DIR/brainstorm/outputs/claude-v<N>.md.

Antigravity Variants (sub-agents)

For each Antigravity variant N (1 through 3), launch a separate Task agent (subagent_type: "general-purpose", mode: "default") to execute the Antigravity (agy) model. Include in the agent prompt: the resolved backend command and timeout from Phase 2, the $SESSION_DIR path, the $REPO_TOPLEVEL path and $REPO_FINGERPRINT value, the variant number, and the prompt with the compound preamble.

The agent must:

1. Read the variant prompt from $SESSION_DIR/brainstorm/prompts/variant-<N>.md

2. Run the resolved Antigravity command with output redirection. Repo Guard: agy has no native read-only mode (its print mode reads and writes), so isolate it in a disposable git worktree checked out at HEAD — agy reads the snapshot while any stray write lands in the throwaway worktree, never the main repo (see docs/repo-guard-protocol.md Layer 1). Because multiple variants can run concurrently, each variant's worktree path carries its variant number (-v<N>) so parallel runs never share a worktree. The gemini and agent fallbacks keep their own native read-only modes.

   Primary (agy CLI, disposable worktree):

   (AGY_RO_WT="${REPO_TOPLEVEL}-weave-agy-ro-v<N>"; git -C "$REPO_TOPLEVEL" worktree remove --force "$AGY_RO_WT" 2>/dev/null; git -C "$REPO_TOPLEVEL" worktree add -q --detach "$AGY_RO_WT" HEAD && (cd "$AGY_RO_WT" && <timeout_cmd> <timeout_seconds> agy --model "Gemini 3.1 Pro (High)" --add-dir "$AGY_RO_WT" --dangerously-skip-permissions -p "$(cat "$SESSION_DIR/brainstorm/prompts/variant-<N>.md")" </dev/null >"$SESSION_DIR/brainstorm/outputs/agy-v<N>.md" 2>"$SESSION_DIR/brainstorm/stderr/agy-v<N>.txt"); rc=$?; git -C "$REPO_TOPLEVEL" worktree remove --force "$AGY_RO_WT" 2>/dev/null; exit "$rc")
   

   Fallback (gemini CLI):

   (cd "$SESSION_DIR" && <timeout_cmd> <timeout_seconds> gemini -m gemini-3-pro-preview --approval-mode plan --include-directories "$REPO_TOPLEVEL" --skip-trust -p "$(cat "$SESSION_DIR/brainstorm/prompts/variant-<N>.md")" >"$SESSION_DIR/brainstorm/outputs/agy-v<N>.md" 2>"$SESSION_DIR/brainstorm/stderr/agy-v<N>.txt")
   

   Fallback (agent CLI):

   (cd "$SESSION_DIR" && <timeout_cmd> <timeout_seconds> agent -p --mode plan --trust --workspace "$REPO_TOPLEVEL" --model gemini-3.1-pro "$(cat "$SESSION_DIR/brainstorm/prompts/variant-<N>.md")" >"$SESSION_DIR/brainstorm/outputs/agy-v<N>.md" 2>>"$SESSION_DIR/brainstorm/stderr/agy-v<N>.txt")
   

3. Repo Guard post-CLI verification: immediately after the CLI returns, check the repository state. If dirty, revert and log the violation:

   CURRENT_STATUS="$(git -C "$REPO_TOPLEVEL" status --porcelain)"
   

   If $CURRENT_STATUS differs from $REPO_FINGERPRINT:

   git -C "$REPO_TOPLEVEL" checkout -- . 2>/dev/null || true
   

   git -C "$REPO_TOPLEVEL" clean -fd 2>/dev/null || true
   

   printf '{"event":"repo_guard_violation","timestamp":"%s","model":"agy","reverted":true}\n' \
     "$(date -u '+%Y-%m-%dT%H:%M:%SZ')" \
     >>"$SESSION_DIR/guard-events.jsonl"
   

4. On failure: classify (timeout → retry with 1.5x timeout; rate-limit → retry after 10s; credit-exhausted → skip retry, escalate to the next backend immediately; crash → not retryable; empty → retry once), retry max once with same backend, then fall back down the chain (agy → gemini → agent) if a native CLI was used; if all are credit-exhausted or unavailable, use the lesser model (Gemini 3.5 Flash (High) via agy for Antigravity, then gemini-3-flash-preview).

5. Return: exit code, elapsed time, retry count, output file path.

GPT Variants (sub-agents)

For each GPT variant N (1 through 3), launch a separate Task agent (subagent_type: "general-purpose", mode: "default") to execute the GPT model. Same dispatch shape as Antigravity, with these command replacements. Include $REPO_TOPLEVEL and $REPO_FINGERPRINT in the agent prompt for post-CLI verification.

Repo Guard: invoke the CLI in its native read-only sandbox — it reads the repo but cannot write it (see docs/repo-guard-protocol.md Layer 1).

Native (codex CLI):

(cd "$SESSION_DIR" && <timeout_cmd> <timeout_seconds> codex exec -s read-only -C "$REPO_TOPLEVEL" --skip-git-repo-check </dev/null -c model_reasoning_effort=medium "$(cat "$SESSION_DIR/brainstorm/prompts/variant-<N>.md")" >"$SESSION_DIR/brainstorm/outputs/gpt-v<N>.md" 2>"$SESSION_DIR/brainstorm/stderr/gpt-v<N>.txt")

Fallback (agent CLI):

(cd "$SESSION_DIR" && <timeout_cmd> <timeout_seconds> agent -p --mode plan --trust --workspace "$REPO_TOPLEVEL" --model gpt-5.4-high "$(cat "$SESSION_DIR/brainstorm/prompts/variant-<N>.md")" >"$SESSION_DIR/brainstorm/outputs/gpt-v<N>.md" 2>>"$SESSION_DIR/brainstorm/stderr/gpt-v<N>.txt")

Repo Guard post-CLI verification: immediately after the CLI returns, check the repository state. If dirty, revert and log:

CURRENT_STATUS="$(git -C "$REPO_TOPLEVEL" status --porcelain)"

If $CURRENT_STATUS differs from $REPO_FINGERPRINT:

git -C "$REPO_TOPLEVEL" checkout -- . 2>/dev/null || true

git -C "$REPO_TOPLEVEL" clean -fd 2>/dev/null || true

printf '{"event":"repo_guard_violation","timestamp":"%s","model":"gpt","reverted":true}\n' \
  "$(date -u '+%Y-%m-%dT%H:%M:%SZ')" \
  >>"$SESSION_DIR/guard-events.jsonl"

Same retry/fallback classification as Antigravity. Lesser model fallback: gpt-5.4-mini via agent.

Execution Strategy

• Launch ALL model × variant agents in the same turn to execute simultaneously. With 3 models × 3 variants = up to 9 parallel dispatches per session. If parallel dispatch is unavailable, launch sequentially — Phase 4 tolerates partial results.
• Each variant MUST be a separate, independent prompt invocation. Never send multiple variants to the same model in a single prompt — this prevents anchoring across lens slots.
• Each sub-agent handles its own retry and fallback protocol internally.
• After all agents return, verify output files exist in $SESSION_DIR/brainstorm/outputs/.
• If a sub-agent reports failure after exhausting retries, mark that model variant as unavailable in session.json and continue. The presentation phase will display partial results.

Phase 4: Present Originals and Transition Gate

Follow Phase 4 (Present Brainstorm Results and Transition Gate) of the weave-brainstorm-and-refine skill verbatim. Present all successful brainstorm originals to the user, ask which ones enter refinement via ask-user-choice, update session.json to phase: "refine", and proceed.

If the user selects "None", end the session and report the brainstorm artifacts only.

Phase 5: Panel Judge — First Refine Pass

This phase introduces the Panel Judge Protocol — net-new to serene-bliss. All available models judge in parallel and their verdicts are merged via peer-only averaging.

Step 1: Build the shared judge prompt

The panel judges share a single prompt. Build it identically to the External Judge Protocol section of the weave-refine skill — scoring rubric (4 dimensions × 0-10), expected output format (scores table, winner, rationale, runner-up analysis), and ALL selected originals included inline (external models cannot read session files).

Prepend this additional instruction to the standard External Judge Protocol prompt:

"You are one of three judges on a panel. Score every output honestly including outputs from your own model. Do not self-favor — the merge step will exclude your self-scores automatically via peer-only averaging. Rate each output on the four dimensions (Quality, Originality, Completeness, Coherence) on a 0-10 scale."

Write the shared prompt to $SESSION_DIR/refine/pass-0001/panel-prompt.md.

Step 2: Dispatch panel judges in parallel

Launch one judge per available model in the same turn:

• Claude judge: Task agent with subagent_type: "general-purpose" receiving the panel-prompt content directly. Writes assessment to $SESSION_DIR/refine/pass-0001/judges/claude.md.

• Antigravity judge: sub-agent dispatching the agy CLI primary (or gemini/agent fallback) with the shared prompt as input. Same retry/fallback protocol as Phase 3 Antigravity variants. agy has no native read-only mode, so isolate it in a disposable git worktree named ${REPO_TOPLEVEL}-weave-agy-ro-judge (a SEPARATE worktree from any model-pass run so the two never collide; see docs/repo-guard-protocol.md Layer 1). Writes to $SESSION_DIR/refine/pass-0001/judges/agy.md.

  Primary (agy CLI, disposable worktree):

  (AGY_RO_WT="${REPO_TOPLEVEL}-weave-agy-ro-judge"; git -C "$REPO_TOPLEVEL" worktree remove --force "$AGY_RO_WT" 2>/dev/null; git -C "$REPO_TOPLEVEL" worktree add -q --detach "$AGY_RO_WT" HEAD && (cd "$AGY_RO_WT" && <timeout_cmd> <timeout_seconds> agy --model "Gemini 3.1 Pro (High)" --add-dir "$AGY_RO_WT" --dangerously-skip-permissions -p "$(cat "$SESSION_DIR/refine/pass-0001/panel-prompt.md")" </dev/null >"$SESSION_DIR/refine/pass-0001/judges/agy.md" 2>"$SESSION_DIR/refine/pass-0001/judges/judge-agy.txt"); rc=$?; git -C "$REPO_TOPLEVEL" worktree remove --force "$AGY_RO_WT" 2>/dev/null; exit "$rc")
  

  Fallback (gemini CLI):

  (cd "$SESSION_DIR" && <timeout_cmd> <timeout_seconds> gemini -m gemini-3-pro-preview --approval-mode plan --include-directories "$REPO_TOPLEVEL" --skip-trust -p "$(cat "$SESSION_DIR/refine/pass-0001/panel-prompt.md")" >"$SESSION_DIR/refine/pass-0001/judges/agy.md" 2>"$SESSION_DIR/refine/pass-0001/judges/judge-agy.txt")
  

  Fallback (agent CLI):

  (cd "$SESSION_DIR" && <timeout_cmd> <timeout_seconds> agent -p --mode plan --trust --workspace "$REPO_TOPLEVEL" --model gemini-3.1-pro "$(cat "$SESSION_DIR/refine/pass-0001/panel-prompt.md")" >"$SESSION_DIR/refine/pass-0001/judges/agy.md" 2>>"$SESSION_DIR/refine/pass-0001/judges/judge-agy.txt")
  

• GPT judge: sub-agent dispatching the codex CLI (or agent fallback) with the shared prompt as input. Same retry/fallback protocol as Phase 3 GPT variants. Writes to $SESSION_DIR/refine/pass-0001/judges/gpt.md.

Repo Guard: the GPT judge CLI must use the same native read-only sandbox invocation as Phase 3 variant dispatches, and the Antigravity judge must run inside its -judge disposable worktree as above (see docs/repo-guard-protocol.md Layer 1). After each judge CLI returns, run the post-CLI repo state verification — capture CURRENT_STATUS="$(git -C "$REPO_TOPLEVEL" status --porcelain)", and if $CURRENT_STATUS differs from $REPO_FINGERPRINT, revert and log the violation to $SESSION_DIR/guard-events.jsonl with the judge's model name.

Each judge file uses the standard judge assessment format (scores table, winner, rationale, runner-up analysis) with this header:

# Judge's Assessment — Pass 1
**Judged by**: <model> (panel member, peer-only averaging)

If only 2 models are available (degraded panel), launch 2 judges and proceed. If only Claude is available (panel infeasible), skip Phase 5 Steps 1-4 entirely and use the Host Judge Protocol from the weave-brainstorm-and-refine skill (Phase 5 Step 1, Host Judge Protocol).

Step 3: Parse judge responses

For each judge that completed dispatch:

1. Read the judge file from $SESSION_DIR/refine/pass-0001/judges/<model>.md.
2. Attempt to parse the scores table (originals × 4 dimensions), declared winner, rationale, and runner-up analysis.
3. On parse failure: log a warning to $SESSION_DIR/refine/pass-0001/parse-errors.txt and exclude this judge from the merge step.
4. On dispatch failure (reported by Step 2's sub-agent): also exclude.

Full-panel failure fallback: if 0 judges succeed (all parse or dispatch failed), fall back to the Host Judge Protocol from the weave-brainstorm-and-refine skill (Phase 5 Step 1, Host Judge Protocol). Run that protocol now and produce a single judge.md file. Mark the resulting panel.md (Step 4) as **Judged by**: Claude (fallback — all panel judges failed) and include the full host judgment inline.

Step 4: Merge via peer-only averaging

For each successfully-parsed judge, the input is a scores table where each row is one original (e.g., claude-v1, agy-v2, gpt-v3) and each column is a dimension score (0-10).

Peer-only averaging algorithm (described in prose; the host implements this directly):

For each original O in the pass's review set:

1. Identify the producer model for O from its label (e.g., claude-v2 → producer = Claude; agy-v1 → producer = Antigravity).
2. For each successfully-parsed judge J:
   • If J is the same as the producer: exclude this judge's score for O (peer-only rule).
   • Otherwise: include J's 4 dimension scores in the per-dimension accumulators for O.
3. Compute the merged per-dimension scores for O as the arithmetic mean of the included judges' scores.
4. Compute the merged total for O as the sum of merged per-dimension scores (0-40).

After all originals have merged scores:

5. Winner = the original with the highest merged total.
6. Tie resolution: if 2+ originals share the highest merged total, the host (Claude) picks among them and writes a 1-paragraph tie-break rationale into panel.md.

Merged runner-up analysis: read the runner-up sections from each parsed judge file, deduplicate strengths that multiple judges noted (collapse to one bullet with (N/3 judges) annotation), and preserve unique observations from each judge.

Write the merged assessment to $SESSION_DIR/refine/pass-0001/panel.md using this template:

# Panel Assessment — Pass 1
**Judged by**: Panel (Claude + Antigravity + GPT, peer-only averaging)
**Judges succeeded**: 3/3   <!-- or "2/3 (agy parse failed)" etc. -->

## Individual Scores
| Original   | Claude | Antigravity | GPT  | Merged (peer-only) |
|------------|--------|-------------|------|---------------------|
| claude-v1  |   —    |  33         |  31  |  32 / 40            |
| claude-v2  |   —    |  28         |  35  |  31 / 40            |
| agy-v1     |  34    |   —         |  30  |  32 / 40            |
| agy-v2     |  31    |   —         |  29  |  30 / 40            |
| gpt-v1     |  32    |  30         |   —  |  31 / 40            |
| ...        |  ...   |  ...        | ...  |  ...                |

(em-dashes mark self-scores excluded by the peer-only rule)

## Winner
**<label>** — merged score XX / 40
<!-- if tie: "tied with <other>, broken by host: <rationale>" -->

## Merged Runner-Up Analysis

### <label> (N/3 judges agree)
- <strength noted by multiple judges>

### <label> (1/3 judge — Claude only)
- <unique observation>

## Individual Judge Summaries
- **Claude**: picked <label>; emphasized <one-line rationale>
- **Antigravity**: picked <label>; emphasized <one-line rationale>
- **GPT**: picked <label>; emphasized <one-line rationale>

## Merge Notes
- Peer-only averaging: each original's score excludes the producing
  model's self-assessment.
- Tie resolution: <"none" | "host arbitrated between A and B">.

Step 5: Weave

Follow Phase 5 Steps 2-3 (Analyze Runners-Up and Weave) of the weave-brainstorm-and-refine skill verbatim, with one substitution: read panel.md (this command's merged assessment) instead of judge.md. The host (Claude) constructs the woven version incorporating the winner plus runner-up strengths and writes it to $SESSION_DIR/refine/pass-0001/woven.md.

Step 6: Distribute (if pass_count > 1)

Follow Phase 5 Step 4 (Distribute for Pass 2) of brainstorm-and-refine.md verbatim. Send the woven version back to all 3 models for the next pass's critique.

Phase 6: Panel Judge — Subsequent Passes

Repeat Phase 5 Steps 1-6 for each pass from 2 through pass_count. The panel composition is stable across passes — no rotation, no membership changes (this is the key difference from brainstorm-and-refine's round-robin mode, where the judge rotates).

For each subsequent pass N:

• Input under review = output of pass N-1 (each model's critique of the previous woven version).
• Judges = the same panel members detected in Phase 2.
• Merge step = peer-only averaging as in Phase 5 Step 4.
• Output paths use pass-NNNN (zero-padded) consistently.

Early-stop detection mirrors Phase 6 Step 5 (Early-Stop Detection) of the weave-brainstorm-and-refine skill: if the woven version of pass N is substantially identical to the woven version of pass N-1, stop early and skip to Phase 7.

The final pass skips Step 6 (distribute) — there is no next pass to prepare for.

Phase 7: Present Final Result

Step 0: Deslop Pass

Unless --no-deslop was set, read references/deslop-pass.md and apply it with:

• ARTIFACT_PATH = $SESSION_DIR/refine/pass-<final>/woven.md
• SESSION_DIR = $SESSION_DIR
• BASELINE_SHA = the trunk SHA captured by the repo guard
• DESLOP_MODE = quiet if --quiet-deslop, verbose if --verbose-deslop, else default

Step 1: Present the result

Read references/present-results.md and apply it with:

• RESULT_KIND = serene-bliss
• ARTIFACT_PATH = $SESSION_DIR/refine/pass-<final>/woven.md
• SESSION_DIR = $SESSION_DIR
• PASS_COUNT = the number of completed refine passes
• IN_PLAN_MODE = false
• WORKER_BACKEND = worker_backend
• PARTICIPANTS = the successful participant artifact IDs
• EXECUTORS = the resolved participant artifact ID to executor mapping
• MODELS = resolved models when worker_backend == model-clis; otherwise null
• LABEL_MAP_PATH = $SESSION_DIR/refine/pass-NNNN/label-map.json

In the presentation, include one additional line: "Judged by: Panel (Claude + Antigravity + GPT, peer-only averaging) across N pass(es)."

After the reference returns, finalize the session: repo guard, session.json, events.jsonl, latest symlink.

Portability notes

• ask-user-choice — follow the source's choice contract. Hosts with a structured multiple-choice tool (Claude Code's AskUserQuestion) should use it. Honor a documented headless default when the source defines one; otherwise print a numbered list and wait for a numbered reply. Never invent a choice.
• $ARGUMENTS — the text the user passed when invoking this skill. If your host does not substitute it, read it as the user's request in the current turn, and ask when there is none.
• Bundled files — every relative path in this skill points at a file shipped inside this skill directory. Read them from here, not from the host's plugin tree.