fix: add consumer propagation check to bmad-quick-dev workflow

When introducing new type variants, error codes, or DB values, the
workflow now requires enumerating all consumers in the Code Map during
planning (step-02) and HALTs implementation (step-03) if consumer
tracing was missed.

Fixes #2122

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

src/bmm-skills/4-implementation/bmad-quick-dev/step-02-plan.md

@@ -12,7 +12,7 @@ deferred_work_file: '{implementation_artifacts}/deferred-work.md'
 
 ## INSTRUCTIONS
 
-1. Investigate codebase. _Isolate deep exploration in sub-agents/tasks where available. To prevent context snowballing, instruct subagents to give you distilled summaries only._
+1. Investigate codebase. _Isolate deep exploration in sub-agents/tasks where available. To prevent context snowballing, instruct subagents to give you distilled summaries only._ If the approach introduces new type variants, error codes, or DB values: grep all consumers of the parent type/column and annotate each in the Code Map as `consumer — update required` or `consumer — excluded (reason)`.
 2. Read `./spec-template.md` fully. Fill it out based on the intent and investigation, and write the result to `{wipFile}`.
 3. Self-review against READY FOR DEVELOPMENT standard.
 4. If intent gaps exist, do not fantasize, do not leave open questions, HALT and ask the human.

src/bmm-skills/4-implementation/bmad-quick-dev/step-03-implement.md

@@ -14,6 +14,8 @@
 
 Verify `{spec_file}` resolves to a non-empty path and the file exists on disk. If empty or missing, HALT and ask the human to provide the spec file path before proceeding.
 
+If the spec introduces new type variants, error codes, or DB values and the Code Map has no consumer annotations, HALT — consumer tracing was missed in planning.
+
 ## INSTRUCTIONS
 
 ### Baseline