all workflows aware

2025-12-29 16:14:59 +00:00 · 2025-10-12 22:19:28 -05:00
parent 88989d5403
commit 36bf506241
18 changed files with 1488 additions and 68 deletions
--- a/src/modules/bmm/workflows/3-solutioning/instructions.md
+++ b/src/modules/bmm/workflows/3-solutioning/instructions.md
@@ -7,10 +7,55 @@ This workflow generates scale-adaptive solution architecture documentation that

 <step n="0" goal="Load project analysis, validate prerequisites, and scale assessment">
 <action>
-1. Read project-workflow-status.md:
-   Path: {{project_workflow_analysis_path}}
+1. Search {output_folder}/ for files matching pattern: project-workflow-status*.md
+   Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)

-2. Extract:
+2. Check if status file exists:
+   <check if="exists">
+     <action>Load the status file</action>
+     <action>Set status_file_found = true</action>
+     <action>Store status_file_path for later updates</action>
+
+     <action>Validate workflow sequence:</action>
+     <check if='next_step != "solution-architecture" AND current_step not in ["plan-project", "workflow-status"]'>
+       <ask>**⚠️ Workflow Sequence Note**
+
+Status file shows:
+- Current step: {{current_step}}
+- Expected next: {{next_step}}
+
+This workflow (solution-architecture) is typically run after plan-project for Level 3-4 projects.
+
+Options:
+1. Continue anyway (if you're resuming work)
+2. Exit and run the expected workflow: {{next_step}}
+3. Check status with workflow-status
+
+What would you like to do?</ask>
+       <action>If user chooses exit → HALT with message: "Run workflow-status to see current state"</action>
+     </check>
+   </check>
+
+   <check if="not exists">
+     <ask>**No workflow status file found.**
+
+The status file tracks progress across all workflows and stores project configuration.
+
+Options:
+1. Run workflow-status first to create the status file (recommended)
+2. Continue in standalone mode (no progress tracking)
+3. Exit
+
+What would you like to do?</ask>
+     <action>If user chooses option 1 → HALT with message: "Please run workflow-status first, then return to solution-architecture"</action>
+     <action>If user chooses option 2 → Set standalone_mode = true and continue</action>
+     <action>If user chooses option 3 → HALT</action>
+   </check>
+
+3. Extract project configuration from status file:
+   Path: {{status_file_path}}
+
+   Extract:
   - project_level: {{0|1|2|3|4}}
   - field_type: {{greenfield|brownfield}}
   - project_type: {{web|mobile|embedded|game|library}}
@@ -19,7 +64,7 @@ This workflow generates scale-adaptive solution architecture documentation that
   - ux_spec_path: /docs/ux-spec.md (if exists)
   - prd_status: {{complete|incomplete}}

-3. Validate Prerequisites (BLOCKING):
+4. Validate Prerequisites (BLOCKING):

   Check 1: PRD complete?
   IF prd_status != complete:
@@ -67,7 +112,7 @@ This workflow generates scale-adaptive solution architecture documentation that
     - UX Spec: {{complete | not_applicable}}
     Proceeding with solution architecture workflow...

-4. Determine workflow path:
+5. Determine workflow path:
   IF project_level == 0:
     - Skip solution architecture entirely
     - Output: "Level 0 project - validate/update tech-spec.md only"
@@ -745,6 +790,86 @@ Would you like to proceed with story drafting now? (y/n)
 </ask>
 </step>

+<step n="12" goal="Update status file on completion">
+<action>
+Search {output_folder}/ for files matching pattern: project-workflow-status*.md
+Find the most recent file (by date in filename)
+</action>
+
+<check if="status file exists">
+<action>Load the status file</action>
+
+<template-output file="{{status_file_path}}">current_step</template-output>
+<action>Set to: "solution-architecture"</action>
+
+<template-output file="{{status_file_path}}">current_workflow</template-output>
+<action>Set to: "solution-architecture - Complete"</action>
+
+<template-output file="{{status_file_path}}">progress_percentage</template-output>
+<action>Increment by: 15% (solution-architecture is a major workflow)</action>
+
+<template-output file="{{status_file_path}}">decisions_log</template-output>
+<action>Add entry:</action>
+```
+
+- **{{date}}**: Completed solution-architecture workflow. Generated solution-architecture.md, cohesion-check-report.md, and {{epic_count}} tech-spec files. Populated story backlog with {{total_story_count}} stories. Phase 3 complete. Next: SM agent should run create-story to draft first story ({{first_story_id}}).
+
+```
+
+<template-output file="{{status_file_path}}">next_action</template-output>
+<action>Set to: "Draft first user story ({{first_story_id}})"</action>
+
+<template-output file="{{status_file_path}}">next_command</template-output>
+<action>Set to: "Load SM agent and run 'create-story' workflow"</action>
+
+<template-output file="{{status_file_path}}">next_agent</template-output>
+<action>Set to: "bmad/bmm/agents/sm.md"</action>
+
+<output>**✅ Solution Architecture Complete**
+
+**Architecture Documents:**
+- solution-architecture.md (main architecture document)
+- cohesion-check-report.md (validation report)
+- tech-spec-epic-1.md through tech-spec-epic-{{epic_count}}.md ({{epic_count}} specs)
+
+**Story Backlog:**
+- {{total_story_count}} stories populated in status file
+- First story: {{first_story_id}} ({{first_story_title}})
+
+**Status file updated:**
+- Current step: solution-architecture ✓
+- Progress: {{new_progress_percentage}}%
+- Phase 3 (Solutioning) complete
+- Ready for Phase 4 (Implementation)
+
+**Next Steps:**
+1. Load SM agent (bmad/bmm/agents/sm.md)
+2. Run `create-story` workflow to draft story {{first_story_id}}
+3. Review drafted story
+4. Run `story-ready` to approve for development
+
+Check status anytime with: `workflow-status`
+</output>
+</check>
+
+<check if="status file not found">
+<output>**✅ Solution Architecture Complete**
+
+**Architecture Documents:**
+- solution-architecture.md
+- cohesion-check-report.md
+- tech-spec-epic-1.md through tech-spec-epic-{{epic_count}}.md
+
+Note: Running in standalone mode (no status file).
+
+To track progress across workflows, run `workflow-status` first.
+
+**Next Steps:**
+1. Load SM agent and run `create-story` to draft stories
+</output>
+</check>
+</step>
+
 </workflow>
 ```

--- a/src/modules/bmm/workflows/3-solutioning/tech-spec/instructions.md
+++ b/src/modules/bmm/workflows/3-solutioning/tech-spec/instructions.md
@@ -1,13 +1,66 @@
 <!-- BMAD BMM Tech Spec Workflow Instructions (v6) -->

-```xml
+````xml
 <critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>This workflow generates a comprehensive Technical Specification from PRD and Architecture, including detailed design, NFRs, acceptance criteria, and traceability mapping.</critical>
 <critical>Default execution mode: #yolo (non-interactive). If required inputs cannot be auto-discovered and {{non_interactive}} == true, HALT with a clear message listing missing documents; do not prompt.</critical>

 <workflow>
-  <step n="1" goal="Collect inputs and initialize">
+  <step n="1" goal="Check and load workflow status file">
+    <action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
+    <action>Find the most recent file (by date in filename: project-workflow-status-YYYY-MM-DD.md)</action>
+
+    <check if="exists">
+      <action>Load the status file</action>
+      <action>Extract key information:</action>
+      - current_step: What workflow was last run
+      - next_step: What workflow should run next
+      - planned_workflow: The complete workflow journey table
+      - progress_percentage: Current progress
+      - project_level: Project complexity level (0-4)
+
+      <action>Set status_file_found = true</action>
+      <action>Store status_file_path for later updates</action>
+
+      <check if="project_level < 3">
+        <ask>**⚠️ Project Level Notice**
+
+Status file shows project_level = {{project_level}}.
+
+Tech-spec workflow is typically only needed for Level 3-4 projects.
+For Level 0-2, solution-architecture usually generates tech specs automatically.
+
+Options:
+1. Continue anyway (manual tech spec generation)
+2. Exit (check if solution-architecture already generated tech specs)
+3. Run workflow-status to verify project configuration
+
+What would you like to do?</ask>
+        <action>If user chooses exit → HALT with message: "Check docs/ folder for existing tech-spec files"</action>
+      </check>
+    </check>
+
+    <check if="not exists">
+      <ask>**No workflow status file found.**
+
+The status file tracks progress across all workflows and stores project configuration.
+
+Note: This workflow is typically invoked automatically by solution-architecture, or manually for JIT epic tech specs.
+
+Options:
+1. Run workflow-status first to create the status file (recommended)
+2. Continue in standalone mode (no progress tracking)
+3. Exit
+
+What would you like to do?</ask>
+      <action>If user chooses option 1 → HALT with message: "Please run workflow-status first, then return to tech-spec"</action>
+      <action>If user chooses option 2 → Set standalone_mode = true and continue</action>
+      <action>If user chooses option 3 → HALT</action>
+    </check>
+  </step>
+
+  <step n="2" goal="Collect inputs and initialize">
    <action>Identify PRD and Architecture documents from recommended_inputs. Attempt to auto-discover at default paths.</action>
    <ask optional="true" if="{{non_interactive}} == false">If inputs are missing, ask the user for file paths.</ask>

@@ -17,7 +70,7 @@
    <action>Resolve output file path using workflow variables and initialize by writing the template.</action>
  </step>

-  <step n="2" goal="Overview and scope">
+  <step n="3" goal="Overview and scope">
    <action>Read COMPLETE PRD and Architecture files.</action>
    <template-output file="{default_output_file}">
      Replace {{overview}} with a concise 1-2 paragraph summary referencing PRD context and goals
@@ -26,7 +79,7 @@
    </template-output>
  </step>

-  <step n="3" goal="Detailed design">
+  <step n="4" goal="Detailed design">
    <action>Derive concrete implementation specifics from Architecture and PRD (NO invention).</action>
    <template-output file="{default_output_file}">
      Replace {{services_modules}} with a table or bullets listing services/modules with responsibilities, inputs/outputs, and owners
@@ -36,7 +89,7 @@
    </template-output>
  </step>

-  <step n="4" goal="Non-functional requirements">
+  <step n="5" goal="Non-functional requirements">
    <template-output file="{default_output_file}">
      Replace {{nfr_performance}} with measurable targets (latency, throughput); link to any performance requirements in PRD/Architecture
      Replace {{nfr_security}} with authn/z requirements, data handling, threat notes; cite source sections
@@ -45,14 +98,14 @@
    </template-output>
  </step>

-  <step n="5" goal="Dependencies and integrations">
+  <step n="6" goal="Dependencies and integrations">
    <action>Scan repository for dependency manifests (e.g., package.json, pyproject.toml, go.mod, Unity Packages/manifest.json).</action>
    <template-output file="{default_output_file}">
      Replace {{dependencies_integrations}} with a structured list of dependencies and integration points with version or commit constraints when known
    </template-output>
  </step>

-  <step n="6" goal="Acceptance criteria and traceability">
+  <step n="7" goal="Acceptance criteria and traceability">
    <action>Extract acceptance criteria from PRD; normalize into atomic, testable statements.</action>
    <template-output file="{default_output_file}">
      Replace {{acceptance_criteria}} with a numbered list of testable acceptance criteria
@@ -60,16 +113,80 @@
    </template-output>
  </step>

-  <step n="7" goal="Risks and test strategy">
+  <step n="8" goal="Risks and test strategy">
    <template-output file="{default_output_file}">
      Replace {{risks_assumptions_questions}} with explicit list (each item labeled as Risk/Assumption/Question) with mitigation or next step
      Replace {{test_strategy}} with a brief plan (test levels, frameworks, coverage of ACs, edge cases)
    </template-output>
  </step>

-  <step n="8" goal="Validate">
+  <step n="9" goal="Validate">
    <invoke-task>Validate against checklist at {installed_path}/checklist.md using bmad/core/tasks/validate-workflow.xml</invoke-task>
  </step>

+  <step n="10" goal="Update status file on completion">
+    <action>Search {output_folder}/ for files matching pattern: project-workflow-status*.md</action>
+    <action>Find the most recent file (by date in filename)</action>
+
+    <check if="status file exists">
+      <action>Load the status file</action>
+
+      <template-output file="{{status_file_path}}">current_step</template-output>
+      <action>Set to: "tech-spec (Epic {{epic_id}})"</action>
+
+      <template-output file="{{status_file_path}}">current_workflow</template-output>
+      <action>Set to: "tech-spec (Epic {{epic_id}}: {{epic_title}}) - Complete"</action>
+
+      <template-output file="{{status_file_path}}">progress_percentage</template-output>
+      <action>Increment by: 5% (tech-spec generates one epic spec)</action>
+
+      <template-output file="{{status_file_path}}">decisions_log</template-output>
+      <action>Add entry:</action>
+      ```
+      - **{{date}}**: Completed tech-spec for Epic {{epic_id}} ({{epic_title}}). Tech spec file: {{default_output_file}}. This is a JIT workflow that can be run multiple times for different epics. Next: Continue with remaining epics or proceed to Phase 4 implementation.
+      ```
+
+      <template-output file="{{status_file_path}}">planned_workflow</template-output>
+      <action>Mark "tech-spec (Epic {{epic_id}})" as complete in the planned workflow table</action>
+
+      <output>**✅ Tech Spec Generated Successfully**
+
+**Epic Details:**
+- Epic ID: {{epic_id}}
+- Epic Title: {{epic_title}}
+- Tech Spec File: {{default_output_file}}
+
+**Status file updated:**
+- Current step: tech-spec (Epic {{epic_id}}) ✓
+- Progress: {{new_progress_percentage}}%
+
+**Note:** This is a JIT (Just-In-Time) workflow.
+- Run again for other epics that need detailed tech specs
+- Or proceed to Phase 4 (Implementation) if all tech specs are complete
+
+**Next Steps:**
+1. If more epics need tech specs: Run tech-spec again with different epic_id
+2. If all tech specs complete: Proceed to Phase 4 implementation
+3. Check status anytime with: `workflow-status`
+      </output>
+    </check>
+
+    <check if="status file not found">
+      <output>**✅ Tech Spec Generated Successfully**
+
+**Epic Details:**
+- Epic ID: {{epic_id}}
+- Epic Title: {{epic_title}}
+- Tech Spec File: {{default_output_file}}
+
+Note: Running in standalone mode (no status file).
+
+To track progress across workflows, run `workflow-status` first.
+
+**Note:** This is a JIT workflow - run again for other epics as needed.
+      </output>
+    </check>
+  </step>
+
 </workflow>
-```
+````