diff --git a/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/instructions.md b/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/instructions.md index b2b8a331..b1635173 100644 --- a/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/instructions.md +++ b/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/instructions.md @@ -32,18 +32,115 @@ - **[t] Plan first** - Create tech-spec then implement + + + +Evaluate escalation threshold against user input (minimal tokens, no file loading): + +**Triggers escalation** (if 2+ signals present): + +- Multiple components mentioned (e.g., dashboard + api + database) +- System-level language (e.g., platform, integration, architecture) +- Uncertainty about approach (e.g., "how should I", "best way to") +- Multi-layer scope (e.g., UI + backend + data together) +- Extended timeframe (e.g., "this week", "over the next few days") + +**Reduces signal:** + +- Simplicity markers (e.g., "just", "quickly", "fix", "bug", "typo", "simple", "basic", "minor") +- Single file/component focus +- Confident, specific request + +Use holistic judgment, not mechanical keyword matching. + + + + **[t] Plan first** - Create tech-spec then implement **[e] Execute directly** - Start now - - Load and execute {create_tech_spec_workflow} - Continue to implementation after spec complete + + Load and execute {create_tech_spec_workflow} + Continue to implementation after spec complete + + + + Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start. + step_2 + + - - Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start. - step_2 + + + Load {project_levels} and evaluate user input against detection_hints.keywords + Determine level (0-4) using scale-adaptive definitions + + + + **[t] Plan first** - Create tech-spec then implement + +**[e] Execute directly** - Start now + + + Load and execute {create_tech_spec_workflow} + Continue to implementation after spec complete + + + + Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start. + step_2 + + + + + This looks like a focused feature with multiple components. + +**[t] Create tech-spec first** (recommended) +**[w] Seems bigger than quick-dev** — see what BMad Method recommends (workflow-init) +**[e] Execute directly** + + + Load and execute {create_tech_spec_workflow} + Continue to implementation after spec complete + + + + Load and execute {workflow_init} + EXIT quick-dev - user has been routed to BMad Method + + + + Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start. + step_2 + + + + + + This sounds like platform/system work. + +**[w] Start BMad Method** (recommended) (workflow-init) +**[t] Create tech-spec** (lighter planning) +**[e] Execute directly** - feeling lucky + + + Load and execute {workflow_init} + EXIT quick-dev - user has been routed to BMad Method + + + + Load and execute {create_tech_spec_workflow} + Continue to implementation after spec complete + + + + Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start. + step_2 + + + + diff --git a/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml b/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml index 3f9ca77e..7c2de639 100644 --- a/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml +++ b/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml @@ -25,5 +25,9 @@ create_tech_spec_workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quic party_mode_exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md" advanced_elicitation: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml" +# Routing resources (lazy-loaded) +project_levels: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/project-levels.yaml" +workflow_init: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml" + standalone: true web_bundle: false