bmad-template/.trae/skills/bmad-create-epics-and-stories/customize.toml

# DO NOT EDIT -- overwritten on every update.
#
# Workflow customization surface for bmad-create-epics-and-stories. Mirrors the
# agent customization shape under the [workflow] namespace.

[workflow]

# --- Configurable below. Overrides merge per BMad structural rules: ---
#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.

# Steps to run before the standard activation (config load, greet).
# Overrides append. Use for pre-flight loads, compliance checks, etc.

activation_steps_prepend = []

# Steps to run after greet but before the workflow begins.
# Overrides append. Use for context-heavy setup that should happen
# once the user has been acknowledged.

activation_steps_append = []

# Persistent facts the workflow keeps in mind for the whole run
# (standards, compliance constraints, stylistic guardrails).
# Distinct from the runtime memory sidecar — these are static context
# loaded on activation. Overrides append.
#
# Each entry is either:
#   - a literal sentence, e.g. "All epics must deliver complete end-to-end user value."
#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
#     (glob patterns are supported; the file's contents are loaded and treated as facts).

persistent_facts = [
  "file:{project-root}/**/project-context.md",
]

# Scalar: executed when the workflow reaches Step 4 (Final Validation) and the
# user confirms [C] Complete — after the epics.md is saved and bmad-help is invoked.
# Override wins. Leave empty for no custom post-completion behavior.

on_complete = ""