julian
17c08e6392
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24) - apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004) - apps/web: React 19 + Vite 8 (ESM) - libs/shared/api-interface: Zod contract base - Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit - WDS artifacts: - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs) - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact) - Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md - AGENTS.md + README.md como entrada para devs/agentes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
63 lines
2.5 KiB
TOML
63 lines
2.5 KiB
TOML
# DO NOT EDIT -- overwritten on every update.
|
|
#
|
|
# Workflow customization surface for bmad-investigate. Mirrors the
|
|
# agent customization shape under the [workflow] namespace.
|
|
|
|
[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 the workflow begins.
|
|
# 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.
|
|
# Use for citation conventions (path:line vs path#L42), grading-scale
|
|
# overrides (ITIL severity 1-5 instead of High/Medium/Low), tone
|
|
# directives (engineering vs exec-facing), or compliance constraints
|
|
# the case file must respect.
|
|
# Distinct from the runtime memory sidecar — these are static context
|
|
# loaded on activation. Overrides append.
|
|
#
|
|
# Each entry is either:
|
|
# - a literal sentence, e.g. "Use ITIL severity 1-5 instead of High/Medium/Low for confidence."
|
|
# - 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: path to the case-file template, resolved from the skill root.
|
|
# Override to point at an org-shaped template (compliance sections,
|
|
# SLA fields, post-mortem hooks, ITIL fields).
|
|
|
|
case_file_template = "references/case-file-template.md"
|
|
|
|
# Scalar: subdirectory under {implementation_artifacts} where case files land.
|
|
# Override for org taxonomies (forensics/, cases/, incidents/, bug-bash/).
|
|
|
|
case_file_subdir = "investigations"
|
|
|
|
# Scalar: filename pattern for new case files. {slug} expands to the
|
|
# ticket ID or a short user-agreed name.
|
|
|
|
case_file_filename = "{slug}-investigation.md"
|
|
|
|
# Scalar: executed when the workflow finalizes the case file at Outcome 5,
|
|
# after the conclusion is presented. Override wins. Use for post-case
|
|
# automation: post the case to Slack/Teams, push fields back to ticketing,
|
|
# link the case to a sprint, trigger a follow-up retro.
|
|
# Leave empty for no custom post-completion behavior.
|
|
|
|
on_complete = ""
|