Merge ace23f6902 into abf3d25f06

These config keys were added in efc69ffb but never consumed by any
template, conditional logic, or runtime code. They represent platform
capabilities that the agent can determine at runtime — persisting a
stale user guess adds installation friction with zero execution value.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md

@@ -124,13 +124,21 @@ Saved to: {finalFile}
 
 Once you are fully satisfied with the spec (ideally after **Adversarial Review** and maybe a few rounds of **Advanced Elicitation**), it is recommended to run implementation in a FRESH CONTEXT for best results.
 
-Copy this prompt to start dev:
+Load and follow **Adversarial Review** in a fresh context (recommended for information asymmetry):
 
 \`\`\`
-quick-dev {finalFile}
+/bmad-review-adversarial-general "{finalFile}"
 \`\`\`
 
-This ensures the dev agent has clean context focused solely on implementation.
+Load and follow **development** in a fresh context:
+
+\`\`\`
+/quick-dev "{finalFile}"
+\`\`\`
+
+_(Both are slash commands — prefix `/` invokes a BMAD skill or workflow.)_
+
+This ensures the agent has clean context focused solely on its task.
 ```
 
 b) **HALT and wait for user selection.**
@@ -179,7 +187,7 @@ b) **HALT and wait for user selection.**
 When you're ready to implement, run:
 
 ```
-quick-dev {finalFile}
+/quick-dev {finalFile}
 ```
 
 Ship it!"

src/core/module.yaml

@@ -23,13 +23,3 @@ output_folder:
   prompt: "Where should output files be saved?"
   default: "_bmad-output"
   result: "{project-root}/{value}"
-
-tool_supports_subagents:
-  prompt: "Subagents are supported by the LLM or Tool I will be using?"
-  default: true
-  result: "{value}"
-
-tool_supports_agent_teams:
-  prompt: "Agent Teams are supported by the LLM or Tool I will be using?"
-  default: false
-  result: "{value}"