@delorenj/pjangler 1.2.25 → 1.3.0

package/templates/commonproject/_bmad/bmb/workflows/workflow/data/workflow-examples.md

@@ -1,276 +0,0 @@
-# Novel Workflow Examples
-
-**Purpose:** Illustrative examples of workflows across diverse domains to demonstrate the range of what users can create.
-
----
-
-## Understanding Workflow Structure
-
-**Each arrow (→) in the "Flow" column represents a potential step file.**
-
-```
-Flow: Discovery → Assessment → Strategy → Shopping List → Prep Schedule
-       ↓           ↓           ↓           ↓              ↓
-       step-01-   step-02-   step-03-    step-04-      step-05-
-    discovery  assessment  strategy  shopping-list  prep-schedule
-```
-
-**Each step file contains internal structure:**
-- STEP GOAL
-- MANDATORY EXECUTION RULES
-- EXECUTION PROTOCOLS
-- MANDATORY SEQUENCE (numbered sub-steps)
-- Menu options
-- Success/failure metrics
-
-**Key insight:** A simple workflow might have 3-4 step files. A complex workflow might have 10+. Each step file is a focused, self-contained instruction.
-
----
-
-## Example 1: Personalized Meal Plan Generator
-
-**Domain:** Health & Fitness
-
-| Aspect | Details |
-|--------|---------|
-| **Flow** (each → = step file) | Discovery → Assessment → Strategy → Shopping List → Prep Schedule |
-| **Step Files** | ~5 files: step-01-discovery, step-02-assessment, step-03-strategy, step-04-shopping, step-05-prep |
-| **Output** | Direct-to-final document, each step appends a section |
-| **Intent/Prescriptive** | Intent-based - Facilitates discovery of preferences |
-| **Planning** | No - builds final meal plan directly |
-| **Continuable** | Yes - Can be 200+ tokens, users may need multiple sessions |
-| **Structure** | Linear, 5 steps, no branching |
-| **Conversation** | Open-ended with progressive questioning (1-2 at a time, probe preferences) |
-
-**Description:** Helps users create personalized weekly meal plans based on dietary restrictions, health goals, and cooking habits.
-
----
-
-## Example 2: Year-End Tax Organizer
-
-**Domain:** Finance
-
-| Aspect | Details |
-|--------|---------|
-| **Flow** (each → = step file) | Input Discovery → Document Categorization → Missing Document Alert → Final Summary |
-| **Step Files** | 4 files: step-01-input-discovery, step-02-categorize, step-03-missing-alerts, step-04-summary |
-| **Output** | Analysis-only + checklist of missing docs |
-| **Intent/Prescriptive** | Highly Prescriptive - Tax compliance, exact categories |
-| **Planning** | N/A |
-| **Continuable** | No - Simple single-session checklist |
-| **Structure** | Linear, 4 steps |
-| **Conversation** | Focused - specific questions, document what user provides |
-
-**Description:** Organizes financial documents for tax preparation, categorizes income/deductions, alerts to missing documents.
-
----
-
-## Example 3: Employee Termination Checklist
-
-**Domain:** Legal / HR / Compliance
-
-| Aspect | Details |
-|--------|---------|
-| **Flow** (each → = step file) | Context → Regulatory Check → Document Requirements → Notification Timeline → Final Checklist |
-| **Step Files** | 5 files: step-01-context, step-02-regulatory, step-03-documents, step-04-timeline, step-05-checklist. Some steps branch internally based on reason/location. |
-| **Output** | Direct-to-final compliance checklist |
-| **Intent/Prescriptive** | Highly Prescriptive - Legal compliance, state-specific |
-| **Planning** | No |
-| **Continuable** | No - Focused, single-session |
-| **Structure** | Branching - Different paths within steps based on: reason, location, employee count |
-| **Conversation** | Focused - specific classification questions, present requirements |
-
-**Description:** Generates legally-compliant termination checklists that vary by state, termination reason, and employee count.
-
----
-
-## Example 4: Tabletop RPG Campaign Builder
-
-**Domain:** Entertainment / Games
-
-| Aspect | Details |
-|--------|---------|
-| **Flow** (each → = step file) | Session Concept → NPC Creation → Scene Setup → Key Beats → Generate → [Repeat for next session] |
-| **Step Files** | 4 core files: step-01-concept, step-02-npc, step-03-scene, step-04-beats, step-05-generate. Same files reused each session. |
-| **Output** | Per-session document, maintains campaign continuity |
-| **Intent/Prescriptive** | Intent-based - Creative facilitation |
-| **Planning** | No - Each session builds directly to playable content |
-| **Continuable** | Yes - Campaign has many sessions over months |
-| **Structure** | Repeating loop - Same steps, new content each session |
-| **Conversation** | Open-ended creative facilitation, "What if..." prompts |
-
-**Description:** Helps Game Masters create individual RPG session content while tracking campaign continuity across multiple sessions.
-
----
-
-## Example 5: Course Syllabus Creator
-
-**Domain:** Education
-
-| Aspect | Details |
-|--------|---------|
-| **Flow** | Course Type → Learning Objectives → Module Breakdown → Assessment → [Branch: academic] → Accreditation → [Branch: vocational] → Certification → Final |
-| **Output** | Direct-to-final syllabus document |
-| **Intent/Prescriptive** | Balanced - Framework prescriptive, content flexible |
-| **Planning** | No |
-| **Continuable** | Yes - Complex syllabus may require multiple sessions |
-| **Structure** | Branching - Course type determines different sections |
-| **Conversation** | Mixed - Framework questions (prescriptive) + content discovery (intent) |
-
-**Description:** Creates course syllabi that adapt based on course type (academic, vocational, self-paced) with appropriate accreditation requirements.
-
----
-
-## Example 6: SOP Writer
-
-**Domain:** Business Process
-
-| Aspect | Details |
-|--------|---------|
-| **Flow** | Process Selection → Scope Definition → Documentation → Review → [Generate] → "Create another?" → If yes, repeat |
-| **Output** | Each SOP is independent, stored in `{sop_folder}/` |
-| **Intent/Prescriptive** | Prescriptive - SOPs must be exact, unambiguous |
-| **Planning** | No - Each SOP generated directly |
-| **Continuable** | No - Single SOP per run, but workflow is repeatable |
-| **Structure** | Repeating - Can create multiple SOPs in one session |
-| **Conversation** | Focused on process details - "Walk me through step 1" |
-
-**Description:** Generates Standard Operating Procedure documents for business processes. Can create multiple SOPs in one session, each stored independently.
-
----
-
-## Example 7: Novel Outliner
-
-**Domain:** Creative Writing
-
-| Aspect | Details |
-|--------|---------|
-| **Flow** | Structure Selection → Character Arcs → Beat Breakdown → Pacing Review → Final Polish |
-| **Output** | Free-form with Final Polish step to ensure flow and coherence |
-| **Intent/Prescriptive** | Intent-based - "What does your character want?" |
-| **Planning** | No - Builds outline directly |
-| **Continuable** | Yes - Long-form creative work, sessions span weeks |
-| **Structure** | Branching - Different flows based on structure choice |
-| **Conversation** | Open-ended creative coaching, provocations |
-
-**Description:** Helps authors create novel outlines with proper story structure (3-Act, Hero's Journey, etc.), character arcs, and beat sheets.
-
----
-
-## Example 8: Wedding Itinerary Coordinator
-
-**Domain:** Event Planning
-
-| Aspect | Details |
-|--------|---------|
-| **Flow** | Venue Type → Vendor Coordination → Timeline → Guest Experience → [Branch: hybrid] → Virtual Setup → Day-of Schedule |
-| **Output** | Direct-to-final itinerary |
-| **Intent/Prescriptive** | Intent-based - Facilitates couple's vision |
-| **Planning** | No |
-| **Continuable** | Yes - Wedding planning takes months |
-| **Structure** | Branching - Venue type affects required sections |
-| **Conversation** | Open-ended discovery of preferences, budget, constraints |
-
-**Description:** Creates detailed wedding day itineraries, adapting to venue type (indoor/outdoor/hybrid) and guest experience goals.
-
----
-
-## Example 9: Annual Life Review
-
-**Domain:** Personal Development
-
-| Aspect | Details |
-|--------|---------|
-| **Flow** | Input Discovery (last year's goals) → Life Areas Assessment → Reflections → Goal Setting → Action Planning → Final Polish |
-| **Output** | Free-form with Final Polish, discovers prior review first |
-| **Intent/Prescriptive** | Intent-based - Coaching questions |
-| **Planning** | No - Direct to life plan document |
-| **Continuable** | Yes - Deep reflection may need multiple sessions |
-| **Structure** | Linear with Input Discovery at start |
-| **Conversation** | Open-ended coaching, progressive questioning |
-
-**Description:** Annual review workflow that discovers prior year's goals, facilitates reflection across life areas, and sets intentional goals for coming year.
-
----
-
-## Example 10: Room Renovation Planner
-
-**Domain:** Home Improvement
-
-| Aspect | Details |
-|--------|---------|
-| **Flow** | Room Type → Budget Assessment → Phase Planning → Materials → Contractor Timeline → [Branch: DIY] → Instructions |
-| **Output** | Direct-to-final renovation plan |
-| **Intent/Prescriptive** | Balanced - Code compliance prescriptive, design intent-based |
-| **Planning** | No |
-| **Continuable** | Yes - Complex planning, multi-session |
-| **Structure** | Branching - Room type and DIY vs pro affect content |
-| **Conversation** | Mixed - "What's your budget?" + "Describe your vision" |
-
-**Description:** Creates room-specific renovation plans with material selection, contractor coordination, and optional DIY instructions.
-
----
-
-## Pattern Analysis
-
-### Structure Types
-
-| Type | Count | Examples |
-|------|-------|----------|
-| Linear | 5 | Meal Plan, Tax, Termination, Life Review, Renovation |
-| Branching | 5 | Termination, Syllabus, Novel, Wedding, Renovation |
-| Repeating Loop | 2 | RPG Campaign, SOP Writer |
-
-### Intent Spectrum
-
-| Type | Count | Examples |
-|------|-------|----------|
-| Intent-based | 7 | Meal Plan, RPG Campaign, Syllabus (partial), Novel, Wedding, Life Review, Renovation (partial) |
-| Prescriptive | 1 | Tax, Termination, SOP |
-| Balanced | 2 | Syllabus, Renovation |
-
-### Continuable vs Single-Session
-
-| Type | Count | Examples |
-|------|-------|----------|
-| Continuable | 7 | Meal Plan, RPG Campaign, Syllabus, Novel, Wedding, Life Review, Renovation |
-| Single-Session | 3 | Tax, Termination, SOP (repeatable but single-output) |
-
-### Output Patterns
-
-| Type | Count | Examples |
-|------|-------|----------|
-| Direct-to-Final | 9 | All except Tax |
-| Analysis Only | 1 | Tax |
-| With Final Polish | 1 | Novel |
-| Input Discovery | 1 | Life Review |
-| Repeating Output | 2 | RPG Campaign (sessions), SOP Writer (multiple SOPs) |
-
----
-
-## Key Insights
-
-1. **Continuable workflows are the norm** - 7 of 10 examples are continuable
-2. **Intent-based dominates** - 7 of 10 are primarily intent-based facilitation
-3. **Branching is common** - 5 of 10 have conditional paths based on user choices
-4. **Input discovery matters** - Workflows in sequences (like BMM pipeline) need to find prior documents
-5. **Final polish is critical** - Complex documents built section-by-section need optimization step
-6. **Repeating loops exist** - Some workflows generate multiple outputs per session or repeat across sessions
-7. **Mixed conversation styles** - Most use focused questions for data, open-ended for creative
-
----
-
-## Workflow Design Questions
-
-When creating a new workflow, ask:
-
-1. **Domain:** What problem space does this operate in?
-2. **Output:** What does this workflow produce? (Document, checklist, analysis, physical output?)
-3. **Intent:** Is this prescriptive (compliance) or intent-based (creative)?
-4. **Planning:** Plan-then-build or direct-to-final?
-5. **Continuable:** Could this take multiple sessions or consume many tokens?
-6. **Structure:** Linear, branching, or repeating loop?
-7. **Inputs:** Does this require documents from prior workflows or external sources?
-8. **Chaining:** Is this part of a module sequence? What comes before/after?
-9. **Polish:** Does the final output need optimization for flow and coherence?
-10. **Conversation:** Focused questions or open-ended facilitation?

package/templates/commonproject/_bmad/bmb/workflows/workflow/data/workflow-type-criteria.md

@@ -1,172 +0,0 @@
-# Workflow Type Criteria
-
-**Purpose:** Key decisions when designing a workflow.
-
----
-
-## Key Decisions
-
-1. **Module affiliation** - Standalone or part of a module?
-2. **Continuable** - Can it span multiple sessions?
-3. **Edit/Validate support** - Will it have edit and validate flows?
-4. **Document output** - Does it produce a document?
-
----
-
-## 1. Module Affiliation
-
-### Standalone Workflow
-- NOT part of any module
-- Stored in user's custom location
-- Only standard variables available
-
-### Module-Based Workflow
-- Part of a specific module (e.g., BMB)
-- Has access to module-specific variables
-- Stored in module's workflows directory
-
-**BMB additional variable:** `{bmb_creations_output_folder}`
-
----
-
-## 2. Continuable or Single-Session?
-
-### Continuable (Multi-Session)
-**Use when:** Workflow might consume MASSIVE tokens, complex, many steps
-
-**Required:**
-- `step-01-init.md` with continuation detection
-- `step-01b-continue.md` for resuming
-- `stepsCompleted` tracking in output frontmatter
-
-**Frontmatter:**
-```yaml
-stepsCompleted: ['step-01-init', 'step-02-gather']
-lastStep: 'step-02-gather'
-lastContinued: '2025-01-02'
-```
-
-**Rule:** Each step appends its NAME to `stepsCompleted`
-
-### Single-Session
-**Use when:** Simple, quick (<15 min), token-efficient
-
-**Required:**
-- Standard `step-01-init.md` (no continuation logic)
-- No `stepsCompleted` tracking needed
-
----
-
-## 3. Edit/Validate Support
-
-### Create-Only
-```
-workflow-folder/
-├── workflow.md
-├── data/
-└── steps-c/
-    ├── step-01-init.md
-    └── step-N-final.md
-```
-
-**Use when:** Simple workflows, experimental, one-off
-
-### Create + Edit + Validate (Tri-Modal)
-```
-workflow-folder/
-├── workflow.md
-├── data/                    # SHARED
-├── steps-c/                 # Create
-├── steps-e/                 # Edit
-└── steps-v/                 # Validate
-```
-
-**Key:**
-- Each mode is SELF-CONTAINED
-- NO shared step files between modes
-- DATA folder is SHARED (prevents drift)
-- Duplicative steps OK (better than confusion)
-
-**Use when:** Complex workflows that will be maintained
-
----
-
-## 4. Document Output
-
-### Document-Producing
-- Creates persistent output file
-- Uses templates for structure
-- Each step contributes to document
-- Consider final polish step
-
-### Non-Document
-- Performs actions without persistent output
-- May produce temporary files
-- Focus on execution, not creation
-
----
-
-## Decision Tree
-
-```
-START: Creating a workflow
-│
-├─ Part of a module?
-│  ├─ YES → Module-based (include module variables)
-│  └─ NO  → Standalone (standard variables only)
-│
-├─ Could this take multiple sessions / lots of tokens?
-│  ├─ YES → Continuable (add step-01b-continue.md)
-│  └─ NO  → Single-session (simpler init)
-│
-└─ Will users need to edit/validate this workflow?
-   ├─ YES → Tri-modal (steps-c/, steps-e/, steps-v/)
-   └─ NO  → Create-only (steps-c/ only)
-```
-
----
-
-## Questions to Ask User
-
-**Module:**
-"Is this workflow standalone or part of a specific module (BMB, BMM, CIS, BMGD)?"
-
-**Continuable:**
-"Could this workflow consume many tokens or require multiple sessions?
-- If YES: Add continuation support
-- If NO: Keep it simple for single-session"
-
-**Edit/Validate:**
-"Will this workflow need edit and validate capabilities, or just create?
-- Create only: Simpler, faster
-- Create + Edit + Validate: More robust, maintainable"
-
-**Document:**
-"Does this workflow produce a document/output file?"
-- If YES: Use free-form template (recommended)
-- If NO: What does it produce?
-
----
-
-## Output Format Decision
-
-| Workflow Type           | Init Template            | Output Format |
-| ----------------------- | ------------------------ | ------------- |
-| Continuable + Document  | step-01-init-continuable | Free-form     |
-| Single-Session + Document| Standard init           | Free-form     |
-| Continuable + No Doc    | step-01-init-continuable | N/A           |
-| Single-Session + No Doc  | Standard init            | N/A           |
-
-**Free-form template** (recommended):
-```yaml
----
-stepsCompleted: []
-lastStep: ''
-date: ''
-user_name: ''
----
-
-# {{document_title}}
-
-[Content appended progressively]
-```

package/templates/commonproject/_bmad/bmb/workflows/workflow/steps-c/step-00-conversion.md

@@ -1,262 +0,0 @@
----
-name: 'step-00-conversion'
-description: 'Convert existing workflow to BMAD compliant format by reading all instructions and extracting plan'
-
-nextStepFile: './step-02-classification.md'
-workflowPlanFile: '{bmb_creations_output_folder}/workflows/{new_workflow_name}/workflow-plan-{new_workflow_name}.md'
----
-
-# Step 0: Workflow Conversion
-
-## STEP GOAL:
-
-Convert an existing workflow (any format) to BMAD compliant format by fully reading and understanding every instruction, extracting the essence, and creating a plan document.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER skip reading the entire source workflow
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 📋 YOU ARE A FACILITATOR, not an autonomous converter
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a workflow analyst and conversion specialist
-- ✅ If you already have been given communication or persona patterns, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring workflow architecture expertise, user brings their existing workflow
-- ✅ Together we will extract the essence and rebuild compliantly
-
-### Step-Specific Rules:
-
-- 🎯 Focus on understanding the COMPLETE existing workflow
-- 🚫 FORBIDDEN to skip any instruction or file
-- 💬 Read EVERYTHING - instructions.md, workflow.yaml, step files, templates
-- 📋 Document the essence succinctly
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load and read the ENTIRE source workflow
-- 💾 Extract: goal, steps, output, input requirements
-- 📖 Create plan with conversionFrom metadata
-- 🚫 FORBIDDEN to proceed without complete understanding
-
-## CONTEXT BOUNDARIES:
-
-- User provides existing workflow path (from routing or direct)
-- This REPLACES step-01-discovery - we skip to step-02-classification
-- The source workflow can be ANY format (legacy XML, partial, other systems)
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-### 1. Get Source Workflow Path
-
-**If path was passed from routing (e.g., from edit workflow):**
-- Use `{sourceWorkflowPath}` provided
-
-**If no path was passed:**
-
-"I can help you convert an existing workflow to BMAD compliant format.
-
-**Please provide the path to the workflow you want to convert:**
-
-This could be:
-- A folder containing workflow.md
-- A folder with workflow.yaml (legacy format)
-- A folder with instructions.md
-- Any workflow from another system
-
-**Path:** {user provides path}"
-
-### 2. Load EVERYTHING - DO NOT BE LAZY
-
-"**Loading source workflow for complete analysis...**
-
-**CRITICAL:** I will read EVERY file in this workflow to understand it completely."
-
-**Load these files based on what exists:**
-
-**If workflow.md exists:**
-- Load workflow.md completely
-- Load all step files (steps/*, steps-c/*, steps-v/*, steps-e/*)
-- Load all data files (data/*)
-- Load all templates (templates/*)
-
-**If workflow.yaml exists (legacy XML format):**
-- Load workflow.yaml completely
-- Load instructions.md completely
-- Load all step files, templates, data
-
-**If other format:**
-- Load every file that exists
-- Read everything to understand the structure
-
-**⚠️ DO NOT BE LAZY - Load and READ COMPLETELY:**
-
-For each step file, read:
-- The STEP GOAL
-- All MANDATORY EXECUTION RULES
-- All instructions in EXECUTION PROTOCOLS
-- All menu options
-- All templates and outputs
-
-"**✅ Source workflow loaded completely**
-
-**Files read:** {count} files
-**Format detected:** {format}
-**Structure identified:** {brief description}"
-
-### 3. Extract and Document Workflow Essence
-
-Create the workflow plan with complete extraction:
-
-"**Extracting workflow essence...**"
-
-Create `{workflowPlanFile}`:
-
-```markdown
----
-conversionFrom: '{sourceWorkflowPath}'
-originalFormat: '{detected format}'
-stepsCompleted: ['step-00-conversion']
-created: {current date}
-status: CONVERSION
----
-
-# Workflow Creation Plan
-
-## Conversion Source
-
-**Original Path:** {sourceWorkflowPath}
-**Original Format:** {workflow.yaml / workflow.md / custom / etc.}
-**Detected Structure:** {describe what was found}
-
----
-
-## Original Workflow Analysis
-
-### Goal (from source)
-
-{Extract the exact goal from the source workflow}
-
-### Original Steps (Complete List)
-
-{Create succinct bullet list of EVERY step from the source:}
-
-**Step 1:** {Step name} - {Brief purpose}
-**Step 2:** {Step name} - {Brief purpose}
-**Step 3:** {Step name} - {Brief purpose}
-...
-**Step N:** {Step name} - {Brief purpose}
-
-### Output / Deliverable
-
-{What does this workflow produce?}
-
-### Input Requirements
-
-{What inputs does this workflow need from the user?}
-
-### Key Instructions to LLM
-
-{Extract the key instruction patterns - how does the workflow talk to the LLM?
-What style? What level of detail? What collaborative approach?}
-
----
-
-## Conversion Notes
-
-**What works well in original:**
-{List strengths to preserve}
-
-**What needs improvement:**
-{List issues to address}
-
-**Compliance gaps identified:**
-{List what's missing for BMAD compliance}
-```
-
-### 4. Present Extracted Information to User
-
-"**I've analyzed your existing workflow completely. Here's what I found:**
-
----
-
-**Workflow Goal:**
-{goal from analysis}
-
-**Steps ({count}):**
-{Display succinct bullet list}
-
-**Output:**
-{what it produces}
-
-**Input Requirements:**
-{what it needs from user}
-
----
-
-**Format:** {originalFormat}
-**Compliance Status:** {compliant / non-compliant / partial}
-
-**Key observations:**
-{Share 2-3 key insights about the workflow}"
-
-### 5. Discovery Questions for Conversion
-
-Even though this is a conversion, we need to understand some things:
-
-"**A few questions to ensure the conversion captures your intent:**
-
-1. **What's working well** in this workflow that we should definitely preserve?
-
-2. **What problems** have you encountered with this workflow that we should fix?
-
-3. **Any missing features** or improvements you'd like to add during conversion?
-
-4. **Who will use** the converted workflow - same audience or different?"
-
-### 6. Confirm and Proceed to Classification
-
-"**Based on my analysis and your answers, I'm ready to proceed with classification.**
-
-**Next step:** We'll classify the workflow type (document, action, interactive, autonomous, meta), determine structure (continuable or single-session), and decide if it needs validation steps.
-
-**Ready to proceed?** [C] Continue to Classification"
-
-#### Menu Handling Logic:
-
-- IF C: Update workflowPlanFile with conversion notes, then load, read entirely, then execute {nextStepFile}
-- IF Any other: help user respond, then redisplay menu
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN the entire source workflow has been read and analyzed, and the plan document contains the complete extraction (goal, steps, output, inputs) and conversionFrom metadata, will you then load and read fully `{nextStepFile}` to execute classification.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- ENTIRE source workflow loaded and read
-- Every step documented in plan
-- Goal, output, inputs extracted
-- conversionFrom metadata set
-- User confirms understanding
-- Proceeding to classification
-
-### ❌ SYSTEM FAILURE:
-
-- Not loading all files in source workflow
-- Skipping step files
-- Not reading instructions completely
-- Missing steps in documentation
-- Not setting conversionFrom metadata
-- Proceeding without complete understanding
-
-**Master Rule:** DO NOT BE LAZY. Read EVERYTHING. Document the COMPLETE workflow essence. The conversion must capture ALL of the original workflow's intent and functionality.