bmadcode · Sep 28, 2026 · Sep 28, 2026 · Sep 28, 2026
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -8,6 +8,7 @@
 
 * `planning_artifacts` and `implementation_artifacts` are no longer read or seeded. Run `bmad migrate method` on a v6 project.
 * The ticketing store's `root` key is gone; the ticket tree is `{output_folder}/{active_initiative}`. To move the store, set `core.output_folder` in `_bmad/custom/config.toml`.
+* `bmad-preview-ticketing` is now `bmad-ticket`. `npx skills update` does not install the new name: run `npx skills add bmad-code-org/BMAD-METHOD --skill bmad-ticket`, and rename `_bmad/custom/bmad-preview-ticketing.toml` to `bmad-ticket.toml` if you have one. Until the v7 release, the old name is a forwarder that says this.
 
 ## v6.12.0 - 2026-09-03
 

diff --git a/docs-site/astro.config.mjs b/docs-site/astro.config.mjs
@@ -31,6 +31,7 @@ export default defineConfig({
     '/how-to/quick-fixes': `${basePath}build/build-a-change/`,
     '/explanation/build': `${basePath}build/build-a-change/`,
     '/explanation/checkpoint-preview': `${basePath}build/walk-through-a-change/`,
+    '/plan/help-test-v7-previews': `${basePath}plan/set-up-the-ticket-tree/`,
     '/build/review-a-completed-change': `${basePath}build/walk-through-a-change/`,
     '/build/checkpoint-a-change': `${basePath}build/walk-through-a-change/`,
     '/fr/explanation/checkpoint-preview': `${basePath}fr/build/walk-through-a-change/`,
@@ -352,8 +353,8 @@ export default defineConfig({
               slug: 'plan/break-work-into-stories-and-track-it',
             },
             {
-              label: 'Help Test v7 Previews',
-              slug: 'plan/help-test-v7-previews',
+              label: 'Set Up the Ticket Tree',
+              slug: 'plan/set-up-the-ticket-tree',
             },
           ],
         },

diff --git a/docs-site/locale-coverage-baseline.json b/docs-site/locale-coverage-baseline.json
@@ -17,7 +17,7 @@
     "plan/define-requirements-and-a-specification",
     "plan/design-ux-and-architecture",
     "plan/explore-and-validate-an-idea",
-    "plan/help-test-v7-previews",
+    "plan/set-up-the-ticket-tree",
     "plan/plan-inside-an-organization",
     "plan/research-a-decision",
     "reference/skills-and-agents",
@@ -43,7 +43,7 @@
     "plan/define-requirements-and-a-specification",
     "plan/design-ux-and-architecture",
     "plan/explore-and-validate-an-idea",
-    "plan/help-test-v7-previews",
+    "plan/set-up-the-ticket-tree",
     "plan/plan-inside-an-organization",
     "plan/research-a-decision",
     "reference/skills-and-agents",
@@ -71,7 +71,7 @@
     "plan/define-requirements-and-a-specification",
     "plan/design-ux-and-architecture",
     "plan/explore-and-validate-an-idea",
-    "plan/help-test-v7-previews",
+    "plan/set-up-the-ticket-tree",
     "plan/plan-inside-an-organization",
     "plan/research-a-decision",
     "reference/skills-and-agents",
@@ -99,7 +99,7 @@
     "plan/define-requirements-and-a-specification",
     "plan/design-ux-and-architecture",
     "plan/explore-and-validate-an-idea",
-    "plan/help-test-v7-previews",
+    "plan/set-up-the-ticket-tree",
     "plan/plan-inside-an-organization",
     "plan/research-a-decision",
     "reference/skills-and-agents",
@@ -128,7 +128,7 @@
     "plan/define-requirements-and-a-specification",
     "plan/design-ux-and-architecture",
     "plan/explore-and-validate-an-idea",
-    "plan/help-test-v7-previews",
+    "plan/set-up-the-ticket-tree",
     "plan/plan-inside-an-organization",
     "plan/research-a-decision",
     "reference/skills-and-agents",

diff --git a/docs-site/src/diagrams/planning-skills.labels.json b/docs-site/src/diagrams/planning-skills.labels.json
@@ -23,16 +23,15 @@
     "design-md-experience-md": "ux-<slug>.md, DESIGN.md, EXPERIENCE.md",
     "bmad-spec": "bmad-spec",
     "spec-md-companions": "spec-<slug>.md + companions",
-    "ticketing-handoff": "ticketing handoff",
+    "ticketing-handoff": "bmad-ticket handoff",
     "spec-when-needed": "Use a spec when needed.",
     "one-session-of-work-goes": "One session of work goes",
     "straight-from-the-spec-to-build": "straight from the spec to Build.",
     "solutioning": "SOLUTIONING",
     "decide-how-divide-the-work": "decide how, divide the work",
     "bmad-architecture": "bmad-architecture",
     "architecture-spine-md": "architecture-<slug>.md",
-    "bmad-preview": "bmad-preview-",
-    "ticketing": "ticketing",
+    "bmad-ticket": "bmad-ticket",
     "ordered-entries": "ordered tickets.toml entries",
     "bmad-build": "bmad-build",
     "build-output": "one session per unit · built → user marks done · keep plans"

diff --git a/docs-site/src/diagrams/planning-skills.svg b/docs-site/src/diagrams/planning-skills.svg
diff --git a/docs/build/autonomous-development-loops.md b/docs/build/autonomous-development-loops.md
@@ -51,10 +51,10 @@ Supported intent shapes include:
 ### Tickets from the Tree
 
 Build Auto reads the tree through `{project-root}/_bmad/method/scripts/tickets.py`,
-the script the [ticketing skill](../plan/break-work-into-stories-and-track-it.md) installs.
+the script [`bmad-ticket`](../plan/break-work-into-stories-and-track-it.md) installs.
 This page describes the repo store, where a ticket's status lives in its plan.
 On a tracker store, `tickets.py mark` refuses to run, so move the ticket on
-the tracker through the ticketing skill.
+the tracker through `bmad-ticket`.
 
 - A named ticket goes through `tickets.py find`. When `find` fails, for example on a reference that matches no ticket or more than one, the run halts with `ticket not resolved`.
 - It builds from the entry in `tickets.toml`, its epic file and what that file's References name, and the entry's story file when it has one. It never writes a ticket file and never runs `tickets.py pull`.
@@ -140,7 +140,7 @@ The plan frontmatter `status` is the main machine-readable state for orchestrati
 | `built`         | The run finished; nobody has called the ticket done yet  | `review`      |
 | `done`          | The user or an orchestrator called the ticket done       | `done`        |
 | `blocked`       | The run cannot safely continue unattended                | `in-progress` |
-| `dropped`       | The ticketing skill dropped the ticket, on the user's word | `dropped`     |
+| `dropped`       | `bmad-ticket` dropped the ticket, on the user's word | `dropped`     |
 
 Build Auto never moves a ticket to `done`. The user or an orchestrator
 marks a ticket done with `tickets.py mark <ref> done`. A follow-up pass on a

diff --git a/docs/build/build-a-change.md b/docs/build/build-a-change.md
@@ -199,7 +199,7 @@ decisions may set patterns for later work. Once those patterns are stable,
 | `bmad-retrospective`  | Review a completed epic against the evidence it left behind ([Finish an Epic](./finish-an-epic.md))                                                           | Retro document, action items, acceptance verdict |
 
 Clear one-session work enters `bmad-build` directly. Larger work is sliced
-into a ticket tree with `bmad-preview-ticketing`, from a spec or any other
+into a ticket tree with `bmad-ticket`, from a spec or any other
 intent, and each build takes one ticket. `bmad-build-auto` does not orchestrate
 those tickets: an AI coding session or another orchestrator, such as bmad-loop,
 dispatches one worker per ticket. See

diff --git a/docs/build/finish-an-epic.md b/docs/build/finish-an-epic.md
@@ -49,7 +49,7 @@ show. It won't invent a root cause or a pattern the code doesn't back up.
 ## What It Reads
 
 The retrospective works on one epic folder in the ticket tree that
-`bmad-preview-ticketing` keeps (see
+`bmad-ticket` keeps (see
 [Break Work into Stories](../plan/break-work-into-stories-and-track-it.md)):
 
 - **`tickets.toml`**: the epic's tickets, in build order.

diff --git a/docs/existing-codebases/getting-deeper.md b/docs/existing-codebases/getting-deeper.md
@@ -158,7 +158,7 @@ documentation. Do not add another Django documentation file or an external
 service. Use diffsettings-audit as the spec folder slug.
 ```
 
-BMad Spec first has you pick or create an initiative, then writes `_bmad-output/initiative-<slug>/spec-diffsettings-audit/spec-diffsettings-audit.md`. Hand it to `bmad-preview-ticketing` to create `epic-diffsettings-audit` and its three ordered entries in `tickets.toml`. Read the spec and entries and answer any questions. Continue when they match the requirements above; note the epic folder the skill creates.
+BMad Spec first has you pick or create an initiative, then writes `_bmad-output/initiative-<slug>/spec-diffsettings-audit/spec-diffsettings-audit.md`. Hand it to `bmad-ticket` to create `epic-diffsettings-audit` and its three ordered entries in `tickets.toml`. Read the spec and entries and answer any questions. Continue when they match the requirements above; note the epic folder the skill creates.
 
 ## 9. Build the Three Stories
 

diff --git a/docs/existing-codebases/start-in-an-existing-codebase.md b/docs/existing-codebases/start-in-an-existing-codebase.md
@@ -17,7 +17,7 @@ ordinary change — an agent doing a small request should not even be
 able to find it by accident.
 
 For a small change, use `[bmad-build](../build/build-a-change.md)`.
-For one that needs several coding sessions, run `bmad-spec`, plan its entries with `bmad-preview-ticketing`, and Build each entry directly. Then run `bmad-retrospective` on the epic. Keep its joined plans as live status and evidence. If it is bigger than that, treat it as a project and follow [Choose a Planning Path](../plan/choose-a-planning-path.md).
+For one that needs several coding sessions, run `bmad-spec`, plan its entries with `bmad-ticket`, and Build each entry directly. Then run `bmad-retrospective` on the epic. Keep its joined plans as live status and evidence. If it is bigger than that, treat it as a project and follow [Choose a Planning Path](../plan/choose-a-planning-path.md).
 
 Too little planning costs one Build run: Build looks at the code
 first, and stops to ask when it cannot settle the intent. Too much

diff --git a/docs/plan/break-work-into-stories-and-track-it.md b/docs/plan/break-work-into-stories-and-track-it.md
@@ -5,15 +5,15 @@ sidebar:
   order: 7
 ---
 
-Use `bmad-preview-ticketing` to split and track work. It accepts described intent, a spec, or a PRD. One small story or bug can go straight to [Build](../build/build-a-change.md) without ticketing.
+Use `bmad-ticket` to split and track work. It accepts described intent, a spec, or a PRD. One small story or bug can go straight to [Build](../build/build-a-change.md) without ticketing.
 
 ## Plan the Work
 
 For several epics, create an initiative and ask the skill to slice it. Each epic gets an envelope with requirements and done-when checks. Incept one epic to propose its stories and bugs in build order, with requirement coverage, dependencies, and verification. Review the breakdown before accepting it.
 
 The initiative's `tickets.toml` lists epics. Each epic's `tickets.toml` lists entries with stable numeric ids. A planned entry needs no story file. Standalone tracked stories and bugs have files in `backlog/`; they do not need an invented epic.
 
-See [Set Up the Ticket Tree](./help-test-v7-previews.md) for store and tracker configuration.
+See [Set Up the Ticket Tree](./set-up-the-ticket-tree.md) for store and tracker configuration.
 
 ## Build an Entry
 
@@ -25,14 +25,14 @@ For unattended work, explicitly dispatch a ticket to `bmad-build-auto`, one invo
 
 ## Track Progress
 
-Ask ticketing “what's next?” or “show status.” Plans carry build progress. A build finishes at `built`, shown in the review column; the user or orchestrator decides when to mark it `done`. A tracker card's status remains separate from build status.
+Ask `bmad-ticket` “what's next?” or “show status.” Plans carry build progress. A build finishes at `built`, shown in the review column; the user or orchestrator decides when to mark it `done`. A tracker card's status remains separate from build status.
 
 Keep completed plans. Deleting one removes the state and evidence later builds, review, and retrospective read.
 
 ## Review and Close
 
-`bmad-code-review` reads a ticket's plan and baseline and appends a dated `Code Review` block. It never changes ticket status. When the epic is finished, run [Retrospective](../build/finish-an-epic.md) with its folder, id, or slug. Retrospective writes its evidence and verdict directly in the epic folder; ticketing handles confirmed closure.
+`bmad-code-review` reads a ticket's plan and baseline and appends a dated `Code Review` block. It never changes ticket status. When the epic is finished, run [Retrospective](../build/finish-an-epic.md) with its folder, id, or slug. Retrospective writes its evidence and verdict directly in the epic folder; `bmad-ticket` handles confirmed closure.
 
 ## Correct Course
 
-Run `bmad-correct-course` when a requirement, architecture choice, or dependency changes significantly. It requires a PRD and your description of the affected work and dependencies. For standalone spec work without a PRD, update the spec with `bmad-spec` instead. Correct-course assesses the available planning documents and writes its proposal as `change-<slug>/change-<slug>.md` in the active initiative's folder, or in the output folder when none is active, with the edits and a ticketing handoff. It does not read or edit the ticket tree. Apply the approved changes through the owning skills, then use ticketing to revise the remaining breakdown.
+Run `bmad-correct-course` when a requirement, architecture choice, or dependency changes significantly. It requires a PRD and your description of the affected work and dependencies. For standalone spec work without a PRD, update the spec with `bmad-spec` instead. Correct-course assesses the available planning documents and writes its proposal as `change-<slug>/change-<slug>.md` in the active initiative's folder, or in the output folder when none is active, with the edits and a `bmad-ticket` handoff. It does not read or edit the ticket tree. Apply the approved changes through the owning skills, then use `bmad-ticket` to revise the remaining breakdown.