boost-skill-cli 1.0.63__tar.gz → 1.0.64__tar.gz

{boost_skill_cli-1.0.63 → boost_skill_cli-1.0.64}/CLAUDE.md

@@ -72,9 +72,33 @@ keep them from clobbering each other:
   never merge onto a red release, and after merging confirm the publish workflow
   goes green — not just the PR checks.
 
+### The roadmap is data-driven — add items, never hand-edit the HTML
+
+`docs/roadmap.html` is **generated** from one file per item under
+`docs/roadmap/items/*.md` by `scripts/build_roadmap.py` (this is what stopped the
+roadmap being the repo's #1 merge-conflict source). To add or change a card:
+
+1. Create/edit `docs/roadmap/items/<id>.md` — a Markdown-with-frontmatter file
+   (`id, board: code, section, status, category, complexity, impact, wow, note,
+   order, owner, pr, title` + the card body after the `---`).
+2. Run `python3 scripts/build_roadmap.py` (or `make generate`) and commit both
+   the item file and the regenerated HTML. Counters ("Loop finds" etc.) are
+   **computed** — never hand-type them.
+
+Never hand-edit the `<article>` cards or snapshot counters in `docs/roadmap.html`:
+CI's `build_roadmap.py --check` and `tests/unit/test_roadmap_fresh.py` fail on
+drift. Two loops adding two items now touch two *different files* → clean merge.
+
+**Claiming an item (so two loops never pick the same one):** set `status:` and
+`owner: loop/<topic>` in that item's file on your branch and open the PR. Two
+loops claiming *different* items edit different files (no conflict); two loops
+claiming the *same* item edit the same small file, so the second merge conflicts —
+the intended "already claimed" signal, first-to-merge wins. (`docs/design-roadmap.html`
+is still hand-edited until the Phase 1b migration lands.)
+
 ## Layout
 
 - `boost_cli/commands/` — CLI command groups   · `boost_cli/core/` — engine (the mutation-gated code)
 - `boost_cli/data/` — shipped catalog data (generated)   · `scripts/` — build/gate tooling
 - `tests/unit`, `tests/functional`, `tests/smoke.sh` — the three test tiers
-- `docs/` — `overview.html` (visual guide), `DEBUGGING.md`
+- `docs/` — `overview.html` (visual guide), `DEBUGGING.md`; `roadmap.html` is generated from `docs/roadmap/items/*.md` (see above)

{boost_skill_cli-1.0.63 → boost_skill_cli-1.0.64}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.63
+Version: 1.0.64
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE
@@ -870,9 +870,13 @@ boost bmad doctor                    # what's installed where
 ```
 
 When startup is on, a `SessionStart` hook runs `boost bmad orient`, which prints
-a short orientation into the session only while the toggle is enabled. Global
-installs stage the installer in a temp dir and copy only the `bmad-*` skills, so
-`$HOME` never gets a stray `_bmad/` — the workflow runtime stays per-project.
+a short orientation into the session only while the toggle is enabled. That
+orientation sets a **default bias**: build/fix/change/refactor requests go
+straight to the `bmad-quick-dev` skill (clarify → plan → implement → review),
+skipping the full brief → PRD → architecture ceremony unless you ask for full
+planning. Global installs stage the installer in a temp dir and copy only the
+`bmad-*` skills, so `$HOME` never gets a stray `_bmad/` — the workflow runtime
+stays per-project.
 
 ## The boost style
 

{boost_skill_cli-1.0.63 → boost_skill_cli-1.0.64}/README.md

@@ -164,9 +164,13 @@ boost bmad doctor                    # what's installed where
 ```
 
 When startup is on, a `SessionStart` hook runs `boost bmad orient`, which prints
-a short orientation into the session only while the toggle is enabled. Global
-installs stage the installer in a temp dir and copy only the `bmad-*` skills, so
-`$HOME` never gets a stray `_bmad/` — the workflow runtime stays per-project.
+a short orientation into the session only while the toggle is enabled. That
+orientation sets a **default bias**: build/fix/change/refactor requests go
+straight to the `bmad-quick-dev` skill (clarify → plan → implement → review),
+skipping the full brief → PRD → architecture ceremony unless you ask for full
+planning. Global installs stage the installer in a temp dir and copy only the
+`bmad-*` skills, so `$HOME` never gets a stray `_bmad/` — the workflow runtime
+stays per-project.
 
 ## The boost style
 

{boost_skill_cli-1.0.63 → boost_skill_cli-1.0.64}/boost_cli/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '1.0.63'
-__version_tuple__ = version_tuple = (1, 0, 63)
+__version__ = version = '1.0.64'
+__version_tuple__ = version_tuple = (1, 0, 64)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.0.63 → boost_skill_cli-1.0.64}/boost_cli/commands/bmad.py

@@ -8,6 +8,7 @@ full provisioning is delegated to the canonical `npx bmad-method install`.
     boost bmad install --scope global      # skills into ~/.claude/skills (+ toggle)
     boost bmad init                        # add _bmad/ runtime to the current repo
     boost bmad startup on|off|status       # toggle the SessionStart orientation
+                                           # (biases build/fix/change work to bmad-quick-dev)
     boost bmad disable / enable            # quarantine / restore skills (recoverable)
     boost bmad uninstall                   # delete skills + _bmad/ for a scope
     boost bmad doctor                      # what's installed where
@@ -56,6 +57,10 @@ Planning (bmad-prd -> bmad-architecture -> bmad-create-epics-and-stories) ->
 Build (bmad-sprint-planning -> bmad-create-story -> bmad-dev-story ->
 bmad-code-review -> bmad-qa-generate-e2e-tests -> bmad-retrospective).
 
+Default bias: for a build, fix, change, or refactor request, go straight to the
+`bmad-quick-dev` skill (clarify -> plan -> implement -> review) — skip the full
+brief -> PRD -> architecture ceremony unless the user asks for full planning.
+
 Full workflows need a per-project `_bmad/` runtime — run `boost bmad init` in a
 repo if it isn't there yet. Turn this orientation off with `boost bmad startup off`."""
 

{boost_skill_cli-1.0.63 → boost_skill_cli-1.0.64}/boost_skill_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.63
+Version: 1.0.64
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE
@@ -870,9 +870,13 @@ boost bmad doctor                    # what's installed where
 ```
 
 When startup is on, a `SessionStart` hook runs `boost bmad orient`, which prints
-a short orientation into the session only while the toggle is enabled. Global
-installs stage the installer in a temp dir and copy only the `bmad-*` skills, so
-`$HOME` never gets a stray `_bmad/` — the workflow runtime stays per-project.
+a short orientation into the session only while the toggle is enabled. That
+orientation sets a **default bias**: build/fix/change/refactor requests go
+straight to the `bmad-quick-dev` skill (clarify → plan → implement → review),
+skipping the full brief → PRD → architecture ceremony unless you ask for full
+planning. Global installs stage the installer in a temp dir and copy only the
+`bmad-*` skills, so `$HOME` never gets a stray `_bmad/` — the workflow runtime
+stays per-project.
 
 ## The boost style
 

{boost_skill_cli-1.0.63 → boost_skill_cli-1.0.64}/tests/functional/test_cli_bmad.py

@@ -110,10 +110,12 @@ class TestOrient:
         # off by default -> silent
         r = boost("bmad", "orient", "--scope", "project")
         assert r.out.strip() == ""
-        # enabled -> prints orientation
+        # enabled -> prints orientation, incl. the quick-dev default bias
         boost("bmad", "startup", "on")
         r = boost("bmad", "orient", "--scope", "project")
         assert "BMAD MODE ACTIVE" in r.out
+        assert "bmad-quick-dev" in r.out
+        assert "Default bias" in r.out
 
 
 class TestDisableEnable: