customize.toml 5.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899
  1. # DO NOT EDIT -- overwritten on every update.
  2. #
  3. # Workflow customization surface for gds-gdd.
  4. #
  5. # Override files (not edited here):
  6. # {project-root}/_bmad/custom/gds-gdd.toml (team)
  7. # {project-root}/_bmad/custom/gds-gdd.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. # Use for pre-flight loads, compliance checks, etc.
  13. activation_steps_prepend = []
  14. # Steps to run after greet but before the workflow begins.
  15. # Use for context-heavy setup that should happen once the user has been acknowledged.
  16. activation_steps_append = []
  17. # Persistent facts the workflow keeps in mind for the whole run
  18. # (standards, compliance constraints, stylistic guardrails).
  19. # Each entry is either a literal sentence, a skill prefixed with `skill:`, or a `file:`-prefixed
  20. # path/glob whose contents are loaded as facts.
  21. #
  22. # Default loads project-context.md if gds-generate-project-context has produced one — this gives
  23. # the facilitator persistent awareness of the project's tech, domain, and constraints without
  24. # re-asking. Common opt-ins (set in team/user override TOML):
  25. # "skill:acme-studio:house-game-pillars" # a skill that contains relevant info
  26. # "Every mechanic in the GDD must trace back to a documented pillar." # generic agent instruction
  27. persistent_facts = [
  28. "file:{project-root}/**/project-context.md",
  29. ]
  30. # Executed when the workflow completes (after the user has been told the
  31. # GDD is ready). Accepts either a string scalar (single instruction)
  32. # or an array of instructions executed in order. Empty for none.
  33. on_complete = ""
  34. # Default GDD structure. Treated as a starting point — the LLM adapts it
  35. # to the game type and project scope. The {{GAME_TYPE_SPECIFIC_SECTIONS}}
  36. # slot is filled from the matched genre guide. Override the path in
  37. # team/user TOML to enforce a different structure (e.g. studio-standard GDD).
  38. gdd_template = "assets/gdd-template.md"
  39. # Validation checklist used at the Validate intent and at Finalize step 3.
  40. # A subagent walks the checklist against gdd.md and returns structured findings.
  41. # The genre and game-type checks read game_types_csv and genre_complexity_csv.
  42. # Override the path in team/user TOML to enforce a studio-specific checklist.
  43. validation_checklist = "assets/gdd-validation-checklist.md"
  44. # HTML template used to render validation findings into a styled, scannable
  45. # report. The renderer (scripts/render-validation-html.py) substitutes
  46. # structured findings + summary stats into this template; the template is
  47. # fully overridable to match studio branding. The default uses inline CSS, no
  48. # external dependencies, and native HTML <details> for collapse — no JS.
  49. validation_report_template = "assets/validation-report-template.html"
  50. # Game-type taxonomy. Drives game-type detection during Discovery and the
  51. # game-type cross-reference check during Validate. Columns: id, name,
  52. # description, genre_tags, fragment_file. Each fragment_file names a genre
  53. # guide under assets/game-types/ that scaffolds the GameType Specific Design
  54. # section. Override the path in team/user TOML to extend the taxonomy.
  55. game_types_csv = "assets/game-types.csv"
  56. # Genre-complexity ratings. Drives the genre-compliance check during Validate
  57. # and tells Discovery which genres carry must-document conventions. Columns:
  58. # genre, signals, complexity, key_concerns, required_knowledge,
  59. # suggested_workflow, special_sections.
  60. genre_complexity_csv = "assets/genre-complexity.csv"
  61. # Run folder location. The GDD, epics file, decision log, and optional
  62. # validation report all land inside `{output_dir}/{output_folder_name}/`.
  63. output_dir = "{planning_artifacts}/gdds"
  64. output_folder_name = "gdd-{project_name}-{date}"
  65. # Document standards applied to human-consumed docs at Finalize. Each entry is
  66. # a `skill:`, `file:`, or plain-text directive; the parent LLM applies the
  67. # findings before the user sees the draft. Empty by default — Game Dev Studio
  68. # ships no editorial-review skills. Add your own in team/user override TOML:
  69. # "skill:my-studio:editorial-review-prose"
  70. # "file:{project-root}/_bmad/style-guides/studio-voice.md"
  71. # "Convert all dates to ISO 8601 format."
  72. doc_standards = []
  73. # External-source registry. Natural-language directives describing knowledge
  74. # bases, MCP tools, or internal systems the LLM may consult during the workflow
  75. # when a relevant need surfaces. The LLM does NOT query these preemptively —
  76. # it consults them on demand. If a named MCP tool is unavailable at runtime,
  77. # the LLM falls back to standard behavior and notes the gap. Empty by default.
  78. external_sources = []
  79. # External-handoff routing. Natural-language directives the LLM applies at
  80. # Finalize to route outputs beyond local files (Confluence, Notion, Google
  81. # Drive, ticket systems, etc.). Handoffs run after the artifact is polished
  82. # and before the final user-facing message. URLs or IDs returned by the
  83. # destination are captured and surfaced to the user. Empty by default.
  84. external_handoffs = []