fix(skills): revert out-of-scope changes from validation pass

- Revert step renumbering in retrospective (no validator rule)
- Revert full-scan-instructions, quick-dev-preview, quick-spec changes
- Restore duration/energy/time content in brainstorming steps 02a-d, 03
  (SEQ-02 time estimate removal was misapplied to display templates)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

src/bmm/workflows/4-implementation/bmad-retrospective/workflow.md

@@ -192,12 +192,12 @@ Bob (Scrum Master): "Perfect. Epic {{epic_number}} is complete and ready for ret
 
 </step>
 
-<step n="2" goal="Discover and load project documents">
+<step n="0.5" goal="Discover and load project documents">
   <action>Load input files according to the Input Files table in INITIALIZATION. For SELECTIVE_LOAD inputs, load only the epic matching {{epic_number}}. For FULL_LOAD inputs, load the complete document. For INDEX_GUIDED inputs, check the index first and load relevant sections. After discovery, these content variables are available: {epics_content} (selective load for this epic), {architecture_content}, {prd_content}, {document_project_content}</action>
   <note>After discovery, these content variables are available: {epics_content} (selective load for this epic), {architecture_content}, {prd_content}, {document_project_content}</note>
 </step>
 
-<step n="3" goal="Deep Story Analysis - Extract Lessons from Implementation">
+<step n="2" goal="Deep Story Analysis - Extract Lessons from Implementation">
 
 <output>
 Bob (Scrum Master): "Before we start the team discussion, let me review all the story records to surface key themes. This'll help us have a richer conversation."
@@ -291,7 +291,7 @@ Bob (Scrum Master): "We'll get to all of it. But first, let me load the previous
 
 </step>
 
-<step n="4" goal="Load and Integrate Previous Epic Retrospective">
+<step n="3" goal="Load and Integrate Previous Epic Retrospective">
 
 <action>Calculate previous epic number: {{prev_epic_num}} = {{epic_number}} - 1</action>
 
@@ -387,7 +387,7 @@ Charlie (Senior Dev): "First epic, first retro. Let's make it count."
 
 </step>
 
-<step n="5" goal="Preview Next Epic with Change Detection">
+<step n="4" goal="Preview Next Epic with Change Detection">
 
 <action>Calculate next epic number: {{next_epic_num}} = {{epic_number}} + 1</action>
 
@@ -476,7 +476,7 @@ Bob (Scrum Master): "No problem. We'll still do a thorough retro on Epic {{epic_
 
 </step>
 
-<step n="6" goal="Initialize Retrospective with Rich Context">
+<step n="5" goal="Initialize Retrospective with Rich Context">
 
 <action>Load agent configurations from {agent_manifest}</action>
 <action>Identify which agents participated in Epic {{epic_number}} based on story records</action>
@@ -566,7 +566,7 @@ Bob (Scrum Master): "Exactly. {user_name}, any questions before we dive in?"
 
 </step>
 
-<step n="7" goal="Epic Review Discussion - What Went Well, What Didn't">
+<step n="6" goal="Epic Review Discussion - What Went Well, What Didn't">
 
 <output>
 Bob (Scrum Master): "Let's start with the good stuff. What went well in Epic {{epic_number}}?"
@@ -711,13 +711,13 @@ Bob (Scrum Master): "Does that capture it? Anyone have something important we mi
 
 </step>
 
-<step n="8" goal="Next Epic Preparation Discussion - Interactive and Collaborative">
+<step n="7" goal="Next Epic Preparation Discussion - Interactive and Collaborative">
 
 <check if="{{next_epic_exists}} == false">
   <output>
 Bob (Scrum Master): "Normally we'd discuss preparing for the next epic, but since Epic {{next_epic_num}} isn't defined yet, let's skip to action items."
   </output>
-  <action>Skip to Step 9</action>
+  <action>Skip to Step 8</action>
 </check>
 
 <output>
@@ -835,7 +835,7 @@ Bob (Scrum Master): "{user_name}, does this preparation plan work for you?"
 
 </step>
 
-<step n="9" goal="Synthesize Action Items with Significant Change Detection">
+<step n="8" goal="Synthesize Action Items with Significant Change Detection">
 
 <output>
 Bob (Scrum Master): "Let's capture concrete action items from everything we've discussed."
@@ -1076,7 +1076,7 @@ Bob (Scrum Master): "Everyone clear on what they own?"
 
 </step>
 
-<step n="10" goal="Critical Readiness Exploration - Interactive Deep Dive">
+<step n="9" goal="Critical Readiness Exploration - Interactive Deep Dive">
 
 <output>
 Bob (Scrum Master): "Before we close, I want to do a final readiness check."
@@ -1259,7 +1259,7 @@ Charlie (Senior Dev): "Better to catch this now than three stories into the next
 
 </step>
 
-<step n="11" goal="Retrospective Closure with Celebration and Commitment">
+<step n="10" goal="Retrospective Closure with Celebration and Commitment">
 
 <output>
 Bob (Scrum Master): "We've covered a lot of ground today. Let me bring this retrospective to a close."
@@ -1335,7 +1335,7 @@ Bob (Scrum Master): "See you all when prep work is done. Meeting adjourned!"
 
 </step>
 
-<step n="12" goal="Save Retrospective and Update Sprint Status">
+<step n="11" goal="Save Retrospective and Update Sprint Status">
 
 <action>Ensure retrospectives folder exists: {implementation_artifacts}</action>
 <action>Create folder if it doesn't exist</action>
@@ -1392,7 +1392,7 @@ Retrospective document was saved successfully, but {sprint_status_file} may need
 
 </step>
 
-<step n="13" goal="Final Summary and Handoff">
+<step n="12" goal="Final Summary and Handoff">
 
 <output>
 **✅ Retrospective Complete, {user_name}!**

src/bmm/workflows/bmad-document-project/workflows/full-scan-instructions.md

@@ -89,21 +89,21 @@ Your choice [1/2/3]:
 <check if="workflow_mode == initial_scan OR workflow_mode == full_rescan">
   <ask>Choose your scan depth level:
 
-**1. Quick Scan** [DEFAULT]
+**1. Quick Scan** (2-5 minutes) [DEFAULT]
 
 - Pattern-based analysis without reading source files
 - Scans: Config files, package manifests, directory structure
 - Best for: Quick project overview, initial understanding
 - File reading: Minimal (configs, README, package.json, etc.)
 
-**2. Deep Scan**
+**2. Deep Scan** (10-30 minutes)
 
 - Reads files in critical directories based on project type
 - Scans: All critical paths from documentation requirements
 - Best for: Comprehensive documentation for brownfield PRD
 - File reading: Selective (key files in critical directories)
 
-**3. Exhaustive Scan**
+**3. Exhaustive Scan** (30-120 minutes)
 
 - Reads ALL source files in project
 - Scans: Every source file (excludes node_modules, dist, build)

src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/steps/step-01-clarify-and-route.md

@@ -18,8 +18,8 @@ spec_file: '' # set at runtime before leaving this step
 
 - `{wipFile}` exists? → Offer resume or archive.
 - Active specs (`ready-for-dev`, `in-progress`, `in-review`) in `{implementation_artifacts}`? → List them and HALT. Ask user which to resume (or `[N]` for new).
-  - If `ready-for-dev` or `in-progress` selected: Set `spec_file`, set `execution_mode = "plan-code-review"`, proceed to step 3.
+  - If `ready-for-dev` or `in-progress` selected: Set `spec_file`, set `execution_mode = "plan-code-review"`, skip to step 3.
-  - If `in-review` selected: Set `spec_file`, set `execution_mode = "plan-code-review"`, proceed to step 4.
+  - If `in-review` selected: Set `spec_file`, set `execution_mode = "plan-code-review"`, skip to step 4.
 - Unformatted spec or intent file lacking `status` frontmatter in `{implementation_artifacts}`? → Suggest to the user to treat its contents as the starting intent for this workflow. DO NOT attempt to infer a state and resume it.
 
 ## INSTRUCTIONS

src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/steps/step-04-review.md

@@ -26,8 +26,8 @@ Do NOT `git add` anything — this is read-only inspection.
 
 **Plan-code-review:** Launch three subagents without conversation context. If no sub-agents are available, generate three review prompt files in `{implementation_artifacts}` — one per reviewer role below — and HALT. Ask the human to run each in a separate session (ideally a different LLM) and paste back the findings.
 
-- **Blind hunter** — receives `{diff_output}` only. No spec, no context docs, no project access. Invoke the `bmad-review-adversarial-general` skill.
+- **Blind hunter** — receives `{diff_output}` only. No spec, no context docs, no project access. Invoke via the `bmad-review-adversarial-general` skill.
-- **Edge case hunter** — receives `{diff_output}` and read access to the project. Invoke the `bmad-review-edge-case-hunter` skill.
+- **Edge case hunter** — receives `{diff_output}` and read access to the project. Invoke via the `bmad-review-edge-case-hunter` skill.
 - **Acceptance auditor** — receives `{diff_output}`, `{spec_file}`, and read access to the project. Must also read the docs listed in `{spec_file}` frontmatter `context`. Checks for violations of acceptance criteria, rules, and principles from the spec and context docs.
 
 ### Classify

src/bmm/workflows/bmad-quick-flow/bmad-quick-spec/steps/step-01-understand.md

@@ -86,7 +86,7 @@ d) **Build mental model:**
 - What's the likely scope based on what you found?
 - What questions do you NOW have, informed by the code?
 
-**Just enough to ask smart questions.**
+**This scan should take < 30 seconds. Just enough to ask smart questions.**
 
 ### 3. Ask Informed Questions
 

src/core/skills/bmad-brainstorming/steps/step-02a-user-selected.md

@@ -102,19 +102,19 @@ After user selects category:
 **Present 3-5 techniques from selected category:**
 For each technique:
 
-- **Technique Name**
+- **Technique Name** (Duration: [time], Energy: [level])
 - Description: [Brief clear description]
 - Best for: [What this technique excels at]
 - Example prompt: [Sample facilitation prompt]
 
 **Example presentation format:**
-"**1. SCAMPER Method**
+"**1. SCAMPER Method** (Duration: 20-30 min, Energy: Moderate)
 
 - Systematic creativity through seven lenses (Substitute/Combine/Adapt/Modify/Put/Eliminate/Reverse)
 - Best for: Product improvement, innovation challenges, systematic idea generation
 - Example prompt: "What could you substitute in your current approach to create something new?"
 
-**2. Six Thinking Hats**
+**2. Six Thinking Hats** (Duration: 15-25 min, Energy: Moderate)
 
 - Explore problems through six distinct perspectives for comprehensive analysis
 - Best for: Complex decisions, team alignment, thorough exploration
@@ -150,7 +150,7 @@ When user selects techniques:
 - [Technique 3]: [If selected, how it builds on others]
 
 **Session Plan:**
-This combination will focus on [expected outcomes].
+This combination will take approximately [total_time] and focus on [expected outcomes].
 
 **Confirm these choices?**
 [C] Continue - Begin technique execution

src/core/skills/bmad-brainstorming/steps/step-02b-ai-recommended.md

@@ -76,6 +76,12 @@ Analyze user's session context across multiple dimensions:
 - User language playful → creative, theatrical, wild techniques
 - User language reflective → introspective_delight, deep techniques
 
+**4. Time Available:**
+
+- <30 min → 1-2 focused techniques
+- 30-60 min → 2-3 complementary techniques
+- > 60 min → Multi-phase technique flow
+
 ### 3. Generate Technique Recommendations
 
 Based on context analysis, create tailored recommendations:
@@ -85,20 +91,24 @@ Based on context analysis, create tailored recommendations:
 Based on your session context, I recommend this customized technique sequence:
 
 **Phase 1: Foundation Setting**
-**[Technique Name]** from [Category]
+**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
+
 - **Why this fits:** [Specific connection to user's goals/context]
 - **Expected outcome:** [What this will accomplish for their session]
 
 **Phase 2: Idea Generation**
-**[Technique Name]** from [Category]
+**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
+
 - **Why this builds on Phase 1:** [Complementary effect explanation]
 - **Expected outcome:** [How this develops the foundation]
 
 **Phase 3: Refinement & Action** (If time allows)
-**[Technique Name]** from [Category]
+**[Technique Name]** from [Category] (Duration: [time], Energy: [level])
+
 - **Why this concludes effectively:** [Final phase rationale]
 - **Expected outcome:** [How this leads to actionable results]
 
+**Total Estimated Time:** [Sum of durations]
 **Session Focus:** [Primary benefit and outcome description]"
 
 ### 4. Present Recommendation Details

src/core/skills/bmad-brainstorming/steps/step-02c-random-selection.md

@@ -74,23 +74,27 @@ Reveal the randomly selected techniques with enthusiasm:
 "**🎲 Your Randomly Selected Creative Techniques! 🎲**
 
 **Phase 1: Exploration**
-**[Random Technique 1]** from [Category]
+**[Random Technique 1]** from [Category] (Duration: [time], Energy: [level])
+
 - **Description:** [Technique description]
 - **Why this is exciting:** [What makes this technique surprising or powerful]
 - **Random discovery bonus:** [Unexpected insight about this technique]
 
 **Phase 2: Connection**
-**[Random Technique 2]** from [Category]
+**[Random Technique 2]** from [Category] (Duration: [time], Energy: [level])
+
 - **Description:** [Technique description]
 - **Why this complements the first:** [How these techniques might work together]
 - **Random discovery bonus:** [Unexpected insight about this combination]
 
 **Phase 3: Synthesis**
-**[Random Technique 3]** from [Category]
+**[Random Technique 3]** from [Category] (Duration: [time], Energy: [level])
+
 - **Description:** [Technique description]
 - **Why this completes the journey:** [How this ties the sequence together]
 - **Random discovery bonus:** [Unexpected insight about the overall flow]
 
+**Total Random Session Time:** [Combined duration]
 **Serendipity Factor:** [Enthusiastic description of creative potential]"
 
 ### 4. Highlight the Creative Potential

src/core/skills/bmad-brainstorming/steps/step-02d-progressive-flow.md

@@ -128,9 +128,10 @@ Show the full progressive flow with timing and transitions:
 
 "**Your Complete Creative Journey Map:**
 
+**⏰ Total Journey Time:** [Combined duration]
 **🎯 Session Focus:** Systematic development from ideas to action
 
-**Phase 1: Expansive Exploration**
+**Phase 1: Expansive Exploration** ([duration])
 
 - **Technique:** [Selected technique]
 - **Goal:** Generate [number]+ diverse ideas without limits
@@ -138,7 +139,7 @@ Show the full progressive flow with timing and transitions:
 
 **→ Phase Transition:** We'll review and cluster ideas before moving deeper
 
-**Phase 2: Pattern Recognition**
+**Phase 2: Pattern Recognition** ([duration])
 
 - **Technique:** [Selected technique]
 - **Goal:** Identify themes and prioritize most promising directions
@@ -146,7 +147,7 @@ Show the full progressive flow with timing and transitions:
 
 **→ Phase Transition:** Select top concepts for detailed development
 
-**Phase 3: Idea Development**
+**Phase 3: Idea Development** ([duration])
 
 - **Technique:** [Selected technique]
 - **Goal:** Refine priority ideas with depth and practicality
@@ -154,7 +155,7 @@ Show the full progressive flow with timing and transitions:
 
 **→ Phase Transition:** Choose final concepts for implementation planning
 
-**Phase 4: Action Planning**
+**Phase 4: Action Planning** ([duration])
 
 - **Technique:** [Selected technique]
 - **Goal:** Create concrete implementation plans and next steps

src/core/skills/bmad-brainstorming/steps/step-03-technique-execution.md

@@ -12,7 +12,7 @@
 - 🧠 **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?"
 - 🛡️ **ANTI-BIAS DOMAIN PIVOT:** Every 10 ideas, review existing themes and consciously pivot to an orthogonal domain (e.g., UX -> Business -> Physics -> Social Impact).
 - 🌡️ **SIMULATED TEMPERATURE:** Act as if your creativity is set to 0.85 - take wilder leaps and suggest "provocative" concepts.
-- ⏱️ Generate at least 100 ideas in active ideation before offering to conclude
+- ⏱️ Spend minimum 30-45 minutes in active ideation before offering to conclude
 - 🎯 EXECUTE ONE TECHNIQUE ELEMENT AT A TIME with interactive exploration
 - 📋 RESPOND DYNAMICALLY to user insights and build upon their ideas
 - 🔍 ADAPT FACILITATION based on user engagement and emerging directions
@@ -176,7 +176,7 @@ Remember: The goal is quantity first - we can organize later. What feels right?"
 **IMPORTANT:** Default to continuing exploration. Only suggest organization if:
 
 - User has explicitly asked to wrap up, OR
-- You've generated 100+ ideas, OR
+- You've been exploring for 45+ minutes AND generated 100+ ideas, OR
 - User's energy is clearly depleted (short responses, "I don't know", etc.)
 
 ### 4a. Handle Immediate Technique Transition