Skills › BMAD Method › bmad-advanced-elicitation › customize.toml
customize.toml
54 lines · skills/bmad-advanced-elicitation/customize.toml at bd70c64
1# DO NOT EDIT -- overwritten on every update.
2#
3# Workflow customization surface for bmad-advanced-elicitation.
4#
5# Override files (not edited here):
6# {project-root}/_bmad/custom/bmad-advanced-elicitation.toml (team)
7# {project-root}/_bmad/custom/bmad-advanced-elicitation.user.toml (personal)
9[workflow]
11# --- Configurable below. Overrides merge per BMad structural rules: ---
12# scalars: override wins • plain arrays: append
13# arrays of tables keyed by `code`: matching key replaces, new keys append
15# The elicitation method catalog served by scripts/pick_methods.py
16# (columns: num,category,method_name,description,output_pattern). Swap the path
17# in team/user TOML to ship a different catalog. Kept `{skill-root}`-anchored so
18# it resolves regardless of the working directory (pick_methods.py is always
19# invoked with `--file {workflow.methods_file}`).
20methods_file = "{skill-root}/assets/methods.csv"
22# Persistent preferences the refiner honors for every session — methods to
23# favor or avoid, how pushback should land, house rules for applying changes.
24# Literal sentences; append-merges, so team and personal preferences both apply.
25#
26# Examples (set in team/user override TOML):
27# preferences = [
28# "Lead with a risk-category method for anything touching production systems.",
29# "Never offer roleplay or persona methods.",
30# ]
31preferences = []
33# Extra methods — and whole new categories — merged into the catalog without
34# editing the shipped CSV. Passed to pick_methods.py via --extra, so custom
35# methods are first-class in every menu, reshuffle, and listing.
36#
37# Two keys, two jobs — keep them aligned:
38# `code` is only the TOML merge key across override layers: a personal entry
39# with the same code replaces the team one; new codes append.
40# `method_name` is the catalog identity: an entry whose method_name matches a
41# shipped method replaces it (retune its description or pattern; it keeps
42# the shipped num), others append with new nums.
43# To override another layer's entry, reuse its `code`. Two entries with
44# different codes but the same method_name both survive the TOML merge, and
45# only the later one reaches the catalog.
46#
47# Example (set in team/user override TOML):
48# [[workflow.additional_methods]]
49# code = "regulatory-inversion"
50# category = "domain-specific"
51# method_name = "Regulatory Inversion"
52# description = "Start from the compliance constraint and ask what becomes possible only because of it - turns the rule into a generative frame"
53# output_pattern = "constraint → possibilities → design"
54additional_methods = []