customize.toml 2.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253
  1. # DO NOT EDIT -- overwritten on every update.
  2. #
  3. # Workflow customization surface for bmad-spec.
  4. #
  5. # Override files (not edited here):
  6. # {project-root}/_bmad/custom/bmad-spec.toml (team)
  7. # {project-root}/_bmad/custom/bmad-spec.user.toml (personal)
  8. [workflow]
  9. # --- Configurable below. Overrides merge per BMad structural rules: ---
  10. # scalars: override wins • arrays: append
  11. # Steps to run before the standard activation (config load, greet).
  12. activation_steps_prepend = []
  13. # Steps to run after greet but before the operation begins.
  14. activation_steps_append = []
  15. # Persistent facts the workflow keeps in mind for the whole run.
  16. # Each entry is either a literal sentence, a skill prefixed with `skill:`,
  17. # or a `file:`-prefixed path/glob whose contents are loaded as facts.
  18. # Default points to a single top-level file; override in team/user TOML
  19. # to widen the scope (e.g. `_bmad/**/project-context.md`) if needed.
  20. persistent_facts = [
  21. "file:{project-root}/project-context.md",
  22. ]
  23. # Executed when the workflow completes. Scalar or array of instructions.
  24. on_complete = ""
  25. # Spec template. The five-field kernel skeleton. Override the path in
  26. # team/user TOML to enforce a different shape (e.g. a hypothesis field
  27. # for research initiatives, or a mechanics field for games).
  28. spec_template = "assets/spec-template.md"
  29. # Canonical filename for the kernel artifact inside the spec folder.
  30. # Uppercase by convention to signal "the central source of truth."
  31. spec_filename = "SPEC.md"
  32. # Output path for spec folders. Lands directly under {output_folder}
  33. # so bmad-spec works in core-only installs and matches the
  34. # long-term BMad direction of grouping artifacts as siblings under
  35. # {output_folder}/<type>/ rather than nested inside planning vs
  36. # implementation folders.
  37. spec_output_path = "{output_folder}/specs"
  38. # Run-folder pattern inside spec_output_path. Resolved against the
  39. # input-derived slug at activation. Same slug = same folder, so a
  40. # second invocation updates the existing spec in place (capability
  41. # IDs preserved). Override to add {date} or other components if a
  42. # fresh dated history is preferred.
  43. run_folder_pattern = "spec-{slug}"