Skills › BMAD Method › bmad-agent-po › repo-ticketing.toml
repo-ticketing.toml
57 lines · skills/bmad-agent-po/config/repo-ticketing.toml at bd70c64
1# Store starter: tickets as files in the repo, the default. `scripts/read_store.py` reads this file as the
2# base layer; the project's _bmad/custom/ticketing-store-config.toml names the store and replaces any key
3# here, key by key. With no project file this starter is the whole config.
4# It updates with the skill and holds only what is specific to this store: the rules every store shares
5# are in references/board.md. Comments and `description` are never loaded; `description` is for choosing a store.
6#
7# Tickets and artifacts live together as markdown files under `output_folder` (layout in workflow.md,
8# The ticket tree), committed in the monorepo or in a repo of their own. Status and assignee change by commit, and the skill never pushes,
9# so others see them only after a push and pull.
11description = "Quick setup, and the default when nothing else is chosen. Tickets are markdown files under version control: in the monorepo, or in their own repo (recommended for mono and poly repos alike). No tracker or account needed. The simplest store — right for a solo developer or a very small team with no other tracking."
13[tickets]
14store = "repo"
16access = """
17Read and write the files under `output_folder`.
18"""
20fields = """
21risk and severity live in the frontmatter (risk: low|medium|high on any ticket; severity: P0-P3
22on bugs); estimate the same way. Nothing else carries them.
23"""
25[verbs]
26setup = """
27Tickets live in `output_folder` beside the documents. To keep them outside the project, set `output_folder`
28under `[core]` in `_bmad/custom/config.toml` to a folder beside it — the session then launches one level
29up — or in the workspace that already holds the repos. `git init` a new folder so tickets have
30history; skip that when the user picks a folder already under git, the monorepo included. Then
31create `backlog/` and the active initiative's folder there when they do not exist.
32"""
34write = """
35Every change is an edit to the ticket's file, its `tickets.toml` entry, or, for a leaf's status and assignee, its plan through `tickets.py mark`.
36Commit only the files you wrote on the current branch. Root not in a git repo: skip the commit and say so.
37"""
39query = """
40The files are the store: `tickets.py find`, `next`, and `status` answer from them. By a frontmatter field: `grep -rl "^type: bug" <folder>`.
41"""
43# BMad type -> this store's type.
44[tickets.types]
45initiative = "initiative"
46epic = "epic"
47story = "story"
48spike = "spike"
49bug = "bug"
51# BMad state -> this store's status.
52[tickets.status]
53backlog = "backlog"
54in-progress = "in-progress"
55review = "review"
56done = "done"
57dropped = "dropped"