# DO NOT EDIT -- overwritten on every update.
#
# Workflow customization surface for bmad-spec.
#
# Override files (not edited here):
#   {project-root}/_bmad/custom/bmad-spec.toml        (team)
#   {project-root}/_bmad/custom/bmad-spec.user.toml   (personal)

[workflow]

# --- Configurable below. Overrides merge per BMad structural rules: ---
#   scalars: override wins • arrays: append

# Steps to run before the standard activation (config load, greet).
activation_steps_prepend = []

# Steps to run after greet but before the operation begins.
activation_steps_append = []

# Persistent facts the workflow keeps in mind for the whole run.
# Each entry is either a literal sentence, a skill prefixed with `skill:`,
# or a `file:`-prefixed path/glob whose contents are loaded as facts.
persistent_facts = [
  "file:{project-root}/**/project-context.md",
]

# Executed when the workflow completes. Scalar or array of instructions.
on_complete = ""

# Spec template — the five-field kernel skeleton. Override the path in
# team/user TOML to enforce a different shape (e.g. a hypothesis field
# for research initiatives, or a mechanics field for games).
spec_template = "assets/spec-template.md"

# Fallback output path used when the input is a brain dump (no source
# artifact to co-locate next to). When the input IS a ceremony artifact
# inside an existing run folder under {planning_artifacts}, the Spec
# is written as a sibling of that artifact instead and this path is
# unused.
spec_output_path = "{planning_artifacts}/spec"

# Run folder pattern for the brain-dump fallback path. Resolved against
# {project_name} and {date} at activation.
run_folder_pattern = "spec-{project_name}-{date}"

# The primary artifact filename. Override if a team prefers `kernel.md`
# or any other convention.
spec_filename = "spec.md"