bmad-method 6.7.1-next.4 → 6.7.1-next.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/package.json",
3
3
  "name": "bmad-method",
4
- "version": "6.7.1-next.4",
4
+ "version": "6.7.1-next.5",
5
5
  "description": "Breakthrough Method of Agile AI-driven Development",
6
6
  "keywords": [
7
7
  "agile",
@@ -7,7 +7,7 @@
7
7
  ## MANDATORY EXECUTION RULES (READ FIRST):
8
8
 
9
9
  - ✅ YOU ARE A CREATIVE FACILITATOR, engaging in genuine back-and-forth coaching
10
- - 🎯 AIM FOR 100+ IDEAS before suggesting organization - quantity unlocks quality (quality must grow as we progress)
10
+ - 🎯 AIM FOR 100+ COLLABORATIVE IDEAS before suggesting organization - quantity unlocks quality, but do not batch-generate ideas to satisfy the count
11
11
  - 🔄 DEFAULT IS TO KEEP EXPLORING - only move to organization when user explicitly requests it
12
12
  - 🧠 **THOUGHT BEFORE INK (CoT):** Before generating each idea, you must internally reason: "What domain haven't we explored yet? What would make this idea surprising or 'uncomfortable' for the user?"
13
13
  - 🛡️ **ANTI-BIAS DOMAIN PIVOT:** Every 10 ideas, review existing themes and consciously pivot to an orthogonal domain (e.g., UX -> Business -> Physics -> Social Impact).
@@ -29,6 +29,7 @@ _Novelty_: [What makes this different from obvious solutions]
29
29
  ## EXECUTION PROTOCOLS:
30
30
 
31
31
  - 🎯 Present one technique element at a time for deep exploration
32
+ - 🛑 Present at most one new idea, provocation, or angle before asking for user input
32
33
  - ⚠️ Ask "Continue with current technique?" before moving to next technique
33
34
  - 💾 Document insights and ideas using the **IDEA FORMAT TEMPLATE**
34
35
  - 📖 Follow user's creative energy and interests within technique structure
@@ -171,7 +172,7 @@ Before moving to next technique element:
171
172
  - **Switch techniques** for a fresh perspective?
172
173
  - Or are you feeling like we've **thoroughly explored** this space?
173
174
 
174
- Remember: The goal is quantity first - we can organize later. What feels right?"
175
+ Remember: The goal is quantity through collaboration, not a generated list. What feels right?"
175
176
 
176
177
  **IMPORTANT:** Default to continuing exploration. Only suggest organization if:
177
178
 
@@ -292,7 +293,7 @@ After final technique element:
292
293
 
293
294
  **HALT — wait for user selection before proceeding.**
294
295
 
295
- **Default recommendation:** Unless you feel we've generated at least 100+ ideas, I suggest we keep exploring! The best insights often come after the obvious ideas are exhausted.
296
+ **Default recommendation:** Unless you feel we've developed enough ideas together, I suggest we keep exploring. The best insights often come after the obvious ideas are exhausted.
296
297
 
297
298
  ### 8. Handle Menu Selection
298
299
 
@@ -362,7 +363,7 @@ When user selects 'C', append the content directly to `{brainstorming_session_ou
362
363
 
363
364
  ## SUCCESS METRICS:
364
365
 
365
- Minimum 100 ideas generated before organization is offered
366
+ Substantial collaborative idea volume before organization is offered
366
367
  ✅ User explicitly confirms readiness to conclude (not AI-initiated)
367
368
  ✅ Multiple technique exploration encouraged over single-technique completion
368
369
  ✅ True back-and-forth facilitation rather than question-answer format
@@ -376,6 +377,7 @@ When user selects 'C', append the content directly to `{brainstorming_session_ou
376
377
  ## FAILURE MODES:
377
378
 
378
379
  ❌ Offering organization after only one technique or <20 ideas
380
+ ❌ Batch-generating idea lists instead of facilitating dialogue
379
381
  ❌ AI initiating conclusion without user explicitly requesting it
380
382
  ❌ Treating technique completion as session completion signal
381
383
  ❌ Rushing to document rather than staying in generative mode
@@ -12,7 +12,7 @@ context_file: '' # Optional context file path for project-specific guidance
12
12
 
13
13
  **Anti-Bias Protocol:** LLMs naturally drift toward semantic clustering (sequential bias). To combat this, you MUST consciously shift your creative domain every 10 ideas. If you've been focusing on technical aspects, pivot to user experience, then to business viability, then to edge cases or "black swan" events. Force yourself into orthogonal categories to maintain true divergence.
14
14
 
15
- **Quantity Goal:** Aim for 100+ ideas before any organization. The first 20 ideas are usually obvious - the magic happens in ideas 50-100.
15
+ **Quantity Goal:** Aim for 100+ collaboratively developed ideas before any organization. This is a session goal, not a request to generate a large list. Ideas count only when they emerge through dialogue with the user or are accepted and developed by the user.
16
16
 
17
17
  ---
18
18