@devo-bmad-custom/agent-orchestration 1.0.2 → 1.0.3

package/src/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-06-final-assessment.md

@@ -1,129 +1,129 @@
----
-name: 'step-06-final-assessment'
-description: 'Compile final assessment and polish the readiness report'
-
-outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
----
-
-# Step 6: Final Assessment
-
-## STEP GOAL:
-
-To provide a comprehensive summary of all findings and give the report a final polish, ensuring clear recommendations and overall readiness status.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 📖 You are at the final step - complete the assessment
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are delivering the FINAL ASSESSMENT
-- ✅ Your findings are objective and backed by evidence
-- ✅ Provide clear, actionable recommendations
-- ✅ Success is measured by value of findings
-
-### Step-Specific Rules:
-
-- 🎯 Compile and summarize all findings
-- 🚫 Don't soften the message - be direct
-- 💬 Provide specific examples for problems
-- 🚪 Add final section to the report
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Review all findings from previous steps
-- 💾 Add summary and recommendations
-- 📖 Determine overall readiness status
-- 🚫 Complete and present final report
-
-## FINAL ASSESSMENT PROCESS:
-
-### 1. Initialize Final Assessment
-
-"Completing **Final Assessment**.
-
-I will now:
-
-1. Review all findings from previous steps
-2. Provide a comprehensive summary
-3. Add specific recommendations
-4. Determine overall readiness status"
-
-### 2. Review Previous Findings
-
-Check the {outputFile} for sections added by previous steps:
-
-- File and FR Validation findings
-- UX Alignment issues
-- Epic Quality violations
-
-### 3. Add Final Assessment Section
-
-Append to {outputFile}:
-
-```markdown
-## Summary and Recommendations
-
-### Overall Readiness Status
-
-[READY/NEEDS WORK/NOT READY]
-
-### Critical Issues Requiring Immediate Action
-
-[List most critical issues that must be addressed]
-
-### Recommended Next Steps
-
-1. [Specific action item 1]
-2. [Specific action item 2]
-3. [Specific action item 3]
-
-### Final Note
-
-This assessment identified [X] issues across [Y] categories. Address the critical issues before proceeding to implementation. These findings can be used to improve the artifacts or you may choose to proceed as-is.
-```
-
-### 4. Complete the Report
-
-- Ensure all findings are clearly documented
-- Verify recommendations are actionable
-- Add date and assessor information
-- Save the final report
-
-### 5. Present Completion
-
-Display:
-"**Implementation Readiness Assessment Complete**
-
-Report generated: {outputFile}
-
-The assessment found [number] issues requiring attention. Review the detailed report for specific findings and recommendations."
-
-## WORKFLOW COMPLETE
-
-The implementation readiness workflow is now complete. The report contains all findings and recommendations for the user to consider.
-
-Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All findings compiled and summarized
-- Clear recommendations provided
-- Readiness status determined
-- Final report saved
-
-### ❌ SYSTEM FAILURE:
-
-- Not reviewing previous findings
-- Incomplete summary
-- No clear recommendations
+---
+name: 'step-06-final-assessment'
+description: 'Compile final assessment and polish the readiness report'
+
+outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
+---
+
+# Step 6: Final Assessment
+
+## STEP GOAL:
+
+To provide a comprehensive summary of all findings and give the report a final polish, ensuring clear recommendations and overall readiness status.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 📖 You are at the final step - complete the assessment
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are delivering the FINAL ASSESSMENT
+- ✅ Your findings are objective and backed by evidence
+- ✅ Provide clear, actionable recommendations
+- ✅ Success is measured by value of findings
+
+### Step-Specific Rules:
+
+- 🎯 Compile and summarize all findings
+- 🚫 Don't soften the message - be direct
+- 💬 Provide specific examples for problems
+- 🚪 Add final section to the report
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Review all findings from previous steps
+- 💾 Add summary and recommendations
+- 📖 Determine overall readiness status
+- 🚫 Complete and present final report
+
+## FINAL ASSESSMENT PROCESS:
+
+### 1. Initialize Final Assessment
+
+"Completing **Final Assessment**.
+
+I will now:
+
+1. Review all findings from previous steps
+2. Provide a comprehensive summary
+3. Add specific recommendations
+4. Determine overall readiness status"
+
+### 2. Review Previous Findings
+
+Check the {outputFile} for sections added by previous steps:
+
+- File and FR Validation findings
+- UX Alignment issues
+- Epic Quality violations
+
+### 3. Add Final Assessment Section
+
+Append to {outputFile}:
+
+```markdown
+## Summary and Recommendations
+
+### Overall Readiness Status
+
+[READY/NEEDS WORK/NOT READY]
+
+### Critical Issues Requiring Immediate Action
+
+[List most critical issues that must be addressed]
+
+### Recommended Next Steps
+
+1. [Specific action item 1]
+2. [Specific action item 2]
+3. [Specific action item 3]
+
+### Final Note
+
+This assessment identified [X] issues across [Y] categories. Address the critical issues before proceeding to implementation. These findings can be used to improve the artifacts or you may choose to proceed as-is.
+```
+
+### 4. Complete the Report
+
+- Ensure all findings are clearly documented
+- Verify recommendations are actionable
+- Add date and assessor information
+- Save the final report
+
+### 5. Present Completion
+
+Display:
+"**Implementation Readiness Assessment Complete**
+
+Report generated: {outputFile}
+
+The assessment found [number] issues requiring attention. Review the detailed report for specific findings and recommendations."
+
+## WORKFLOW COMPLETE
+
+The implementation readiness workflow is now complete. The report contains all findings and recommendations for the user to consider.
+
+Implementation Readiness complete. Read fully and follow: `{project-root}/_bmad/core/tasks/help.md`
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- All findings compiled and summarized
+- Clear recommendations provided
+- Readiness status determined
+- Final report saved
+
+### ❌ SYSTEM FAILURE:
+
+- Not reviewing previous findings
+- Incomplete summary
+- No clear recommendations

package/src/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md

@@ -1,54 +1,54 @@
----
-name: check-implementation-readiness
-description: 'Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".'
----
-
-# Implementation Readiness
-
-**Goal:** Validate that PRD, Architecture, Epics and Stories are complete and aligned before Phase 4 implementation starts, with a focus on ensuring epics and stories are logical and have accounted for all requirements and planning.
-
-**Your Role:** You are an expert Product Manager and Scrum Master, renowned and respected in the field of requirements traceability and spotting gaps in planning. Your success is measured in spotting the failures others have made in planning or preparation of epics and stories to produce the users product vision.
-
-## WORKFLOW ARCHITECTURE
-
-### Core Principles
-
-- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
-- **Just-In-Time Loading**: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
-- **Append-Only Building**: Build documents by appending content as directed to the output file
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, read fully and follow the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Module Configuration Loading
-
-Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### 2. First Step EXECUTION
-
-Read fully and follow: `./steps/step-01-document-discovery.md` to begin the workflow.
+---
+name: check-implementation-readiness
+description: 'Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".'
+---
+
+# Implementation Readiness
+
+**Goal:** Validate that PRD, Architecture, Epics and Stories are complete and aligned before Phase 4 implementation starts, with a focus on ensuring epics and stories are logical and have accounted for all requirements and planning.
+
+**Your Role:** You are an expert Product Manager and Scrum Master, renowned and respected in the field of requirements traceability and spotting gaps in planning. Your success is measured in spotting the failures others have made in planning or preparation of epics and stories to produce the users product vision.
+
+## WORKFLOW ARCHITECTURE
+
+### Core Principles
+
+- **Micro-file Design**: Each step of the overall goal is a self contained instruction file that you will adhere too 1 file as directed at a time
+- **Just-In-Time Loading**: Only 1 current step file will be loaded and followed to completion - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Module Configuration Loading
+
+Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 2. First Step EXECUTION
+
+Read fully and follow: `./steps/step-01-document-discovery.md` to begin the workflow.

package/src/bmm/workflows/3-solutioning/create-architecture/steps/step-01b-continue.md

@@ -1,82 +1,82 @@
-# Step 1b: Workflow Continuation Handler
-
-**Goal:** Handle workflow continuation by analyzing existing work and guiding the user to resume at the appropriate step.
-
-**Rules:** Read this entire file before acting. Maintain all existing document content — do not overwrite. Get user confirmation before navigating to any step.
-
-- AUTONOMY OVERRIDE: If you have enough context to answer any discovery questions yourself, DO NOT ask the user. Make expert assumptions, generate the content, display it, and immediately proceed to {nextStepFile} without halting.
----
-
-## CONTINUATION SEQUENCE
-
-### 1. Analyze Current Document State
-
-Read the existing architecture document completely.
-
-**Frontmatter analysis:** `stepsCompleted`, `inputDocuments`, `lastStep`, project/user context.
-
-**Content analysis:** Which sections exist, what decisions have been made, what appears incomplete or has TODOs/placeholders.
-
-### 2. Present Continuation Summary
-
-"Welcome back {user_name}! I found your Architecture work for {project_name}.
-
-**Current Progress:**
-- Steps completed: {stepsCompleted list}
-- Last step: Step {lastStep}
-- Input documents: {inputDocuments count} files
-
-**Document Sections Found:**
-{list all H2/H3 sections}
-
-{if incomplete sections exist}
-**Incomplete Areas:** {areas with placeholders or TODOs}
-{/if}
-
-**What would you like to do?**
-[R] Resume from where we left off
-[AR] Adversarial Review [PL] Party Mode Loop [AL] Adversarial Review Loop [C] Continue to next logical step
-[O] Overview of all remaining steps
-[X] Start over (will overwrite existing work)"
-
-### 3. Handle User Choice
-
-**R (Resume):** Identify next step from `stepsCompleted`. If `stepsCompleted: [1, 2, 3]`, load step-04. Load the appropriate step file.
-
-**AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings, then redisplay menu.
-
-**C (Continue to next logical step):** Analyze content completeness for the current step. If complete, advance to next; if incomplete, suggest staying. Load the appropriate step file.
-
-**O (Overview):** Describe all remaining steps briefly, let user choose which to work on.
-
-**X (Start over):** Confirm — "This will delete all existing architectural decisions. Are you sure? (y/n)". If yes: delete document and load step-01-init. If no: return to this menu.
-
-### 4. Navigate to Selected Step
-
-- Update frontmatter `lastStep` before loading
-- Load the selected step file
-
-**Valid step files:**
-- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md`
-- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md`
-- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md`
-- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md`
-- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md`
-- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md`
-- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md`
-
-### 5. Special Cases
-
-- **`stepsCompleted` empty but document has content:** Ask user if they want to set the appropriate step status based on what's there.
-- **Document appears corrupted:** "Would you like me to try to recover what's here, or start fresh?"
-- **Document appears complete but not marked done:** "The architecture looks complete! Should I mark this workflow as finished, or is there more to work on?"
-
----
-
-## SUCCESS METRICS
-
-- Existing document state properly analyzed
-- User presented with clear continuation options
-- User choice handled appropriately
-- Workflow state preserved and updated
-- Navigation to appropriate step handled smoothly
+# Step 1b: Workflow Continuation Handler
+
+**Goal:** Handle workflow continuation by analyzing existing work and guiding the user to resume at the appropriate step.
+
+**Rules:** Read this entire file before acting. Maintain all existing document content — do not overwrite. Get user confirmation before navigating to any step.
+
+- AUTONOMY OVERRIDE: If you have enough context to answer any discovery questions yourself, DO NOT ask the user. Make expert assumptions, generate the content, display it, and immediately proceed to {nextStepFile} without halting.
+---
+
+## CONTINUATION SEQUENCE
+
+### 1. Analyze Current Document State
+
+Read the existing architecture document completely.
+
+**Frontmatter analysis:** `stepsCompleted`, `inputDocuments`, `lastStep`, project/user context.
+
+**Content analysis:** Which sections exist, what decisions have been made, what appears incomplete or has TODOs/placeholders.
+
+### 2. Present Continuation Summary
+
+"Welcome back {user_name}! I found your Architecture work for {project_name}.
+
+**Current Progress:**
+- Steps completed: {stepsCompleted list}
+- Last step: Step {lastStep}
+- Input documents: {inputDocuments count} files
+
+**Document Sections Found:**
+{list all H2/H3 sections}
+
+{if incomplete sections exist}
+**Incomplete Areas:** {areas with placeholders or TODOs}
+{/if}
+
+**What would you like to do?**
+[R] Resume from where we left off
+[AR] Adversarial Review [PL] Party Mode Loop [AL] Adversarial Review Loop [C] Continue to next logical step
+[O] Overview of all remaining steps
+[X] Start over (will overwrite existing work)"
+
+### 3. Handle User Choice
+
+**R (Resume):** Identify next step from `stepsCompleted`. If `stepsCompleted: [1, 2, 3]`, load step-04. Load the appropriate step file.
+
+**AR:** Execute `{project-root}/_bmad/core/tasks/review-adversarial-general.xml` — display findings, then redisplay menu.
+
+**C (Continue to next logical step):** Analyze content completeness for the current step. If complete, advance to next; if incomplete, suggest staying. Load the appropriate step file.
+
+**O (Overview):** Describe all remaining steps briefly, let user choose which to work on.
+
+**X (Start over):** Confirm — "This will delete all existing architectural decisions. Are you sure? (y/n)". If yes: delete document and load step-01-init. If no: return to this menu.
+
+### 4. Navigate to Selected Step
+
+- Update frontmatter `lastStep` before loading
+- Load the selected step file
+
+**Valid step files:**
+- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-02-context.md`
+- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-03-starter.md`
+- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-04-decisions.md`
+- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-05-patterns.md`
+- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-06-structure.md`
+- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-07-validation.md`
+- `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md`
+
+### 5. Special Cases
+
+- **`stepsCompleted` empty but document has content:** Ask user if they want to set the appropriate step status based on what's there.
+- **Document appears corrupted:** "Would you like me to try to recover what's here, or start fresh?"
+- **Document appears complete but not marked done:** "The architecture looks complete! Should I mark this workflow as finished, or is there more to work on?"
+
+---
+
+## SUCCESS METRICS
+
+- Existing document state properly analyzed
+- User presented with clear continuation options
+- User choice handled appropriately
+- Workflow state preserved and updated
+- Navigation to appropriate step handled smoothly