BMAD-METHOD/src/bmm/workflows/bmad-quick-flow/quick-dev/steps
Brian Madison 09316ecc7f fix: remove forbidden workflow_path variable from step files
Remove the forbidden `workflow_path` frontmatter variable from 16 step files
across 3 workflows (quick-dev, quick-spec, check-implementation-readiness).
Per BMAD workflow standards, step files should use relative paths or
{project-root} references instead.

Changes:
- quick-dev (6 files): removed workflow_path and unused thisStepFile
- quick-spec (4 files): removed workflow_path, updated templateFile to use relative path
- check-implementation-readiness (6 files): removed workflow_path, updated all references to use relative paths

Also fixes incorrect path in check-implementation-readiness that referenced
non-existent 'implementation-readiness' folder instead of 'check-implementation-readiness'.

Fixes #1546
2026-02-06 21:16:14 -06:00
..
step-01-mode-detection.md fix: remove forbidden workflow_path variable from step files 2026-02-06 21:16:14 -06:00
step-02-context-gathering.md fix: remove forbidden workflow_path variable from step files 2026-02-06 21:16:14 -06:00
step-03-execute.md fix: remove forbidden workflow_path variable from step files 2026-02-06 21:16:14 -06:00
step-04-self-check.md fix: remove forbidden workflow_path variable from step files 2026-02-06 21:16:14 -06:00
step-05-adversarial-review.md fix: remove forbidden workflow_path variable from step files 2026-02-06 21:16:14 -06:00
step-06-resolve-findings.md fix: remove forbidden workflow_path variable from step files 2026-02-06 21:16:14 -06:00