30 Commits

Author	SHA1	Message	Date
do-operator	87d3407873	feat(docs-site): align the docs with the bmadcode design system, and move diagrams to themed SVG (#2850) ... * feat(website): restyle the docs in the bmadcode design system The docs carried a Ghost-blog theme: Inter and Space Grotesk, a #3b82f6 accent, 12px radii, tinted panels and hover lifts. bmadcode.com is built from the foundry ramp on paper, Archivo and IBM Plex Mono, one accent held under ~2% of the page, 2px corners and hairlines. This aligns the two so the method and its documentation read as one thing. Four type registers, and almost nothing else: Instrument Serif for the page masthead, Archivo 600 for headings, Archivo 400 at 17px for prose, and IBM Plex Mono at 11px for labels — spent once per section, never on prose or a table header. The measure comes down to 46rem so a page reads as an article. Also fixes the site title, which was the only place in the repo spelling the brand "BMAD Method"; it now matches the prose, and every page title and share card with it. The four component overrides are the parts CSS could not reach: the mark in its ink tile, the accent eyebrow naming each section, and the dark footer band. The footer renders from TwoColumnContent rather than the Footer slot because Starlight right-aligns the content column (--sl-content-margin-inline: auto 0), so a band in that column never reached the sidebar edge. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * feat(website): inline hand-authored SVG diagrams Diagrams shipped as rasters: build-diagram.png at 488 KB, plus a -fr and a -ko export of the same picture. Every translation meant re-exporting an image, three of the five locales fell back to the English one, and none of them could follow the site's light and dark themes. Diagrams are now hand-authored SVGs carrying geometry and classes only. A rehype plugin inlines them where a page links to one, so a single stylesheet themes every diagram — an <img> is opaque to page CSS, which is the whole reason for inlining. A second diagram written against the same class vocabulary matches the first without any styling work. Labels are translated rather than redrawn: each <text> carries a data-i18n key and the strings live in <name>.labels.json, so one drawing serves every language and a translation cannot drift out of shape. The integration exists because the inlined SVG lands inside Astro's content layer cache, which is keyed on the markdown file. Editing a diagram left the previous drawing on the page, through a build that reported success. It watches the diagram directory in dev and drops the content store when the drawing changes. Diagram.astro is the same behaviour for anywhere that can take a component. The docs are 193 .md files and no .mdx, where components cannot be imported, so the plugin is the path pages actually use. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs(build): draw the bmad-build run as a themed SVG Replaces build-diagram.png and its -fr and -ko exports with one drawing shared by all five locales: the actors in a left lane, the spine down the middle, a return channel for BAD_SPEC and INTENT_GAP, and the review lenses in a panel — the layout the original had. Gzipped, the diagram goes from 440 KB to 1 KB, and it now follows the theme. The French labels are in place; the other locales fall back to the English text in the SVG, which is what their pages showed before. The raster files stay for now: walk-through-a-change still uses walkthrough-diagram, and that conversion is a separate change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(website): let the diagram cache stamp survive a fresh checkout The stamp is written into Astro's cache directory, which does not exist until Astro creates it partway through the build. On a clean clone — CI, every time — the integration threw in astro:config:done and took the build with it. It now creates the directory, and treats any failure as a warning: a cache that cannot be stamped is a slower build, not a broken one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs(walkthrough): draw the walkthrough run as a themed SVG Replaces walkthrough-diagram.png and its -fr and -ko exports with one drawing shared by all five locales, keeping the original's layout: the two inputs in a left lane, the five stages down the spine, the notes beside them, the early exit skipping the middle, and the three outcomes along the bottom. The outcome chips introduce a `chip` class in the shared stylesheet, taking the green and amber the asides already use, so a green in a diagram is the same green as a tip. Nothing else about this diagram needed styling: it inherits the vocabulary build-run established. With both diagrams converted, website/public/diagrams is empty and the six raster files are gone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs(plan): fold the remaining diagrams into the themed pipeline planning-skills, development-paths and bmad-delivery-loop were already SVG, but outside the pipeline in three ways: they carried their own palettes, they were served as <img> so page CSS could not reach them, and two of them shipped a -ko twin that duplicated the geometry to translate the labels. Two were drawn dark — navy grounds, white text, cyan strokes — so on a light docs page they sat as dark panels. Their palettes are mapped onto the shared tokens, which flips them correctly in both themes, and their backdrops are dropped: a diagram sits on the page's ground rather than painting its own. The hardcoded typefaces go too, so they inherit Archivo and IBM Plex Mono like everything else. The Korean strings are lifted out of the -ko files into the label files, matched by document order, so all five diagrams are now one drawing per diagram. docs/images is empty. Also fixes the cache guard, which was clearing the wrong store: build writes to the cache directory, dev writes to .astro beside the config, and the stamp was shared between them so whichever ran first consumed the invalidation. It is now per command and build-only — deleting the store under a running dev server leaves the content layer unable to render, so dev needs a restart after a diagram edit instead. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(diagrams): align the imported diagrams with the shared vocabulary Mapping the old palettes onto the theme tokens made those three diagrams theme-aware, but not part of the system. They still carried 8-16px corners, painted their own canvas panel or background grid, drew every connector in the accent, and left arrowheads baked to a colour of their own — so next to build-run and walkthrough-run they read as imports. They now use the same roles as the two authored diagrams: .node for boxes, .edge for connectors, .head for arrowheads, 2px corners, and no self-painted ground. Accent drops out of all five: it is for the one thing a drawing points at, which here is a single .node.hot on the destination box rather than a green that read as a status. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore(docs-site): record hast-util-from-html in the lockfile The dependency was declared in package.json during the move to docs-site but its entry never reached the lockfile's root block, so the two disagreed about what the site depends on. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(diagrams): land the arrowheads on their targets in build-run Three arrows pointed at glyphs rather than at boxes, and all three fell short: DEFER stopped 10px from the document and aimed at its corner instead of its body, REJECT stopped 27px from the discard glyph, and the result returning to you stopped 21px from the person. The boxes were fine throughout — every arrow into a node already landed within 2px. What the three had in common is that a glyph sits inside a translated group, so eyeballing them against the drawing's coordinates put the endpoints in the wrong place. Measured across all twenty arrowheads in screen space afterwards: the largest remaining gap is 3px. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(diagrams): move the DEFER label off its own curve, and clear the cache on a dev start too Re-aiming the DEFER arrow at the document glyph swung its curve left, straight through the label that had been sitting clear of the old path. The label moves into the pocket between Present and the curve. Checking it exposed a worse problem: dev was still serving the previous drawing after a restart, so the fix looked like it had not applied. The cache guard had been narrowed to build-only after clearing the store under a live dev server broke rendering — but that failure came from clearing on a mid-session restart, and the watch that caused those is gone. On a cold start, before the content layer loads, clearing is safe in both commands. Confirmed by probe: edit a diagram, restart dev, the edit is served, no errors. So the limitation is now what it was documented to be. Previously an edited diagram needed a full build before dev would show it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(diagrams): give every connector an arrowhead, and clear the boxes Three defects in development-paths, all inherited from the import: Connectors were written as two subpaths in one path element. A marker-end lands on the last vertex of a path, so only the second segment ever drew a head — which is why Change—Edit had none and Edit→Verify did. Four connectors are now separate paths, and all twelve carry a head. The two routed connectors ended exactly on the box they point at, so the arrowhead sat on the border. They stop 4px clear. The epic row was 140/130/130 wide with the labels centred on each box. All three are 140 now, evenly spaced, with the connectors and labels following. Band backgrounds were imported as .node, which made every check treat a connector crossing its own band as an error. They are .band now: same appearance, but the drawing says what it means. Also moves the DEFER label in build-run back alongside its curve. The previous fix pushed it clear of the line and lost the association. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(diagrams): one stroke weight across all five drawings build-run and walkthrough-run carry no inline stroke-width — the stylesheet owns it, at 1.5 for a connector and 1 for a box. The three imported drawings still carried their own: 2, 3, 4 and 2.5, so their lines were twice as heavy as the authored ones. That is also what made the arrowhead into "Build × stories" look wrong. A marker scales with stroke-width by default, so a head defined at 7 units rendered at 21px on a 3px line instead of 10.5px. On a 9px final drop it overshot the corner and sat on the horizontal run above the box. Sixty inline stroke-widths are gone, and the two routed connectors get a longer final drop so the head has room to sit on. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * test(docs-site): cover rehype-inline-diagrams, and fix what it caught Twelve tests alongside the existing plugin suite, against a temporary site root: what gets inlined and what is left alone, label substitution per locale with fallback to the authored English, the accessible name, and the mtime-keyed re-read the dev server depends on. The first run failed on the accessible name, and it was right to. hast camel-cases ARIA attributes, so the guard read `aria-labelledby` and found nothing — meaning every diagram's own <title> was being replaced by the markdown alt text. build-run and walkthrough-run both title themselves with a sentence describing the whole run, and both were announcing a four-word alt instead. Now 119 assertions, and a diagram that names itself keeps its name. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(diagrams): recover the Korean walkthrough labels, and correct the guide Review caught two things. The style guide sent contributors to website/src/diagrams/, the path this branch renamed. A diagram placed there would never be found by the loader or localized. The second is a regression this branch introduced and the PR described wrongly. It claimed the non-English pages "fall back to the English text in the SVG, which is what their pages showed before". That is untrue for four pages: they had localized exports, and replacing those with one drawing plus an English-only label file puts English labels in front of readers who previously had their own language. walkthrough-diagram-ko.svg was an SVG, so its Korean is recoverable and is now the ko-KR label set for walkthrough-run — all 22 keys. The other three were .webp exports, so their text cannot be lifted out: ko-kr build-a-change build-run ko-KR 0/30 keys fr explanation/build build-run fr-FR 13/30 keys fr build/walk-through walkthrough fr-FR 0/22 keys Those need a translator. The 13 French keys are mine and unreviewed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * i18n(diagrams): complete the French and Korean diagram labels Fills the three gaps review found: build-run had no Korean and only 13 of 30 French keys, walkthrough-run had no French. All four sets are now complete. Terms come from the repository rather than fresh coinage. Korean reuses what the -ko diagrams and the Korean pages already established — 의도, 구체화, 계획, 검토, 결과, 사양 — and French follows the vocabulary of docs/fr/explanation/build.md: revue, intention, résultat, implémentation, spécification, and visite guidée from the French walkthrough page. The uppercase edge tokens stay as they are. PATCH, REJECT, BAD_SPEC, INTENT_GAP and DEFER appear in no locale's prose, so they read as protocol constants, the way bmad-build and path:line are already left alone in the Korean set. French runs longer than English and these are fixed-geometry drawings, so both French pages and the Korean one were checked for labels overflowing their box, sitting on a connector, or colliding: none. These are my translations, not a native speaker's. Worth a pass from whoever owns each locale before release. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(docs-site): satisfy the repo's lint and format rules in the new tests The diagram tests used .forEach to walk the hast tree, which this repo's eslint config rejects (unicorn/no-array-for-each), and the file was not Prettier-formatted. CI had been failing on lint since the tests landed. Rewritten as for…of and formatted. Verified against every gate the workflow runs — lint, format:check, test, build — rather than the build alone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs(website): describe the source of the theme without naming a private repo The comments cited the private repository and file paths it was ported from. They point at bmadcode.com instead, which is the public thing a reader can actually check. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(website): keep footer links in the reader's language The footer prefixed only BASE_URL to root-locale paths, so a French or Korean reader following any internal link landed on the English page and lost their language for the rest of the visit. The links now carry the page's locale. Every target exists under every locale — Starlight generates the untranslated ones as fallbacks — so this is safe rather than a trade of one broken link for another: all 36 routes, 6 links across 6 locales, resolve in the built site. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>	2026-09-09 01:26:54 -04:00
Alex Verkhovsky	fa1637ee40	build: move the Node toolchain into docs-site (#2834) ... The root package.json, lockfile, .nvmrc, prettier ignore file and .npmignore are gone. docs-site has its own package.json and lockfile with the Astro, ESLint and Prettier dependencies, and its scripts run relative to that directory. tools/quality.py, both workflows and the docs all call npm inside docs-site. stamp_release.py stamps only the 29 skill manifests now; the version lives nowhere else on this branch. The tests for package stamping go with it.	2026-09-05 18:11:37 -06:00
Brian	3aa110dfd3	fix(customization): resolve the project root from the working directory (#2802) ... * fix(customization): resolve the project root from the working directory resolve_customization.py inferred the project root by walking up from the skill's installed directory. For a skill installed under the user's home, that walk reaches ~ — and when a user-level install has put a ~/_bmad there, the resolver treats home as the project, finds no override, and returns shipped defaults. The real project's _bmad/custom/ file is never opened, with no error and no warning. Whether an override takes effect therefore depended on where its skill happened to be installed, which the override's author cannot see from the override. Every harness installs global skills under ~/<tool>/skills, so this hits all of them identically. Resolve from an ordered candidate list instead: the working directory first (the project is where the user works, not where the skill lives), then the script's own install path (skills invoke it as {project-root}/_bmad/scripts/..., so its grandparent is a root the caller already resolved), then the skill directory as a last resort. Rank _bmad/ above .git at every depth while walking. A submodule or nested repo carries .git without being the BMad project, so treating the two as equal stopped the walk short of the root owning _bmad/custom/ — the same silent failure, reachable by project-installed skills too. Break the silence: when the chosen root has no override for the skill but a rejected candidate does, write a note to stderr naming both roots. stdout stays pure JSON. Pass --project-root from all 44 skill and doc invocation sites, matching resolve_config.py, which already requires it. That asymmetry was the root cause; with the flag passed there is nothing left to infer. Fixes #2796 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L8Hyqmp2giAVgEAnB49zEQ * fix(customization): pass --project-root from the party and forge wrappers resolve_party.py and resolve_personas.py shell out to the customization resolver with --skill only, though both already hold the project root and both pass it to resolve_config.py two functions earlier. The resolver therefore had to infer a root, and since these wrappers capture stderr and discard it, the note about a masked override went nowhere. Under the old skill-directory-first inference this happened to land on the right root for a project-installed skill; under working-directory -first it takes the ambient root instead, which is wrong whenever the party runs from a nested project or an unrelated worktree. Passing the flag removes the inference for both paths rather than trading one wrong guess for another. Cover each wrapper with a test that captures the resolver command and asserts the flag carries the project root it was given. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01L8Hyqmp2giAVgEAnB49zEQ --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-30 23:01:32 -05:00
Alex Verkhovsky	6b83751711	chore(docs): drop llms.txt generation and site banners (#2785) ... Stop generating llms.txt and llms-full.txt, remove the header banners, and point help/docs at the live site.	2026-08-28 01:40:10 -06:00
Brian	d2b87b849b	Rename bmad-checkpoint-preview to bmad-walkthrough (#2783) ... * Rename bmad-checkpoint-preview to bmad-walkthrough "Checkpoint" said nothing about what the skill does and "preview" was wrong: it is a guided human walkthrough of a change, not a preview. Its siblings bmad-code-review and bmad-review already own "review", so the new name leans on what sets this one apart. "Walk me through this change" was already its trigger phrase. - Skill folder, SKILL.md name/description, module-help.csv (menu code CK -> WT), marketplace.json - Trigger words are now "walkthrough", "walk me through this change", "human review"; "checkpoint" is dropped - English how-to page moves to docs/build/walk-through-a-change.md; build-a-change link updated - fr, vi-vn, zh-cn pages move to docs/<lang>/build/walk-through-a-change.md to mirror the English path; explanation sidebar orders renumbered to close the gap - Redirects for the old English and localized routes; sidebar label and translations updated - Diagram assets renamed (image contents unchanged) * Regenerate walkthrough diagrams with the new title Title reads Walkthrough and the input box reads bmad-build spec file (was quick-dev, stale since the Build rename). English and French, same layout and style as before. * Add bmad-checkpoint-preview forwarding shim Forwards to bmad-walkthrough and offers to migrate legacy _bmad/custom/bmad-checkpoint-preview{,.user}.toml files, same as the other v6 shims. * Point test-completed-work links at the renamed walkthrough page	2026-08-27 22:03:36 -05:00
Brian	eab4883caa	docs: remove roadmap page and links, tidy README footers (#2774)	2026-08-25 17:07:24 -05:00
Brian	568365e7ff	chore: default persistent_facts to an empty array (#2750) ... * chore: default persistent_facts to an empty array Every customize.toml shipped with a skill seeded persistent_facts with file:{project-root}/**/project-context.md. That made project-context an opt-out default rather than an opt-in customization. Ship the arrays empty so nothing is loaded unless the user adds it. * docs: correct the persistent_facts default in comments and docs Comments and docs still described project-context.md as loading by default. They were wrong twice over: the array now ships empty, and bmad-project-context no longer produces a project-context.md at all — it writes a verified block into AGENTS.md and treats project-context.md as a legacy artifact. Replace those claims with the actual model: repo-wide context belongs in AGENTS.md, which every skill already sees; persistent_facts carries context only one skill needs, loaded on demand instead of as constant memory. Each site shows the file: entry users can add to opt back in.	2026-08-16 10:37:41 -05:00
Alex Verkhovsky	2f8b437ea2	docs(review): remove the adversarial-review explanation page (#2679) ... The page is no longer needed. Drop it and its localized copies (cs, fr, vi-vn, zh-cn), and de-link the remaining references in forge-idea.md and the zh-cn advanced-elicitation/build pages. Drop a stale line from lens-adversarial.md left over from the prompt slim. Also drop a renderer test assertion that could never fail: it checked that a deleted file wasn't in the snapshot, but the file no longer exists anywhere in src/, so nothing could put it there.	2026-08-03 03:20:29 -07:00
Alex Verkhovsky	cff69a6d54	refactor(review): slim adversarial hunter prompt (#2675) ... * refactor(review): slim adversarial hunter prompt across build and review skills Drop cynical-persona framing. Inline a short review prompt (≥10 findings, look for missing, empty/zero guards) into blind-hunter layer instructions for bmad-build, bmad-build-auto, and bmad-code-review. Delete the old review-prompts/adversarial.md files. Align offline no-subagent dump with the same child prompt. Update bmad-review's adversarial lens to the same method while keeping its canonical finding fields. * test(renderer): stop requiring deleted adversarial.md prompt file Blind hunter is inlined; assert the inlined prompt text and remaining file-backed review prompts instead. * docs: align adversarial review explanation with slim hunter prompt Document the finding floor and missing-not-only-wrong method instead of the old cynical persona. Update core-tools lens table and localized pages.	2026-08-02 19:43:11 -07:00
Alex Verkhovsky	d25a307e71	docs: remove non-interactive installation pages (#2670)	2026-08-02 04:40:38 -07:00
Brian	cf54f4d76d	refactor(bmm): consolidate sprint skills — one owner for the sprint-status artifact (#2659) ... * refactor(bmm): move sprint-planning and sprint-status to plan/ They sit at the plan/ship boundary and their outputs are planning artifacts of the dev cycle; next commit makes sprint-planning the readiness gate, which is plan-side work. * refactor(bmm): fold readiness gate into sprint-planning, retire check-implementation-readiness The old skill was 1,154 lines of legacy numbered-step ceremony whose document discovery hardcoded filename globs (*prd*, *ux*, *epic*) that miss what current skills produce (SPEC.md, DESIGN.md) and still treated retired sharded docs as first-class. Sprint-planning now opens with a lean readiness gate: generic artifact discovery by content, forward/back traceability, PASS/CONCERNS/FAIL, stop on FAIL with findings. The IR trigger on John's and Winston's menus dispatches sprint-planning, so 'check implementation readiness' still works everywhere it used to. * refactor(bmm): modernize sprint-planning with deterministic script core SKILL.md drops the legacy XML step dialect for the product-brief style (~100 lines, uv run, headless contract). New scripts/sprint_plan.py owns the mechanical work — epic parsing, key derivation, ordering, preserve- never-downgrade merge, story-file detection, action_items carry-over, atomic writes, drift checks — with 11 tests wired in as test:sprint-planning. Judgment stays with the LLM: epic discovery, the readiness gate, and reconciling script-reported orphans and unparsed headings. checklist.md retired (the script performs that checklist); sprint-status-template.yaml is the single source for the status vocabulary. Output stays byte-compatible with build's sprint sync and retrospective's tooling. * refactor(bmm): fold sprint-status into sprint-planning's status view sprint_plan.py gains a status subcommand: counts (legacy values mapped), risk flags, open action items, and a priority-ordered next-action recommendation — the old skill's inference-driven summary, computed deterministically and covered by 9 new tests. bmad-sprint-status becomes a v6-shims husk that forwards with status-view intent and a deprecation notice; its dead data/validate modes had zero callers and are gone. If a hand-edited status file defeats the script, the skill falls back to reading it directly and summarizing by best judgment. New explanation page docs/explanation/sprint-planning.md covers the consolidated skill; workflow maps and references updated across all languages. * docs: changelog entries for skill reorg and sprint consolidation * fix(bmm): harden sprint_plan.py per review; add validate/fix intents with full progressive disclosure Review fixes (PR #2659 findings, bot + internal review): - Normalize legacy v6 statuses (drafted/contexted) on every read — merged by meaning and reported, never treated as illegal or reset - dropped_orphans carry their old status; transplant renames via --set - project_key/tracking_system/story_location preserved from the existing file unless overridden; refresh round-trips custom keys and user comments - Hardened write path: dump-to-bytes, fsync, permission-preserving atomic write inside the guarded block, explicit checks (no asserts), atomic restore - JSON-only argparse (errors and -h emit JSON); unicode-aware slugs with hash fallback; fenced code blocks ignored when parsing epics - Odd retro keys, date-typed stamps, and non-mapping YAML report cleanly instead of crashing; unparseable timestamps warn instead of silently disabling the staleness check; malformed action items flagged, not dropped - Dead check subcommand removed; generate --dry-run reports drift/in_sync - test:sprint-planning wired into quality and CI (was test-only) - Retro tests use a vendored template fixture (PATH-05); repo-level test-template-sync.js keeps it byte-identical to the source; template example timestamps and story_location fixed; header block pinned to the template by test New capability: - validate subcommand + reference: structural validation, never writes - fix flow: evidence-gathering subagents -> user-confirmed state table -> generate --fresh --set writes a pristine file (the one path allowed to downgrade); universal script-failure fallback to inference for every intent - SKILL.md is now a lean router: gate, tracking, status, fix, and validate each load as progressive-disclosure references Docs: explanation page gains Repair section; workflow-map and getting-started across all five languages mention the status view; headless payload nests under 'report' to avoid the status key collision; changelog updated. Test suite grows 20 -> 37; retro suite 91/91; docs build and validators green. * docs: mention repair in sprint-planning explanation description	2026-08-01 16:21:38 -05:00
Brian	57ad793167	refactor(bmm): reorganize skills into agents / plan / ship; retire tech-writer agent (#2658) ... * refactor(bmm): move agent skills into agents/ * refactor(bmm): collapse phase folders into planning/ and shipping/ Skills reorganize from numbered pipeline folders (1-analysis, 2-plan-workflows, 3-solutioning, 4-implementation) into two sets: planning/ and shipping/. Path and phase-label references updated across marketplace.json, module-help.csv, tests, and bmad-help; also trues up two marketplace paths that were stale on main (create-story/dev-story already lived in v6-shims). * refactor(bmm): shorten skill folders to plan/ and ship/ * refactor(bmm): retire tech-writer agent (Paige on hiatus) Paige's capabilities were generic LLM defaults with no domain substance; her one real menu item (DP) dispatches bmad-document-project, which stays directly invocable and remains on the Analyst menu. Added to removals.txt so installs clean up, and docs (all languages) carry a hiatus notice — she returns in the future far more capable.	2026-08-01 01:52:51 -05:00
Alex Verkhovsky	022bcbc66d	Rename Quick Dev to Build (#2651) ... * feat(bmm): rename quick dev to build * fix: address build rename review findings * fix: clarify deprecated build shims * fix: offer legacy customization migration	2026-07-29 19:40:05 -07:00
Alex Verkhovsky	1a8fea5bd0	fix(docs): resolve deployed validation findings (#2644)	2026-07-29 01:26:46 -07:00
Alex Verkhovsky	029ba287bc	docs: make Quick Dev the canonical implementation workflow (#2643) ... Rewrite published documentation and maintained translations around variable planning depth with one Phase 4 implementation loop. Update diagrams and AI indexes, and reject obsolete workflow terminology in deployable output.	2026-07-28 22:30:22 -07:00
Brian	bb45db4aa4	feat(core): consolidate research trio into bmad-deep-recon (#2611) ... * feat(bmm): consolidate research trio into bmad-deep-recon Replace bmad-market-research, bmad-domain-research, and bmad-technical-research (5,136 lines of near-duplicate legacy step files) with one modern skill, bmad-deep-recon (~650 lines): - Research-master-orchestrator persona; conclusions never rest on training data alone; lead-following rounds with coverage/novelty-exhaustion stops - Six type packs as ~25-line policy+craft cards (market, domain, technical, competitive, user-voice, academic-lit) + select decision shape layering a weighted-matrix method over any type - Three acquisition modes: Generate (subagent fan-out), Delegate (engine registry: CLI/MCP, engine-first strategy), Import (provenance-tracked) - Claims-ledger verification (normal/high/max) with independence rules and optional red-team pass; cited synthesis with staleness map - Effort presets (quick/standard/deep) over four knobs (subagents, sources/round, depth, validation); precedence request > knob > preset - Plan gate with surface discovery (MCPs/CLIs/engines), routing table, and time estimate; use_workflows and subagent_models config - Create/Refresh/Deepen intents, memlog run-folder workspace, headless JSON - v6 shims forward the three old IDs with type pre-set; analyst menu, catalog, marketplace, docs and translation mirrors updated * feat(bmm): runtime output_format for bmad-deep-recon (v7 artifact protocol) Replace the output_formats array with output_format = auto|html|md|both (default auto): interactive runs render the HTML briefing, headless or skill-invoked runs present the canonical markdown only. research.md always exists in the workspace as the machine-readable report; the briefing is its regenerable face. First instance of the v7 artifact protocol (memlog = truth, md = distillation under contract, html = face). * feat(core): move bmad-deep-recon to core-skills; address review findings Move: research is not code-project-specific — home it in core-skills (brainstorming precedent) so CIS and core-only installs get it. Skill ID unchanged; standalone marketplace plugin added; catalogs moved to Core; {planning_artifacts} falls back to {output_folder} on core-only installs. v6 shims stay in bmm-skills (the legacy trio were bmm skills). Review fixes (CodeRabbit): - Engine briefs are now file-based: invoke templates substitute {brief_file} (a skill-generated path), never inline brief text — quotes and shell metacharacters in researched content can't shape a command. - Refresh/Deepen preserve verification statuses for out-of-scope claims. - HTML briefing: http(s)-only source links, escape source-derived text. - user-voice pack: redact usernames/handles/emails from verbatim quotes; communities complement surveys (triangulate) rather than beat them. - engine.md: explicit single-writer rule — digests return to the lead, which alone writes research.md in plan order. * feat(core): deep-recon v2 — draft/process/run, faster defaults, research firewall Rework after first real-run feedback (slow, token-heavy, locally biased report, end-pass verification degraded quality, digests stranded in subagent contexts): - Three modes replace the acquisition-mode machinery: Draft (build a deep-research prompt the user runs in their own subscribed tool), Process (file a finished report into imports/, extract to digests/, distill research.md summary + metadata so downstream never reprocesses), Run (native fan-out, first-class). Bare research asks get the choice up front with the trade stated honestly. - Engine/Delegate registry cut: the Draft->Process round-trip is the integration with dedicated deep-research tools; engine.md -> run.md. - Files-first: digests hit {doc_workspace}/digests/ on landing, sections commit per dimension, synthesis reads files never conversation memory, dead runs resume from disk. - Research firewall: persistent_facts default now empty, assistants get only their brief, project context frames questions but is inadmissible as evidence. - Verification at landing, not end-of-run: normal = spot-check load-bearing claims only; red_team default off; heavy passes behind high/max. Presets rescaled faster (standard 3 subagents/8 sources/ depth 2). - Multi-agent research lessons folded into run.md and the plan gate: decomposition topology (breadth/depth/straightforward), per-assistant tool-call budgets, query craft with OODA pause, shared source-quality card, stop-and-write valve, mechanical citation check at finalize. - Ripple: v6 shims, catalogs, marketplace, docs one-liners (all five languages), template gains source: provenance field. * feat(core): deep-recon quality pass — carve SKILL.md, recon_kit scripts, single-source verification - SKILL.md 3989→2091 tokens: Draft/Process/Refresh+Deepen/Finalize carved to references/{draft,process,lifecycle,finalize}.md; Run effort knobs + plan gate moved into run.md; Overview and pack prose trimmed - verification.md: red-team pass is the single adversarial mechanism (max runs it at full breadth — no double-spawn); level semantics single-sourced - scripts/recon_kit.py + tests: citations cross-check, memlog claim tally (ref=/status= convention, last wins), staleness date math from per-class windows, deterministic run-folder slugs, escaped source-appendix HTML - Draft wired with preferred/banned source policies and an open-floor opening - external_sources examples (Tavily/Sonar/xAI X-Search MCPs); source-quality card: answer engines are aggregators — chase their citations * docs: Deep Recon explanation page + integration - new docs/explanation/deep-recon.md: three modes, mode-choice guidance, research types, native-run internals diagram, firewall/verification, refresh - analysis-phase.md research section rewritten for bmad-deep-recon - core-tools.md: deep-recon in thinking-skills table, full catalog entry, migration note for the merged market/domain/technical trio - workflow-map.md + getting-started.md link the new page - vi-vn developer guide: last stale old-skill flow mention updated	2026-07-22 21:49:24 -05:00
Brian	8b4da79161	refactor(core): group v6 shims and merge editorial review into bmad-review as lenses (#2608) ... * refactor: group v6 deprecation shims into v6-shims folders Move the nine backward-compatibility forwarders into dedicated v6-shims/ folders so the deprecation set is visible in one place and can later be made an install-time include/exclude option before removal at the v7 cut. core-skills/v6-shims/: the five review and editorial husks bmm-skills/v6-shims/: the four PRD and architecture husks Grouping only — no content changes. The installer discovers skills by a recursive walk and installs each under its own name, so installed paths and skill IDs are unchanged. Verified by diffing a full headless install against main: identical .claude/skills listing and file content, and an identical _bmad tree. The only delta is the path column in skill-manifest.csv, which now records the new source location. External module repos (gds, loop, tea, bmb, os-utils) and enterprise users still invoke these IDs, so they continue to ship by default. * refactor(core): merge editorial review into bmad-review as lenses All reviews are reviews. bmad-editorial-review's two passes become two more bmad-review lenses, leaving one lens runtime instead of two skills with overlapping trigger descriptions — "review this document" matched both before, so which one ran was close to arbitrary. Lenses now declare what they apply to. applies_to is "code", "docs", or "any", and is the first filter on a default review; `when` still refines it in prose. adversarial stays "any" — it is a stance, not a subject- matter method, and is the lens a code/doc skill split could not have placed. edge-case-hunter's `when` was "always", which is why it would have fired on prose; it now gates on having a behavioral surface. A lens may also declare `after`, naming a lens it builds on: prose runs on top of the structure findings, as it always has. The runner announces the plan, runs the independent lenses (in parallel via subagents when available), then the dependent ones on their results. Lens wording is unchanged. The three code lens files are byte-identical; the editorial passes moved verbatim into references/lens-structure.md, references/lens-prose.md, and references/editorial-common.md, which carries what both share — the content-sacrosanct rule, style guide handling, reader calibration, and the findings table. That material used to load unconditionally; as lenses it loads just-in-time, so a code review no longer pays for it. bmad-editorial-review becomes the sixth v6 shim, forwarding with the structure and prose lenses named. It keeps its customize.toml so existing team and user overrides still resolve, and forwards them as pre-resolved values. The four other husks now name bmad-review and their lens explicitly. Each still pins its own legacy output contract. bmm's four document skills point doc_standards at the merged skill with named lenses. Docs updated across all five locales. Core is 7 skills. A headless install produces the same 47-skill set as main, with all six shims resolving. * fix(core): honor forwarded customization and de-hardcode the lens set Follow-up to the editorial/review merge, from review of #2608. Contract fixes: - bmad-review gains a Forwarded activation clause matching bmad-prd and bmad-architecture, so the bmad-editorial-review shim's pre-resolved fields are honored instead of being silently overwritten by the skill's own customize.toml. Existing bmad-editorial-review overrides resolve again. - The announce step is skipped when a caller pinned an exact output contract, and a forwarder's contract now governs everything emitted rather than the findings block alone. The edge-case (raw JSON) and verification-gap (one exact line) forwarders no longer get a prose line prepended. Lens set is no longer hardcoded: - The description and body intro present the shipped lenses as examples and point at whatever {workflow.lenses} resolves to. Docs carry a matching note in all five locales. Also: - Document the `lenses=` directive form in Inputs and in the four bmm doc_standards comments that use it. - module-help.csv review row rewritten to the house "Use to..." convention, naming the reviewable content types and the situations that should trigger a suggestion. - Shim customize.toml trimmed to a lean legacy-key surface with empty defaults, so unset keys fall through to bmad-review and project-context.md is no longer loaded twice. - Redundant `when` clauses dropped where applies_to already encodes the rule. - Core skill count corrected to seven/four and the edge-case applies_to cell fixed to match its actual value, across all five locales.	2026-07-19 18:40:47 -05:00
Brian	c23f23400d	feat: streamline core to an 8-skill set with merged review and editorial skills (#2603) ... * feat: streamline core to a 5-skill kernel with standalone skill modules Core installs 14 -> 5 catalog-visible skills; atoms exit to standalone modules; installer gains real dependency resolution; zero npm deps. - Merge bmad-editorial-review-prose/-structure into bmad-editorial-review (structure models JIT-loaded, new customize.toml) - Merge bmad-review-adversarial-general/-edge-case-hunter/-verification-gap into bmad-review as selectable lenses; hidden husk-forwarders remain at the old IDs (no catalog rows) so gds/loop/os-utils keep working - Move bmad-brainstorming, bmad-party-mode, bmad-forge-idea out of core to src/standalone-skills/ as single-skill modules; add bmad-analysis bundle module (curated dependency list over the atoms) - Move bmad-spec into bmm (2-plan-workflows) - Modernize bmad-advanced-elicitation: uv run, customize.toml, methods pick offloaded to scripts/pick_methods.py (with tests) - Delete bmad-index-docs, bmad-shard-doc (removes the tree's only external npm dependency), and the four deprecation shims (bmad-create-prd, bmad-edit-prd, bmad-validate-prd, bmad-create-architecture); all added to removals.txt - Installer: activate the dependencies field (recursive union into selectedModules, cycle-guarded, warn on unknown), config-driven picker visibility; core stays force-installed - bmm module.yaml declares deps on the three atoms - Docs updated across all locales; new reference/standalone-skills.md; shard-doc how-tos removed * Restore original critical wording lost in the review/editorial merges The merges into bmad-review and bmad-editorial-review were meant to keep the source skills' critical wording behind progressive disclosure, not paraphrase it away. Restore what was lost: - lens-adversarial: clueless-weasel framing, extreme-skepticism wording, the at-least-ten-issues quota, and zero-findings-is-suspicious (the merge had inverted this to zero-is-valid) - bmad-review SKILL: zero-findings stance is now per-lens - lens-edge-case: mandatory exact-order step enforcement - lens-verification-gap: exact 'No verification gaps found.' clean line - editorial-review: full Human/LLM reader principles restored to new references/reader-principles.md; structure-pass HIGH-VALUE DENSITY role, front-load-value, anti-patterns, pacing check, and length_target assessment; prose-pass role sentence, analyze-style-first step, and merge-overlapping-fixes rule; output summary block and min-3-words HALT * feat(installer): promote bmad-analysis bundle to src/bmad-analysis-skills Move the bmad-analysis bundle module out of src/standalone-skills/ into its own src/bmad-analysis-skills root, teach the installer to resolve it there (getModulePath, official-modules listing, isBuiltInModule helper), and update the marketplace manifest and standalone-skills docs to match. * refactor(bmad-review): rename edge-case lens to edge-case-hunter Rename the lens code and reference file (lens-edge-case.md -> lens-edge-case-hunter.md), add explicit when = "always" to the shipped lenses, and tighten the lens-selection wording in SKILL.md. * feat(bmad-editorial-review): configurable style guide + analysis-driven rework Apply the workflow-builder analysis recommendations: - Make the baseline style guide configurable: style_guide in customize.toml now IS the baseline (default "Microsoft Writing Style Guide") instead of an empty override slot; SKILL.md no longer hardcodes the guide. - Inline reader-principles.md into SKILL.md and delete the reference (it loaded on every run and was half-duplicated inline). - Complete the customization surface: activation_steps_prepend/append, persistent_facts (project-context glob), on_complete, and a review_output_path scalar split out of output_preferences; add a file:-load fallback convention. - Ground word metrics: new scripts/word_metrics.py (stdlib, PEP 723, tests) emits total/per-section word counts so impact estimates and the reduction summary use exact numbers. - Cross-pass dedup: prose pass skips CUT-tagged passages and re-attaches fixes in MERGE'd ones; output ranks by impact with a long-tail rollup. - Polish: HALT threshold replaced with plain outcome, duplicate LLM-reader bullets merged, all-caps lowered, literal Overview heading added. * fix(installer): stop cache-refresh git commands from escaping to the parent repo Two compounding bugs let a pre-commit test run shallow-fetch and hard-reset the developer's own repository: 1. Git spawns in custom-module-manager and external-manager inherited the hook environment. Git exports GIT_DIR (absolute, in worktree checkouts) into pre-commit hooks; a child git then targets the hook's repo regardless of cwd, and treats its cwd — the module cache dir — as the work tree. The cache refresh's 'git fetch --depth 1' + 'git reset --hard origin/main' therefore shallowed the shared .bare and moved the checked-out branch. New git-env.js strips repo-targeting GIT_* vars from every git spawn in both managers, including calls that previously inherited process.env implicitly. 2. Test suite 51 (quickUpdate dependency expansion) ran the real CustomModuleManager lookup, which scans ~/.bmad/cache/custom-modules and network-refreshes every cached clone — real user state. The suite now stubs findModuleSourceByCode. Verified by rerunning the suite with GIT_DIR pointed at the repo and a PATH shim blocking fetch/reset/clone: 432 passing, zero blocked calls. * De-scope standalone-skills mechanism: atoms return to core, shims reinstated Shrink the PR to its heart — the skill merges — and defer the module mechanics to a follow-up where all skills become module-driven: - bmad-brainstorming, bmad-party-mode, bmad-forge-idea move back to src/core-skills/ as ordinary core skills with their catalog rows restored; src/standalone-skills/ and the bmad-analysis bundle module are removed - Installer reverted to main: standalone discovery, hidden-module filtering, dependency resolution, manifest changes (test suites 49-51 removed with the code); the cache-refresh git fix is retained - The four bmm deprecation shims (create/edit/validate-prd, create-architecture) are reinstated so enterprise installs that invoke the old IDs or carry _bmad/custom overrides keep working; descriptions trimmed to the short husk style; their removals.txt entries dropped (removal rides the v7 cut as their frontmatter promises) - marketplace.json keeps the five plugin entries with atom paths pointing at src/core-skills/ - Docs (en/cs/fr/vi/zh) reframe the three skills as core thinking skills; standalone-skills.md reference page removed * Fix all findings from the max-effort adversarial review Correctness: - Finish the edge-case -> edge-case-hunter lens rename at every caller: the forwarder husk, the code-review/dev-auto/quick-dev review layers, the renderer test assertion, and the stale example path in bmad-review/SKILL.md - marketplace.json: ship the five core kernel skills with bmad-method-lifecycle so its skills' bmad-review/bmad-editorial-review/ bmad-help/bmad-advanced-elicitation invocations resolve in a marketplace install - pick_methods.py / word_metrics.py: force UTF-8 stdout (Windows locale code pages crashed on the catalog's arrows and CJK headings) - word_metrics.py: pair fences CommonMark-style so 4-backtick fences can embed 3-backtick examples without corrupting sections; count CJK characters as words - pick_methods.py: validate --extra entries are JSON objects (was an uncaught AttributeError); read catalogs with utf-8-sig (BOM'd CSVs silently blanked every num) - bmad-spec: activation now resolves {output_folder} (which the Workspace uses) instead of the unused {planning_artifacts}; drop the stale core-only-installs comment - Editorial husks: pin the legacy output contracts (three-column table / Document Summary report and exact empty-state lines) like the review husks do - PRD shims: advertise the real bmad-prd customize keys (validation_checklist_template, prd_output_path, run_folder_pattern, finalize_reviewers) instead of three that don't exist - bmad-prd: add the forwarded-activation clause its shims rely on (ported from bmad-architecture) - Locale workflow-maps (fr/cs/vi/zh): add the bmad-spec Phase-2 row the English map gained, which every locale's core-tools note points at - git-env.js: also strip GIT_CONFIG_PARAMETERS and the GIT_CONFIG_COUNT/KEY_n/VALUE_n family; pass gitEnv() to the three npm install spawns whose transitive git calls inherited hook vars Consistency: - brain.py --extra overlay now replaces-by-name like pick_methods.py (same customize.toml additional_* semantics across sibling skills), with a regression test * Fix prettier formatting in marketplace.json * Apply valid CodeRabbit findings - brain.py: catch malformed --extra overlays (bad JSON, non-array root, non-object entries) into the clean error path instead of a raw traceback, with a regression test; read catalogs and overlays with utf-8-sig; normalize ALL CSV fields (required ones were unstripped and could arrive as None from short rows) - brain-selector: clamp the random-technique count to what the pool can supply so the Total badge matches the actual draw (template + regenerated assets/brain-selector.html) - bmad-editorial-review: word_metrics command now uses the explicit {skill-root}/ prefix - resolve_party.py / resolve_personas.py: custom member overrides now start from the installed entry, so omitted fields (icon, title, description, module, team) survive; non-string member tokens land in unresolved instead of raising TypeError; party's member loop gains the isinstance guards its personas twin already had - bmad-brainstorming: fix the SKILL.md claim that headless is the only context for self-generated ideas (autonomous mode is interactive); autonomous mode honors user-supplied techniques before self-selecting - Docs: drop duplicate 'only' in the spec template; align zh-cn forge-idea's bmad-review description with the English wording * Create only the output folder at install time bmm no longer pre-creates planning_artifacts, implementation_artifacts, and project_knowledge — the last of which put an empty docs/ at every project root. Skills create those lazily on first write. core now declares {output_folder} in its directories block, which was previously created only as a side effect of the artifact folders nesting under it.	2026-07-18 23:49:22 -05:00
Brian	02739932bc	feat(installer): check for uv and standardize messaging on uv run (#2495) ... Replace the standalone python3 environment check with a uv check, since uv is becoming the de facto standard for running BMad's Python scripts (`uv run <script>`) and uv provisions the interpreter itself. Installer: - Remove tools/installer/core/python-check.js and its wiring in ui.js - Add tools/installer/core/uv-check.js: warn-don't-block, no ack prompt (the migration is in progress, so a missing uv never blocks install). Missing uv warns and points the user at setup, preferring "ask your agent to set up uv" - Add a uv heads-up to the install intro (install-messages.yaml) and a uv tip line to the final "BMAD is ready" summary box - Swap test Suite 46 from python-check to uv-check coverage Docs and script comments (no functional skill invocations changed): - resolve_config.py / resolve_customization.py docstrings: drop the "No uv ... plain python3 is sufficient" claims; frame uv run as the standard, python3 as the transition fallback; examples use uv run - customize-bmad.md (en/fr/vi-vn): same reframing; example commands use uv run - Update uv run hints in brain.py / list_customizable test comments	2026-06-22 00:03:03 -05:00
Emmanuel Atsé	cede485217	feat(docs): Add sidebar order validator for doc frontmatter (#2409) ... * feat(docs): add sidebar order validator Adds tools/validate-sidebar-order.js to validate sidebar.order values in YAML frontmatter across English and translated docs. Checks for duplicate orders, gaps in sequence, and missing order fields. For translations, also warns on order drift from English counterparts. Wired into the quality script as docs:validate-sidebar. * fix(validate-sidebar): tighten language detection and drift guard, add docstrings * fix(validate-sidebar): replace subdirectory heuristic with locale pattern matching detectLanguageDirs() previously classified any top-level docs/ directory containing subdirectories as a translation language. This was too broad — if an English section ever gained nested subfolders it would be silently excluded from validation. Replaced with a BCP 47 locale-code regex (/^[a-z]{2}(?:-[a-zA-Z]{2})?$/) that matches known patterns (cs, fr, vi-vn, zh-cn) and won't falsely classify content sections like explanation/ or reference/. * fix(validate-sidebar): guard drift check against undefined order values extractSidebarOrder() returns { hasSidebar: false } when no sidebar block exists, leaving order as undefined rather than null. The drift check only guarded against null, allowing undefined values to emit noisy warnings like "Order drift: ... order undefined". Changed the guard to typeof === 'number' which correctly excludes both undefined and null without relying on a specific sentinel value. * chore(validate-sidebar): add JSDoc docstrings to all functions Adds @param and @returns annotations to extractSidebarOrder, detectLanguageDirs, getEnglishSections, checkDirectory, checkTranslationDrift, and relativePath. * fix(validate-sidebar): add to pre-commit hook * refactor(validate-sidebar): harden parsing and edge-case handling Refactor to main() wrapper with pure return-based APIs, single directory scan, and shared reporting. Harden frontmatter parsing (anchored delimiter, direct-child-only order extraction, flow mapping support) and validation (Infinity/zero guard, gap flood cap, multi-segment locales, graceful ENOENT). * docs: fix sidebar.order duplicates and gaps across all locales Resolves all validator errors flagged by the new tools/validate-sidebar-order.js check. English (docs/{explanation,how-to,reference}/): - Renumbered to remove duplicates; established reading order for new explanation pages added since orders were last set. Translations (cs, fr, vi-vn, zh-cn): - Mirrored English structural ordering where files exist, then compacted to 1..N within each directory to eliminate gaps caused by missing translation files. Non-blocking drift warnings remain where translation directories have fewer files than English; these are expected per the validator's design. --------- Co-authored-by: Brian Madison <bmadcode@gmail.com>	2026-05-25 10:15:37 -05:00
Brian	aa6dece05d	feat(bmad-spec): introduce Spec kernel distiller skill (#2417) ... * feat(bmad-spec): add Spec kernel distiller skill New 2-plan-workflows skill that distills any intent input (brain dump, PRD, transcript, brief) into a spec.md carrying the five-field kernel: Problem, Capabilities, Constraints, Non-goals, Success signal. Headless callers receive JSON; interactive runs close conversationally with the spec path and gap-coverage invitations. Includes: - SKILL.md with activation contract and conventions - customize.toml exposing template path, output path, run-folder pattern - assets/spec-template.md (five-field skeleton) - assets/headless-schemas.md (JSON IO contracts) * remove brain-dump fallback config from bmad-spec customize.toml * refactor(bmad-spec): companions+sources model, routing tilt, flat output path - Collapse `related:` into `companions:`; companion paths may point inside the spec folder (spec-authored) or outside it (adopted from an upstream skill), distinguished implicitly by path - `sources:` reserved for fully-absorbed inputs; downstream does NOT read these - Soften mutation contract: bmad-spec owns SPEC.md and spec-authored companions; adopted companions belong to their originating skill - Add "when to spawn a companion" tilt: multi-item catalogs, tables, diagrams (always), editorial voice rules; sub-bullets in a kernel field signal it has outgrown the kernel - Fix Spec Law rule 7 and Pass 2: load-bearing content lands in SPEC.md or a companion, not the decision log (the log records wrapper-drops only) - Flatten output path to `{planning_artifacts}/specs/spec-{slug}-{date}/`, mirroring `prds/` and `ux-designs/`; drop `spec_folder_name` (no longer used) - Extract Load-bearing definition into its own section above Spec Law * chore(core): retire bmad-distillator, promote bmad-spec to core - Delete bmad-distillator/ and all registry + doc references (superseded by bmad-spec; no skill or workflow in any BMad module invoked it) - Add bmad-distillator to removals.txt so installer cleans it from existing IDE skill directories on update - Move bmad-spec from bmm-skills/2-plan-workflows/ to core-skills/ (universal scope: game design, research hypotheses, editorial briefs, policy, business plans, not just software) - Register bmad-spec in core module-help.csv and bmad-pro-skills marketplace plugin - Drop bmad-distillator section from core-tools.md (en, vi-vn, cs, fr, zh-cn) and vi-vn dev guide; renumber subsequent sections * refactor(bmad-spec): add lean-prose discipline + generalize help text - Add Spec Law rule 8: lean prose. Every sentence carries load-bearing content; cut decoration, hedges, backstory, throat-clearing. Applies to SPEC.md, companions, and decision log. - Update Self-Validate Pass 1 to enforce rules 1-6 and 8 (rule 7 stays in Pass 2) - Prime the operation up-front: write lean from the first pass, every sentence must earn its place - Note in Companions section that companions follow the same lean discipline - Generalize core module-help.csv entry: domain-agnostic framing (software, game design, research, editorial, policy, business, anything intent-bearing); call out succinct, no-fluff and "locks the WHAT before the HOW" as the value props * fix(bmad-spec): address PR review findings (CodeRabbit + Augment) - headless-schemas.md: rewrite spec_path examples to point at the spec folder (not a file), rename source_artifact to sources[] array, add companions[] array, update verdict from "six rules" to "eight rules", disambiguate reason requirement (only when status=blocked) - SKILL.md activation: fix config path from {project-root}/_bmad/config.yaml to {project-root}/_bmad/core/config.yaml (matches other BMM skills) - customize.toml + SKILL.md Workspace: drop {date} from default run_folder_pattern (spec-{slug}); same slug = same folder = trivial in-place update, no glob-and-pick-most-recent needed. Override available for users who want dated history. - spec-template.md: rename "## Success signals" (plural) to "## Success signal" (singular) to match SKILL.md kernel naming - SKILL.md Frontmatter conventions: fix adopted-companion example path from _bmad-output/ux-designs/foo-ux/DESIGN.md to ../../ux-designs/ux-foo-bar-2026-05-23/DESIGN.md (matches actual flat-output convention) - SKILL.md Spec Law: fix double-period typo in rule 2 ((stack, conventions)..) - SKILL.md Overview: fix awkward "bloat with expansive line item details the kernel" phrasing; drop software-flavored downstream consumer list since bmad-spec is now a core skill serving any domain * fix(bmad-spec): drop {planning_artifacts} dependency; output to {output_folder}/specs bmad-spec is a core skill but its default path used {planning_artifacts}, a bmm-module variable. Core-only installs (no bmm) would fail at activation when the resolver tried to expand the path. Land specs directly under {output_folder}/specs/spec-{slug}/ instead. Works in any install regardless of installed modules, and aligns with the long-term BMad direction of grouping artifacts as siblings under {output_folder}/<type>/ rather than nested under planning vs implementation parents. In bmm installs, adopted-companion paths from spec to UX/PRD pick up one extra .. (e.g., ../planning-artifacts/ux-designs/<run>/DESIGN.md) since the spec folder is now one level up from planning-artifacts. Examples in SKILL.md and headless-schemas.md updated. module-help.csv output-location updated and stale -{date} fragment removed. * docs(bmad-spec): add reference docs, trim headless schema, tighten defaults - Add full bmad-spec entry to docs/reference/core-tools.md and table-row stubs to cs/fr/vi-vn/zh-cn (full translation pending). - Strip headless-schemas.md to a minimal {status, files} success response and {status, error_code, reason} blocked response. Drop spec_path, capabilities, verdict, decision_log_path — all derivable from the files themselves. - Narrow customize.toml persistent_facts default from recursive glob to single {project-root}/project-context.md; document override path. - Drop unused {doc_workspace} convention line from SKILL.md. - Clarify Self-Validate verdict handling for interactive vs headless. - Document missing_slug error code in SKILL.md + headless schema.	2026-05-24 14:08:34 -05:00
Brian	ee47e30cf6	refactor(bmad-ux): spine-based UX skill (DESIGN.md + EXPERIENCE.md) (#2413) ... * refactor(bmad-ux): replace bmad-create-ux-design with lean spine-based bmad-ux * refactor(bmad-ux): adopt DESIGN.md spec, split into two-file spine, align prd/brief DESIGN.md (visual identity per the Google Labs spec) and EXPERIENCE.md (behavior, flow, IA) replace the single design.md spine. EXPERIENCE.md cross-references DESIGN.md tokens via the spec's {path.to.token} syntax. Example suite restructure - 3 DESIGN.md examples: editorial (Stitch source / Linen & Logic), calm native mobile (Quill), shadcn-on-Tailwind web SaaS (Drift) - 2 paired EXPERIENCE.md examples (Quill, Drift); Linen & Logic unpaired to model the Stitch handoff scenario - Replaces the prior 2-example combined spine set Discovery additions (outcome-driven, one line each) - Source scan: glob {planning_artifacts}/ for candidates, parent never reads - Form-factor: resolve before IA closes; journeys often derive it - Surface closure: every stated need has a surface, every surface a journey - Named-protagonist journeys (Mary, not "the user") - Design handoff working mode (extensible producer registry, default: Stitch) PRD and brief alignment with same insights - bmad-prd: dropped standalone Primary Persona section from template; renamed "Personas + Journeys" entry to "Journey-led"; named-protagonist rule on UJs; form-factor probe; validation checklist updated - bmad-product-brief: form-factor surfaced in Discovery topics Quality scan fixes - Added ## Overview heading; renamed ## Activation to ## On Activation - Replaced ../ paths in example assets with {planning_artifacts}/ - Sources section compressed (abstract delta-only rule) - Working mode aligned to "Fast path" / "Coaching path" BMad-wide convention New - references/design-md-spec.md: working summary of the spec for the LLM - customize.toml: design_md_examples, experience_md_examples, design_handoffs registries - .prettierignore: ignore .analysis/ quality-scan artifacts repo-wide * refactor(bmad-ux): activation parity with prd/brief, opt-in reviewer gate, no headline grade - Restructure On Activation as numbered six-step list mirroring bmad-prd and bmad-product-brief, restoring the explicit key-resolution list that earlier crammed-paragraph form had dropped (planning_artifacts and friends were silently unresolved at Create). - Make Reviewer Gate opt-in and lens-selectable. At Finalize, ask before spending tokens on parallel reviewer subagents; at Validate intent, skip that question but still confirm lens picks. Stops the auto-run WCAG audit on hobby-stakes work. - Drop the overall validation grade. Per-category verdicts and severity counts already say what is true; a single headline grade conflated design rigor with release readiness and led "POOR" pills landing on reports whose own bodies described the work as strong. Removed from references/validate.md (ladder rule + markdown twin), HTML template (grade pill div + CSS vars + classes). - Trim creative-tools.md: drop the Custom entries section. Runtime prompt files should only carry what the LLM needs to act in this moment; how-to-extend-via-TOML is setup-time human documentation already covered by customize.toml comments. * fix(bmad-ux): align validation report template with 8-category rubric Template placeholders referenced 'Decision-readiness' and 'seven dimensions' from the prior rubric. Replace with TEMPLATE_CATEGORY_NAME and inline the eight canonical categories from references/validate.md so the synthesis pass names them verbatim. * fix(validate-skills): remove stale WF-01/WF-02 rules WF-01/WF-02 were originally scoped to workflow.md files (now mostly gone) but had been generalized to flag name/description in any non-SKILL.md markdown. That over-captured legitimate spec files — e.g. DESIGN.md examples in bmad-ux/assets/ that carry name/description per the Google Labs DESIGN.md spec. Step files are already covered by STEP-06. Rule count: 14 → 12. * fix(bmad-ux): address PR review followups - validation-report-template.html: severity badge class is badge-sev-*, not sev-* (the comment misled the synthesis pass). - Sweep dangling bmad-create-ux-design references: module-help.csv, bmad-agent-ux-designer/customize.toml, bmad-prd/SKILL.md handoff list, workflow-map.md (en + 4 translations), getting-started.md (en + 4 translations). Workflow-map output column updated to DESIGN.md + EXPERIENCE.md. - references/validate.md: Markdown capitalized as a proper noun.	2026-05-22 23:16:06 -05:00
Davor Racic	0f852a38ac	feat(prompts): add directory prompt with updated Clack runtime (#2387) ... * chore(deps): update @clack/core and @clack/prompts to latest versions and adjust Node.js engine requirement * feat(prompts): add directory prompt with autocomplete and create-directory support * chore(docs): update Node.js version requirement to 20.12+ across multiple documentation files * fix(prompts): code review fixes	2026-05-16 18:30:25 -05:00
LanyGuan	b4d73b7daf	Fix installer custom modules http (#2344) ... * fix(installer): preserve http protocol in custom module clone URLs Previously, parseSource() hardcoded 'https://' when building cloneUrl, forcing http:// Git URLs (e.g., internal LAN hosts) to upgrade to https. This broke cloning for self-hosted Git servers that only serve over HTTP. - Capture the protocol from the regex match instead of discarding it - Update JSDoc and inline comments to document HTTP support - Update install-custom-modules docs (EN, ZH, VN) to list HTTP URL type Fixes the --custom-source flag for http:// addresses. * docs(installer): update JSDoc to mention HTTP support in cloneRepo Add HTTP to the cloneRepo method's JSDoc param description. Also fixes minor spacing in empty arrow functions (formatting). * docs(installer): fix JSDoc annotation for cloneRepo param Correct @param backtick escaping in cloneRepo JSDoc. Also documents HTTP as a supported protocol alongside HTTPS and SSH. --------- Co-authored-by: 关惠民 <9155544@qq.com>	2026-04-27 19:58:38 -05:00
miendinh	16c9976d7e	docs(vi-vn): sync and update Vietnamese documentation (#2291) ... Co-authored-by: miendinh <miendinh@users.noreply.github.com>	2026-04-21 21:31:53 -05:00
Alex Verkhovsky	edfb405e27	fix(docs): update stale Analyst triggers and add PRFAQ link (#2238) ... Analyst (Mary) triggers were listed as BP, RS, CB, WB, DP but the actual agent source defines BP, MR, DR, TR, CB, WB, DP. Update all locale agents.md files. Also add PRFAQ Working Backwards hyperlink to commands.md in en, cs, and vi-vn. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	2026-04-09 22:18:08 -07:00
miendinh	b018c7ad7c	docs(vi-vn): sync translations and add missing checkpoint-preview page (#2222) ... Co-authored-by: miendinh <miendinh@users.noreply.github.com>	2026-04-09 20:49:18 -07:00
Brian	5dbfb588ee	refactor(installer): remove custom content installation feature (#2227) ... * refactor(installer): remove custom content installation feature Remove the entire local filesystem custom content feature from the installer to make way for marketplace-based plugin installation. Deleted: custom-handler.js, custom-module-cache.js, custom-modules.js Removed: --custom-content CLI flag, interactive custom content prompts, custom module caching, manifest tracking, missing-source resolution, and related test suites. Updated docs across all translations. * fix: address review findings from Augment Fix admonition syntax (remove accidental space in :::note) across 4 translated docs files, and update stale JSDoc on listAvailable().	2026-04-07 21:41:03 -05:00
Alex Verkhovsky	0edcd0571f	fix(docs): correct translation fidelity issues in Vietnamese docs (#2192) ... Sync Vietnamese translations with current English source: - Update agent table to consolidated Developer agent architecture - Fix bmad-dev -> bmad-agent-dev skill ID references - Replace Quinn/QA agent framing with built-in QA workflow - Fix SM agent -> Developer agent in getting-started - Fix broken platform-codes.yaml URL - Add missing Validation Commands section to style guide - Fix malformed table row in style guide - Remove unsourced content additions in project-context - Fix roadmap section heading and index link format - Fix accountability softening in party-mode dialogue	2026-04-02 20:46:44 -07:00
miendinh	072de34450	docs(vi-vn): add Vietnamese translation for BMAD documentation (#2110) ... * docs(vi-VN): add Vietnamese translation for BMAD documentation * feat(i18n): add Vietnamese website locale * docs(vi-VN): refine translated documentation * docs(vi-VN): sync terminology with latest upstream docs * fix(docs): normalize Vietnamese locale path casing * docs(vi): update non-interactive installation translation * docs(vi): translate analysis phase explanation * docs(vi): sync updated reference and tutorial pages --------- Co-authored-by: miendinh <miendinh@users.noreply.github.com>	2026-04-02 20:44:13 -07:00