ebbe.bass/ping-mee-self-service-platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

basic BMAD setup

Browse Source
This commit is contained in:
Ebbe Baß
2026-10-15 08:57:23 +02:00
parent 44029127dc
commit 5e747654b9
438 changed files with 41818 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/skills/bmad/references/initiative.md
+10
View File
@@ -0,0 +1,10 @@
# The active initiative
Work for one body of work lives in an initiative folder under `output_folder`. `active_initiative` under `[core]` in `_bmad/custom/config.user.toml` names the one in use. A skill that handed off here continues its own work when this ends.
1. Run `uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key core.output_folder --key core.active_initiative`. Script not found, or no `output_folder`: BMad is not set up here; offer `bmad setup` first.
2. Tell the user the active initiative, or none. List the `initiative-*` folders under `{output_folder}`, with `{project-root}` substituted.
3. The user picks one, asks for a new one, or clears it. For a new one, ask its name and create `{output_folder}/initiative-<slug>/initiative-<slug>.md`, `<slug>` the name in kebab-case, holding only frontmatter: `type: initiative`, `title`, `parent: none`. `bmad-ticket` fills it in when the user plans the work.
4. Write `active_initiative = "<folder name>"` under `[core]` in `{project-root}/_bmad/custom/config.user.toml`, creating the file or the table when missing and keeping the rest of the file. Clearing removes the line.
5. Confirm the change in one line.