Skills › BMAD Method › bmad-retrospective › customize.toml
customize.toml
39 lines · skills/bmad-retrospective/customize.toml at bd70c64
1# DO NOT EDIT -- overwritten on every update.
2#
3# Workflow customization surface for bmad-retrospective. Mirrors the
4# agent customization shape under the [workflow] namespace.
6[workflow]
8# --- Configurable below. Overrides merge per BMad structural rules: ---
9# scalars: override wins • arrays (persistent_facts, activation_steps_*): append
10# arrays-of-tables with `code`/`id`: replace matching items, append new ones.
12# Steps to run before the standard activation.
13# Overrides append. Use for pre-flight loads, compliance checks, etc.
15activation_steps_prepend = []
17# Steps to run after persistent facts load but before the workflow begins.
18# Overrides append. Use for context-heavy setup that should happen
19# once activation context is in place.
21activation_steps_append = []
23# Persistent facts the workflow keeps in mind for the whole run
24# (standards, compliance constraints, stylistic guardrails).
25# Distinct from the runtime memory sidecar — these are static context
26# loaded on activation. Overrides append.
27#
28# Each entry is either:
29# - a literal sentence, e.g. "All retrospectives must produce SMART action items with named owners."
30# - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
31# (glob patterns are supported; the file's contents are loaded and treated as facts).
33persistent_facts = []
35# Scalar: executed at the end of Phase 5 (Finalize), after the retrospective
36# document is saved. Override wins.
37# Leave empty for no custom post-completion behavior.
39on_complete = ""