Version numbers skip. The plugin’s version changes on every skill change so the development channel has something to deliver, but only some of those versions are released. Numbers missing below were never published, and no stable-channel install ever ran them.
Five new skills, a rebuilt planning core, and a second install host.New skills
bd-high-plansettles the shape of a capability before any decomposition — a few discrete, separately testable steps, filed as one planning issue forbd-build-upto break down later.bd-kg-create,bd-kg-refresh, andbd-kg-searchintroduce a project knowledge graph: shared memory of past issues, pull requests, and decisions you can query directly. See Set up your project for binding one.bd-system-questionsanswers questions about the orchestrator itself — why a ticket isn’t running, what’s in flight, how the system is configured.
- Ticket titles and their opening paragraph are now written in Simplified Technical English, with the rest of the body shaped for an agent reading it cold. The questions the skills ask you follow the same style.
- Story points are gone. Sizing is now a judgment about shape — wide and shallow versus deep and targeted — because that predicts whether a ticket lands in one pass and an abstract estimate did not.
bd-mega-build-up changed shape- It no longer produces a design and implementation-plan document pair. The pressure-testing now runs in rounds, finds its own facts rather than asking you for anything it can look up, and writes decision records and glossary entries into your repository as decisions settle.
- Approval gates dropped from three to two.
bd-build-up- Gained dedicated Jira handling, joining
bd-mega-build-upandbd-build-down. Behavior specific to Linear or Jira now lives in adapters shared between skills. - Can extract every step of a planning issue in one pass, including nested breakdowns and children that belong to a different repository.
bd-build-downwaits for a pull request to be ready before commenting, and records what was learned on each issue as it merges.bd-smoke-jumperbuilds and runs the real artifact when a pull request delivers one, rather than inspecting the source.
- Every planning and landing skill consults a bound graph before acting, and skips silently on projects without one.
- The graph can ingest published documentation sites, so answers cite the section they came from.
- The install script installs for Codex as well as Claude Code, with
--codex. See Install BuildDown skills.
The first stable release. The suite reached a versioned, installable state — see BuildDown skills for what it does.
- Versioned installation. A stable channel and a development channel now exist, so you can choose between released versions and ongoing work. Versions and channels covers both.
- The default branch is installable for the first time. Before this release the plugin catalog existed only on the development branch, so an install without a branch specified never resolved. That is why earlier instructions told you to specify one.
bd-build-downno longer hardcodes one ticketing system. Behavior specific to Linear or Jira moved into per-system adapters, so the skill delegates rather than assuming Linear’s state names.- Client-specific references removed throughout the skills and their documentation.
If you installed before this release, your channel was recorded on your machine at install time and a new release cannot move you. Move between channels covers switching, including the caveat that removing a marketplace uninstalls the plugins installed from it.