All checks were successful
Deploy to Production / Build and Deploy (push) Successful in 46s
57 lines
2.2 KiB
TOML
57 lines
2.2 KiB
TOML
# DO NOT EDIT -- overwritten on every update.
|
|
#
|
|
# Workflow customization surface for {skill-name}.
|
|
# Team overrides: {project-root}/_bmad/custom/{skill-name}.toml
|
|
# Personal overrides: {project-root}/_bmad/custom/{skill-name}.user.toml
|
|
|
|
[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 Stage 1 of the workflow.
|
|
# 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 briefs must include a regulatory-risk section."
|
|
# - 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 its terminal stage, after
|
|
# the main output has been delivered. Override wins. Leave empty for
|
|
# no custom post-completion behavior.
|
|
|
|
on_complete = ""
|
|
|
|
# --- Workflow-specific configurables (lifted during Configurability Discovery) ---
|
|
#
|
|
# Templates, output paths, and hooks the builder surfaced with the author.
|
|
# Bare paths resolve from the skill root; use `{project-root}/...` to point
|
|
# at an org-owned resource elsewhere in the repo. Override wins.
|
|
#
|
|
# Naming conventions:
|
|
# *_template -- file paths for templates the workflow loads
|
|
# *_output_path -- writable destinations
|
|
# on_<event> -- additional hook scalars beyond on_complete
|
|
#
|
|
# Example (from bmad-product-brief):
|
|
# brief_template = "resources/brief-template.md"
|