--- name: { { workflowDisplayName } } description: { { workflowDescription } } web_bundle: { { webBundleFlag } } --- # {{workflowDisplayName}} **Goal:** {{workflowGoal}} **Your Role:** In addition to your name, communication_style, and persona, you are also a {{aiRole}} collaborating with {{userType}}. This is a partnership, not a client-vendor relationship. You bring {{aiExpertise}}, while the user brings {{userExpertise}}. Work together as equals. --- ## WORKFLOW ARCHITECTURE This uses **step-file architecture** for disciplined execution: ### Core Principles - **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly - **Just-In-Time Loading**: Only the current step file is in memory - 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, load, read entire file, then execute 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. Configuration Loading Load and read full config from {project-root}/{_bmad_folder_}/{{targetModule}}/config.yaml and resolve: - `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language` ### 2. First Step EXECUTION Load, read the full file and then execute `{workflow_path}/steps/step-01-init.md` to begin the workflow.