boost-skill-cli 1.2.116__tar.gz → 1.2.118__tar.gz

{boost_skill_cli-1.2.116/boost_skill_cli.egg-info → boost_skill_cli-1.2.118}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.2.116
+Version: 1.2.118
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License-Expression: Apache-2.0

{boost_skill_cli-1.2.116 → boost_skill_cli-1.2.118}/boost_cli/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '1.2.116'
-__version_tuple__ = version_tuple = (1, 2, 116)
+__version__ = version = '1.2.118'
+__version_tuple__ = version_tuple = (1, 2, 118)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.2.116 → boost_skill_cli-1.2.118}/boost_cli/commands/bmad.py

@@ -11,7 +11,7 @@ and no network: it writes the seven BMAD persona subagents into
 carrying the persona that should lead it, the support personas to spawn
 alongside, the BMAD skill for that track, and a definition of done read off the
 repo in front of it (its test dir, its docs, its roadmap items, its gate
-command). Trivial asks get nothing, so the router costs a question nothing. All
+command). Trivial asks get no banner. All
 of the thinking lives in :mod:`boost_cli.core.bmad`; this module is glue.
 
     boost bmad on                          # <- the one command. global.

{boost_skill_cli-1.2.116 → boost_skill_cli-1.2.118}/boost_cli/core/bmad.py

@@ -79,6 +79,22 @@ class Track(NamedTuple):
     support: tuple[str, ...]   # persona slugs to run alongside the lead
     skill: str                 # canonical BMAD v6 skill for this track
     note: str                  # how the lead should open
+    done: str                  # what finished looks like: one of DONE_KINDS
+
+
+DONE_KINDS: tuple[str, ...] = ("change", "findings", "artifact")
+"""What a track delivers, which decides what "done" means for it.
+
+Every track used to get the build contract — new coverage, updated docs, a
+finished and verified change — so "review the changes on this branch" was told
+to add tests and finish a change, and "compare the two caching options" was
+told to document what changed when nothing had. A *change* ends in edited
+source; *findings* (review, discovery) end in an answer with its evidence; an
+*artifact* (product, planning, architecture) ends in a written document. Neither
+of the last two refuses work the prompt asked for: the tie-break sends
+"implement the spec in specs/retry.md" to *product* on the word "spec", and a
+flat "no code" would tell the model not to do what it was just asked to do.
+"""
 
 
 # --------------------------------------------------------------------- personas
@@ -238,33 +254,33 @@ PERSONA_BY_SLUG: dict[str, Persona] = {p.slug: p for p in PERSONAS}
 TRACKS: dict[str, Track] = {
     "discovery": Track(
         lead="bmad-analyst", support=("bmad-pm",), skill="bmad-deep-recon",
-        note="Ground it in sources before recommending."),
+        note="Ground it in sources before recommending.", done="findings"),
     "product": Track(
         lead="bmad-pm", support=("bmad-analyst", "bmad-architect"),
         skill="bmad-prd",
-        note="Write criteria a test could assert."),
+        note="Write criteria a test could assert.", done="artifact"),
     "planning": Track(
         lead="bmad-pm", support=("bmad-architect",), skill="bmad-sprint-planning",
-        note="Keep the tracked items and the work in sync."),
+        note="Keep the tracked items and the work in sync.", done="artifact"),
     "architecture": Track(
         lead="bmad-architect", support=("bmad-dev",), skill="bmad-architecture",
-        note="One recommendation, with the rejected option named."),
+        note="One recommendation, with the rejected option named.", done="artifact"),
     "ux": Track(
         lead="bmad-ux", support=("bmad-dev",), skill="bmad-ux",
-        note="Hierarchy and spacing before colour."),
+        note="Hierarchy and spacing before colour.", done="change"),
     "build": Track(
         lead="bmad-dev", support=("bmad-tea", "bmad-scribe"), skill="bmad-build",
-        note="Ship it complete and verified."),
+        note="Ship it complete and verified.", done="change"),
     "quality": Track(
         lead="bmad-tea", support=("bmad-dev",),
         skill="bmad-qa-generate-e2e-tests",
-        note="Assertions that a mutation would fail."),
+        note="Assertions that a mutation would fail.", done="change"),
     "docs": Track(
         lead="bmad-scribe", support=("bmad-dev",), skill="bmad-document-project",
-        note="Verify against the code, regenerate what is generated."),
+        note="Verify against the code, regenerate what is generated.", done="change"),
     "review": Track(
         lead="bmad-tea", support=("bmad-architect",), skill="bmad-code-review",
-        note="Find the failure, not the style nit."),
+        note="Find the failure, not the style nit.", done="findings"),
 }
 
 TRACK_ORDER: tuple[str, ...] = (
@@ -680,14 +696,33 @@ def project_signals(root: Path) -> dict:
     }
 
 
-def done_checklist(signals: dict) -> list[str]:
-    """The definition of done, in the repo's own vocabulary.
+def done_checklist(signals: dict, done: str = "change") -> list[str]:
+    """The definition of done for one kind of work, in the repo's own vocabulary.
 
-    Tests and docs are unconditional — "no doc change needed" is a conclusion to
-    reach, not a step to skip. Roadmap and gate clauses appear only when the
-    repo actually has one, because an instruction to update a file that does
-    not exist teaches the agent to ignore the whole banner.
+    For a *change*, tests and docs are unconditional — "no doc change needed"
+    is a conclusion to reach, not a step to skip. Roadmap and gate clauses
+    appear only when the repo actually has one, because an instruction to
+    update a file that does not exist teaches the agent to ignore the whole
+    banner. *Findings* and *artifacts* are not changes, so they get no tests or
+    docs clause: they are done when the answer or the document is. Both carry
+    an "unless asked" escape, because the tie-break routes real change requests
+    onto them — "fix the lint errors in the scanner" goes to review, and
+    "implement the spec in specs/retry.md" to product.
     """
+    guide = signals.get("guide")
+    binding = ["`%s` is binding" % guide] if guide else []
+    if done == "findings":
+        gate = signals.get("gate")
+        return ["findings: each with its evidence (file:line, output or source)",
+                "no edits unless asked; an edit gets tests%s like any change"
+                % (" and `%s`" % gate if gate else ""), *binding]
+    if done == "artifact":
+        roadmap = signals.get("roadmap")
+        tracked = (["roadmap: create or claim the item under `%s`" % roadmap]
+                   if roadmap else [])
+        return ["a written artifact; no code unless the prompt asks for a "
+                "change, which then gets the change contract", *tracked, *binding]
+
     items: list[str] = []
 
     tests = signals.get("tests")
@@ -711,11 +746,7 @@ def done_checklist(signals: dict) -> list[str]:
     if gate:
         items.append("gate: `%s` green, with real output" % gate)
 
-    guide = signals.get("guide")
-    if guide:
-        items.append("`%s` is binding" % guide)
-
-    return items
+    return items + binding
 
 
 # --------------------------------------------------------------------- routing
@@ -756,13 +787,21 @@ def route_lines(prompt: str, root: Path | None = None,
     lines.extend((
         "BMAD skill: `%s` — invoke it if it is installed; otherwise the "
         "persona's own playbook stands." % track.skill,
-        "Done means: " + " · ".join(done_checklist(signals)),
-        "Work autonomously through to a finished, verified change; stop to ask "
-        "only when a choice would change what gets delivered.",
+        "Done means: " + " · ".join(done_checklist(signals, track.done)),
     ))
+    if track.done == "change":
+        # Not "work autonomously": that competed with approval gates people add
+        # on purpose, and the guide clause above only exists when a guide does.
+        lines.append(CHANGE_CLOSE)
     return lines
 
 
+CHANGE_CLOSE = ("Finish the change and verify it; stop only for a choice that "
+                "changes what gets delivered, or an approval step a repo guide "
+                "or a loaded skill requires.")
+"""The closing banner line for a change, and only a change."""
+
+
 def route_context(prompt: str, root: Path | None = None,
                   agents_dirs: tuple[Path, ...] | None = None) -> str:
     """:func:`route_lines` as one string (``""`` when there is nothing to say)."""
@@ -793,16 +832,27 @@ bmad-create-epics-and-stories / bmad-sprint-planning; ship with bmad-build
 bmad-qa-generate-e2e-tests / bmad-retrospective; bmad-help lists the rest.
 Full workflow skills need a per-project `_bmad/` runtime — `boost bmad init`.
 
-House rule: no change is done until its tests, its docs and its tracked item
-are done with it. Turn this off with `boost bmad off`.""" % roster
+House rule: a change is done when its tests, its docs and its tracked item are;
+findings are done when each carries its evidence; an artifact is done when it is
+written down and tracked. Turn this off with `boost bmad off`.""" % roster
 
 
 # ------------------------------------------------------------ persona files
 
 def persona_description(persona: Persona) -> str:
-    """The one-line `description:` Claude reads when choosing a subagent."""
-    return ("%s, %s (BMAD %s). Use PROACTIVELY for %s."
-            % (persona.character, persona.title, persona.module,
+    """The one-line `description:` Claude reads when choosing a subagent.
+
+    Claude Code treats this line as a delegation rule, and its docs recommend
+    "use proactively" to make delegation *more* eager. That wording made the
+    router's silence cosmetic: a prompt the router judged trivial, or marked
+    `no bmad`, got no banner but could still spawn a persona on the strength of
+    its description alone. Tying the trigger to the banner makes the router the
+    one place that decides, while naming the persona by slug keeps delegation
+    working when a banner does name it, or the user does.
+    """
+    return ("%s, %s (BMAD %s). Use when a [BMAD autopilot] routing banner names "
+            "%s, or the user asks for it by name. Covers %s."
+            % (persona.character, persona.title, persona.module, persona.slug,
                persona.triggers))
 
 
@@ -870,11 +920,18 @@ How you work:
 BMAD skills to prefer when they are installed: %s.
 They are not required — when they are absent, the playbook above is the method.
 
-Before you report back, the same contract applies to you as to the session that
-spawned you: tests updated and actually run, documentation left true, any
-tracked roadmap or backlog item moved to match, and the repo's own gate green
-with output you have seen. If you could not finish a part of it, say which part
-and why — do not narrow the task silently.
+Before you report back, meet the contract for the kind of work you were given,
+the same one the session that spawned you works to.
+
+A change: tests updated and actually run, documentation left true, any tracked
+roadmap or backlog item moved to match, and the repo's own gate green with
+output you have seen.
+Findings: each one with its evidence, and no edits unless you were asked.
+An artifact: the written document itself, with any tracked item moved to match —
+no code unless you were asked for a change, which then gets the contract above.
+
+If you could not finish a part of it, say which part and why — do not narrow
+the task silently.
 """ % (persona.slug, json.dumps(persona_description(persona)), persona.color,
        persona.character, persona.title, persona.mission, playbook, skills)
 

{boost_skill_cli-1.2.116 → boost_skill_cli-1.2.118/boost_skill_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.2.116
+Version: 1.2.118
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License-Expression: Apache-2.0

{boost_skill_cli-1.2.116 → boost_skill_cli-1.2.118}/docs/bmad.md

@@ -60,8 +60,8 @@ BMAD skill: `bmad-build` — invoke it if it is installed; otherwise the persona
 Done means: tests: add or update coverage under `tests/`, and run them · docs: update
 `README.md` / `docs/` wherever the change shows · roadmap: create or claim the item under
 `docs/roadmap/items/` · gate: `make check` green, with real output · `CLAUDE.md` is binding
-Work autonomously through to a finished, verified change; stop to ask only when a choice
-would change what gets delivered.
+Finish the change and verify it; stop only for a choice that changes what gets delivered,
+or an approval step a repo guide or a loaded skill requires.
 ```
 
 Nine tracks (`build`, `quality`, `docs`, `planning`, `product`, `architecture`,
@@ -73,7 +73,17 @@ in front of you: your test directory, your docs, your roadmap items, your gate
 command. Documentation, testing and roadmap bookkeeping travel with the task
 instead of being remembered afterwards.
 
-The router costs a question nothing. Acknowledgements, slash commands, short
+What "done" means depends on what the track delivers. `build`, `quality`,
+`docs` and `ux` deliver a **change**, and get the contract above. `review` and
+`discovery` deliver **findings**: each with its evidence, and no edits unless
+the prompt asks for them. `product`, `planning` and `architecture` deliver an
+**artifact**: a written document with the roadmap item kept in step, and no
+code unless the prompt asked for a change. Both escapes matter: the tie-break
+puts real change requests on both kinds.
+Only a change gets the closing "finish and verify" line, and that line defers
+to any approval step your repo guide or a loaded skill requires.
+
+The router leaves questions alone. Acknowledgements, slash commands, short
 questions ("what does `scan_dir` do?", "are there tests for the parser?"),
 "read X and tell me Y" asks and anything containing `no bmad` produce no banner
 at all. Pasted output is scored on the lines you typed around it, and needs two
@@ -90,6 +100,14 @@ scope, so a copy `boost bmad off` could not reach (a committed project
 `.claude/settings.json` in another checkout, a restored settings snapshot) stays
 silent, and a banner never names a persona whose file is gone.
 
+That silence governs the banner, and the personas are written to follow it.
+Claude Code decides delegation from the `description` line of a subagent, so
+each persona says it applies when a routing banner names it, or when you ask for
+it by name; a silent or `no bmad` prompt has nothing pointing at a persona
+except the session briefing's roster. The final call is Claude Code's, not boost's.
+Personas written by earlier releases said "Use PROACTIVELY" instead: run
+`boost bmad on` again to rewrite the ones you have not edited.
+
 ```bash
 boost bmad personas                            # the roster, and whether it's installed
 boost bmad route "add tests for the scanner" --plain   # what would this route to?

{boost_skill_cli-1.2.116 → boost_skill_cli-1.2.118}/docs/roadmap/items/bmad-done-contract-ignores-the-track.md

@@ -2,15 +2,15 @@
 id: bmad-done-contract-ignores-the-track
 board: code
 section: dx
-status: next
+status: shipped
 category: "Agents · BMAD"
 complexity: M
 impact: High
 wow: 2
 note: a review or research ask is told to add tests and finish a change
 order: 321
-owner:
-pr:
+owner: loop/bmad-done-contract
+pr: 864
 title: "<code>boost bmad</code> gives every track the build contract, so a review is told to finish a change"
 ---
 <code>route_lines</code> (<code>core/bmad.py:523</code>) takes the first four banner lines from the track

{boost_skill_cli-1.2.116 → boost_skill_cli-1.2.118}/docs/roadmap/items/bmad-personas-delegate-outside-the-router.md

@@ -2,15 +2,15 @@
 id: bmad-personas-delegate-outside-the-router
 board: code
 section: dx
-status: next
+status: shipped
 category: "Agents · BMAD"
 complexity: S
 impact: Med
 wow: 3
 note: router silence is banner-only, and nobody has counted
 order: 325
-owner:
-pr:
+owner: loop/bmad-persona-triggers
+pr: 865
 title: "Persona descriptions say <code>Use PROACTIVELY</code>, so the router's silence governs only the banner"
 ---
 <code>boost bmad on</code> gives Claude Code two routes to a persona, and only one goes through the router.

{boost_skill_cli-1.2.116 → boost_skill_cli-1.2.118}/docs/roadmap.html

@@ -7588,68 +7588,9 @@ its own pass rather than a bolt-on inside this PR. Left <code>inflight</code> ra
       </article>
 
       <article class="cap rcard" id="bmad-done-contract-ignores-the-track">
-        <div class="head"><span class="pill next">Next</span><span class="cat">Agents · BMAD</span></div>
+        <div class="head"><span class="pill shipped">Shipped</span><span class="cat">Agents · BMAD</span></div>
         <h3><code>boost bmad</code> gives every track the build contract, so a review is told to finish a change</h3>
-        <p><code>route_lines</code> (<code>core/bmad.py:523</code>) takes the first four banner lines from the track
-and the last two ignore it: <code>done_checklist(signals)</code> (<code>:483</code>) has no
-track parameter, and the autonomy sentence (<code>:551</code>) is a literal. One prompt per track against
-one fixture repo gave <b>one distinct pair of closing lines across all 9 tracks</b>:<br>
-<code>Done means: tests: add or update coverage under `tests/`, and run them · docs: update `README.md` / `docs/` wherever the change shows · gate: `make check` green, with real output · `CLAUDE.md` is binding</code><br>
-<code>Work autonomously through to a finished, verified change; stop to ask only when a choice would change what gets delivered.</code>
-
-<b>Repro</b> (throwaway repo with <code>tests/</code>, <code>docs/</code>, <code>README.md</code>,
-<code>CLAUDE.md</code>, and a <code>Makefile</code> with <code>check:</code>).
-<code>boost bmad route "review the changes on this branch and tell me what could break" --plain</code>
-names Murat (<code>bmad-tea</code>) as lead with <code>bmad-code-review</code>, then defines done as new
-coverage, updated docs and a finished, verified change. <code>"compare the two caching options and recommend one"</code>,
-<code>"write the PRD for the policy engine"</code> and <code>"prioritize the backlog for next sprint"</code>
-get the same two lines. In an empty repo the comparison is told <code>tests: cover the change … docs: write down what changed</code>, but nothing changed.
-The shared lines are 48% of the fixture's review banner (326 of 673 chars) and 41% in the empty repo.
-
-<b>Against real prompts the clause seldom fits.</b> Replaying the origin/main classifier over one
-profile's history (417 ordinary prompts over 6 active days, roughly half from tooling repos): 147 (35%)
-would get a banner, or 109 if pasted text is not in the hook's <code>prompt</code> field (not yet
-checked). A <em>single judge</em> (an agent) labelled 41 routed banners, sampled by track: <code>Done means</code>
-fit <b>5 of 41</b> (11 counting partial fits).
-
-<b>The same contract appears in three places, and one was a deliberate choice.</b> The autopilot item
-made tests and docs unconditional (&ldquo;no doc change needed&rdquo; is a conclusion to reach), and
-<code>tests/unit/test_bmad_core.py:331</code> enforces that. It is right for a change and wrong for an
-answer. Every persona file repeats the contract (<code>_persona_text</code>,
-<code>core/bmad.py:663&ndash;667</code>: &ldquo;tests updated and actually run, documentation left true …&rdquo;),
-so the <code>bmad-analyst</code> a discovery banner hands off to brings it back. The SessionStart
-briefing says to follow the banner (<code>:576</code>) and ends on a tests-docs-item house rule
-(<code>:586</code>).
-
-<b>The autonomy line competes with approval gates users add on purpose</b>, such as the
-<code>HARD-GATE</code> in superpowers' <code>brainstorming</code> skill (no implementation until the user
-approves) or a team rule requiring confirmation before a change that affects production. The banner is
-<code>UserPromptSubmit</code> <code>additionalContext</code> (<code>commands/bmad.py:354</code>), added
-again on every routed prompt. <b>Untested:</b> which instruction a model follows when they
-conflict. Softening the line to defer to the repo guide would not cover this: the <code>is binding</code>
-clause only appears when a guide file exists (<code>core/bmad.py:514&ndash;516</code>), and a plugin skill is not a guide file.
-
-<b>Fix: store the kind of done on <code>Track</code></b> (<code>core/bmad.py:75</code>) and pass it to
-<code>done_checklist(signals, done)</code>. <i>change</i> (build, quality, docs, ux): today's clauses,
-unchanged. <i>findings</i> (review, discovery): &ldquo;findings with evidence, no edits unless
-asked&rdquo;. The &ldquo;unless asked&rdquo; matters because the tie-break sends <code>"fix the lint
-errors in the scanner"</code> to review and <code>"investigate why the export crashes and fix it"</code>
-to discovery. <i>artifact</i> (product, planning, architecture): &ldquo;a written artifact, no
-code&rdquo;, keeping the roadmap and guide clauses. Drop the autonomy line from
-findings and artifact tracks. On change tracks, replace it with wording that does not depend on a
-guide file: finish and verify, and still honour any approval step that the guide or a loaded skill
-requires. <code>_persona_text</code> should state the contract for each kind, since
-<code>bmad-tea</code> leads both quality and review. The house rule should name all three kinds.
-
-<b>Tests go in <code>tests/unit/test_bmad_core.py</code>.</b> Assert every <code>TRACKS</code> entry
-declares a kind, and that no findings or artifact banner has a <code>tests:</code> clause.
-Add verbatim review and discovery banners next to <code>test_the_whole_banner_is_exactly_this</code>
-(<code>:396</code>), whose build pin keeps its <code>Done means</code> line and takes the new closing line.
-Limit <code>:331</code> to change tracks. <code>:376</code> pins <code>autonom</code> on one build banner:
-move it to the new wording and assert the line is absent from findings and artifact banners.
-<code>:688</code> only checks that each persona file mentions tests and docs, so pin the per-kind persona
-contract directly. Out of scope: router accuracy (same single judge: track or lead clearly wrong on
-21 of 41) is a separate defect.</p>
+        <p class="cardbody"><a class="writeup" href="https://github.com/jonnyeclectic/boost/blob/main/docs/roadmap/items/bmad-done-contract-ignores-the-track.md">Write-up &middot; bmad-done-contract-ignores-the-track.md</a></p>
         <div class="meta">
           <span class="m">Complexity <b>M</b></span>
           <span class="m hi">Impact <b>High</b></span>
@@ -7805,74 +7746,9 @@ commands carry <code>--host gemini</code> and that <code>--host claude</code> ne
       </article>
 
       <article class="cap rcard" id="bmad-personas-delegate-outside-the-router">
-        <div class="head"><span class="pill next">Next</span><span class="cat">Agents · BMAD</span></div>
+        <div class="head"><span class="pill shipped">Shipped</span><span class="cat">Agents · BMAD</span></div>
         <h3>Persona descriptions say <code>Use PROACTIVELY</code>, so the router's silence governs only the banner</h3>
-        <p><code>boost bmad on</code> gives Claude Code two routes to a persona, and only one goes through the router.
-The banner is gated: <code>classify</code> returns <code>trivial</code> for slash commands and
-<code>no bmad</code> (<code>boost_cli/core/bmad.py:402</code>), short informational questions (<code>:407</code>)
-and thin keyword evidence (<code>:415</code>). The other route is the <code>description:</code> line of the
-seven persona files written into <code>~/.claude/agents/</code> (<code>boost_cli/commands/bmad.py:258</code>),
-which <code>persona_description</code> renders as <code>&lt;Name&gt;, &lt;Title&gt; (BMAD &lt;module&gt;). Use
-PROACTIVELY for &lt;triggers&gt;.</code> (<code>boost_cli/core/bmad.py:594</code>). Neither that line nor the
-persona body (<code>:642</code>) ties spawning to the router; the body's one mention has Amelia read the gate
-command off its banner (<code>:91</code>).
-
-<b>Claude Code reads that line as a delegation rule.</b> The sub-agents docs define <code>description</code>
-as &ldquo;When Claude should delegate to this subagent&rdquo;, name it alongside the request and current
-context as what automatic delegation is based on, and advise: &ldquo;To encourage proactive delegation,
-include phrases like &lsquo;use proactively&rsquo; in your subagent's description field.&rdquo; So the
-router's tuned silence and the <code>no bmad</code> opt-out decide whether a banner is added, not whether a
-persona gets spawned.
-
-<b>The repo's own silent-prompt fixtures read like the triggers.</b> <code>what does scan_dir do?</code>,
-<code>fix the flaky test in test_catalog, no bmad</code> and <code>/code-review fix the failing tests in the
-catalog scanner</code> (<code>tests/unit/test_bmad_core.py:48</code>, <code>:68</code>, <code>:86</code>) all
-classify <code>trivial</code> with a 0-char banner on origin/main, yet Paige covers &ldquo;explaining a system
-to the next person who touches it&rdquo;, Murat &ldquo;flaky suites&rdquo; and Amelia &ldquo;fixing a bug
-&hellip; or any change that ends in edited source files&rdquo; (<code>boost_cli/core/bmad.py:183</code>&ndash;<code>218</code>).
-Replayed over one real Claude Code profile's history (318 unique non-slash prompts up to 2,000 chars, 6 active
-days), <b>60.7%</b> classify trivial and <b>55.7%</b> match no keyword. Little pushes back. The
-<code>SessionStart</code> briefing says &ldquo;Trivial asks get no banner &mdash; answer those directly&rdquo;
-(<code>:576</code>), but also that personas &ldquo;are delegated to with the Agent tool&rdquo; (<code>:570</code>),
-and its hook does not fire on compaction (matcher <code>startup|resume|clear</code>,
-<code>boost_cli/commands/bmad.py:84</code>). A <code>no bmad</code> prompt carries its own words, but nothing
-says they cover the personas.
-
-<b>Unmeasured, and the measurement could close this item.</b> Nobody has counted delegations on silent
-prompts. Banner cost is countable (mean ~650 chars, ~163 tokens on that profile), while a description-triggered
-spawn would be a whole subagent run that no banner count sees. That is inference, but it limits the claim that
-the router &ldquo;costs a question nothing&rdquo; (<code>docs/bmad.md:76</code>,
-<code>boost_cli/commands/bmad.py:14</code>) to the banner. Measure from a HOME with no persona files or boost
-hooks: run each router-trivial prompt (the fixtures plus the trivial slice of a real history) as
-<code>claude -p &lt;prompt&gt; --output-format stream-json --verbose</code> with the briefing via
-<code>--append-system-prompt</code>, in three arms that differ only in the session-only <code>--agents</code>
-flag (no personas, shipped descriptions, fixed descriptions). Count <code>Agent</code> <code>tool_use</code>
-blocks whose <code>subagent_type</code> starts with <code>bmad-</code>, in messages with a null
-<code>parent_tool_use_id</code>. Cost is on the stream's last line. A fourth arm runs routed prompts with the
-real hook via <code>--settings</code>, to check that the fix still delegates when the slug arrives in hook-added
-context rather than typed by the user. If the shipped arm spawns no more <code>bmad-*</code> subagents than the
-no-persona arm, record that here and close the item.
-
-<b>Proposed fix: make the banner the trigger.</b> Drop <code>Use PROACTIVELY</code> and have
-<code>persona_description</code> say when the persona applies, e.g. <code>Amelia, Senior Software Engineer
-(BMAD bmm). Use when a [BMAD autopilot] routing banner names bmad-dev, or the user asks for it by name.
-Covers implementing a feature, fixing a bug, &hellip;</code>. The banner already names lead and support by
-slug, and the docs say that when you name a subagent in your prompt &ldquo;Claude typically delegates&rdquo;.
-Silent prompts would then leave only the briefing's roster pointing at a persona. If the conditional wording
-fails the measurement, fall back to plain scope descriptions with no imperative. Until the fix lands,
-<code>permissions.deny</code> on <code>Agent(bmad-dev)</code> and the rest stops the spawns but blocks
-banner-led delegation too. <code>docs/bmad.md:76</code>&ndash;<code>78</code> should say that the opt-out and
-the silence apply only to the banner. That doc change needs no measurement and can land now.
-
-<b>Tests.</b> Extend <code>tests/unit/test_bmad_core.py</code>.
-<code>TestPersonaFiles.test_the_frontmatter_block_is_exactly_this</code> (<code>:485</code>) pins Sally's
-description byte for byte and must take the new text. <code>test_persona_descriptions_are_delegation_triggers</code>
-(<code>:694</code>) checks only length and that there is no newline. It should also assert that every
-description lacks <code>proactively</code> in any case and contains its persona's slug.
-<code>test_explicit_opt_out_is_honored</code> (<code>:71</code>) proves only that the classifier stays silent,
-and no unit test can observe delegation, so the headless run is the acceptance check. Only re-running
-<code>boost bmad on</code> rewrites unedited persona files (<code>boost_cli/core/bmad.py:672</code>), so the
-release note must tell users to re-run it.</p>
+        <p class="cardbody"><a class="writeup" href="https://github.com/jonnyeclectic/boost/blob/main/docs/roadmap/items/bmad-personas-delegate-outside-the-router.md">Write-up &middot; bmad-personas-delegate-outside-the-router.md</a></p>
         <div class="meta">
           <span class="m">Complexity <b>S</b></span>
           <span class="m">Impact <b>Med</b></span>