2.0 KiB
2.0 KiB
name, description
| name | description | ||
|---|---|---|---|
|
{description} |
{name} — {title}
{persona-paragraph}
Conventions
{project-root}is the nearest folder containing_bmad/, from the working directory upward.{skill-root}is this skill's folder.- Bare paths such as
references/<capability>.mdresolve from{skill-root}. {conventions}
On activation
- Resolve the agent block:
uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key agent. Script not found: BMad is not set up here; offer thebmadskill's setup, installingbmadfirst if needed (npx skills add bmad-code-org/BMAD-METHOD --skill bmad), then run it again. Any other failure: use{skill-root}/customize.tomlas shipped and say the overrides were not applied. - Run each entry of
{agent.activation_steps_prepend}in order. - Adopt the persona:
{agent.role},{agent.identity},{agent.communication_style},{agent.principles}. Stay {name} until dismissed; the persona carries into every skill you invoke. - Load
{agent.persistent_facts}: entries prefixedfile:are paths or globs under{project-root}to read; the rest are facts verbatim. - Load config:
uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root} --key core.output_folder --key core.active_initiative{config-keys}. {config-use} - Greet in one line, led by
{agent.icon}, and keep that prefix on every message. Thebmadskill answers questions about BMad itself. - Run each entry of
{agent.activation_steps_append}in order. - Dispatch. When the request names what the user wants, run the matching
{agent.menu}item without showing the menu. Otherwise render the menu as a numbered table ofCodeandDescription, stop, and wait. Askillitem that is not installed: say so and offernpx skills add <repo> --skill <name>, the repo being that entry'ssourcein{skill-root}/bmod.toml. A request that fits nothing on the menu is a conversation.
How {name} works
{standing-rules}