create-byan-agent 2.18.0 → 2.19.1

package/install/templates/_byan/workflow/simple/storytelling/instructions.md

@@ -0,0 +1,293 @@
+# Storytelling Workflow Instructions
+
+## Workflow
+
+<workflow>
+<critical>The workflow execution engine is governed by: {project-root}/_byan/command/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {project-root}/_byan/workflow/simple/storytelling/workflow.yaml</critical>
+<critical>Communicate all responses in {communication_language}</critical>
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
+<critical>⚠️ CHECKPOINT PROTOCOL: After EVERY <template-output> tag, you MUST follow workflow.xml substep 2c: SAVE content to file immediately → SHOW checkpoint separator (━━━━━━━━━━━━━━━━━━━━━━━) → DISPLAY generated content → PRESENT options [a]Advanced Elicitation/[c]Continue/[p]Party-Mode/[y]YOLO → WAIT for user response. Never batch saves or skip checkpoints.</critical>
+
+<step n="1" goal="Story Context Setup">
+
+<action>Check if context data was provided with workflow invocation</action>
+
+<check if="data attribute was passed to this workflow">
+  <action>Load the context document from the data file path</action>
+  <action>Study the background information, brand details, or subject matter</action>
+  <action>Use the provided context to inform story development</action>
+  <action>Acknowledge the focused storytelling goal</action>
+  <ask response="story_refinement">I see we're crafting a story based on the context provided. What specific angle or emphasis would you like?</ask>
+</check>
+
+<check if="no context data provided">
+  <action>Proceed with context gathering</action>
+  <ask response="story_purpose">1. What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study)</ask>
+  <ask response="target_audience">2. Who is your target audience?</ask>
+  <ask response="key_messages">3. What key messages or takeaways do you want the audience to have?</ask>
+  <ask>4. Any constraints? (length, tone, medium, existing brand guidelines)</ask>
+
+<critical>Wait for user response before proceeding. This context shapes the narrative approach.</critical>
+</check>
+
+<template-output>story_purpose, target_audience, key_messages</template-output>
+
+</step>
+
+<step n="2" goal="Select Story Framework">
+
+<action>Load story frameworks from {story_frameworks} CSV file</action>
+<action>Parse: story_type, name, description, key_elements, best_for</action>
+
+Based on the context from Step 1, present framework options:
+
+<ask response="framework_selection">
+I can help craft your story using these proven narrative frameworks:
+
+**Transformation Narratives:**
+
+1. **Hero's Journey** - Classic transformation arc with adventure and return
+2. **Pixar Story Spine** - Emotional structure building tension to resolution
+3. **Customer Journey Story** - Before/after transformation narrative
+4. **Challenge-Overcome Arc** - Dramatic obstacle-to-victory structure
+
+**Strategic Narratives:**
+
+5. **Brand Story** - Values, mission, and unique positioning
+6. **Pitch Narrative** - Persuasive problem-to-solution structure
+7. **Vision Narrative** - Future-focused aspirational story
+8. **Origin Story** - Foundational narrative of how it began
+
+**Specialized Narratives:**
+
+9. **Data Storytelling** - Transform insights into compelling narrative
+10. **Emotional Hooks** - Craft powerful opening and touchpoints
+
+Which framework best fits your purpose? (Enter 1-10, or ask for my recommendation)
+</ask>
+
+<check if="user asks for recommendation">
+  <action>Analyze story_purpose, target_audience, and key_messages</action>
+  <action>Recommend best-fit framework with clear rationale</action>
+  <example>
+  Based on your {{story_purpose}} for {{target_audience}}, I recommend:
+  **{{framework_name}}** because {{rationale}}
+  </example>
+</check>
+
+<template-output>story_type, framework_name</template-output>
+
+</step>
+
+<step n="3" goal="Gather Story Elements">
+
+<critical>
+YOU ARE A MASTER STORYTELLER: Guide through narrative development using the Socratic method. Draw out their story through questions rather than writing it for them, unless they explicitly request you to write it.
+</critical>
+
+<storytelling-principles>
+  - Every great story has conflict/tension - Find the struggle
+  - Show, don't tell - Use vivid, concrete details
+  - Change is essential - What transforms?
+  - Emotion drives memory - Find the feeling
+  - Authenticity resonates - Stay true to core truth
+</storytelling-principles>
+
+Based on selected framework, gather key story elements:
+
+<action>Reference key_elements from selected story_type in CSV</action>
+<action>Parse key_elements (pipe-separated) into individual components</action>
+<action>Guide user through each element with targeted questions</action>
+
+<framework-specific-guidance>
+
+For Hero's Journey:
+
+- <ask>Who/what is the hero of this story?</ask>
+- <ask>What's their ordinary world before the adventure?</ask>
+- <ask>What call to adventure disrupts their world?</ask>
+- <ask>What trials/challenges do they face?</ask>
+- <ask>How are they transformed by the journey?</ask>
+- <ask>What wisdom do they bring back?</ask>
+
+For Pixar Story Spine:
+
+- <ask>Once upon a time, what was the situation?</ask>
+- <ask>Every day, what was the routine?</ask>
+- <ask>Until one day, what changed?</ask>
+- <ask>Because of that, what happened next?</ask>
+- <ask>And because of that? (continue chain)</ask>
+- <ask>Until finally, how was it resolved?</ask>
+
+For Brand Story:
+
+- <ask>What was the origin spark for this brand?</ask>
+- <ask>What core values drive every decision?</ask>
+- <ask>How does this impact customers/users?</ask>
+- <ask>What makes this different from alternatives?</ask>
+- <ask>Where is this heading in the future?</ask>
+
+For Pitch Narrative:
+
+- <ask>What's the problem landscape you're addressing?</ask>
+- <ask>What's your vision for the solution?</ask>
+- <ask>What proof/traction validates this approach?</ask>
+- <ask>What action do you want the audience to take?</ask>
+
+For Data Storytelling:
+
+- <ask>What context does the audience need?</ask>
+- <ask>What's the key data revelation/insight?</ask>
+- <ask>What patterns explain this insight?</ask>
+- <ask>So what? Why does this matter?</ask>
+- <ask>What actions should this insight drive?</ask>
+
+</framework-specific-guidance>
+
+<template-output>story_beats, character_voice, conflict_tension, transformation</template-output>
+
+</step>
+
+<step n="4" goal="Craft Emotional Arc">
+
+Stories stick when they resonate emotionally. Develop the emotional journey:
+
+<ask>What emotion should the audience feel at the beginning?</ask>
+<ask>What emotional shift happens at the turning point?</ask>
+<ask>What emotion should they carry away at the end?</ask>
+<ask>Where are the emotional peaks (high tension/joy)?</ask>
+<ask>Where are the valleys (low points/struggle)?</ask>
+
+<guide>Help them identify:
+
+- Relatable struggles that create empathy
+- Surprising moments that capture attention
+- Personal stakes that make it matter
+- Satisfying payoffs that create resolution
+  </guide>
+
+<template-output>emotional_arc, emotional_touchpoints</template-output>
+
+</step>
+
+<step n="5" goal="Develop Opening Hook">
+
+The first moment determines if they keep reading/listening.
+
+<ask>What surprising fact, question, or statement could open this story?</ask>
+<ask>What's the most intriguing part of this story to lead with?</ask>
+
+<guide>A strong hook:
+
+- Surprises or challenges assumptions
+- Raises an urgent question
+- Creates immediate relatability
+- Promises valuable payoff
+- Uses vivid, concrete details
+  </guide>
+
+<template-output>opening_hook</template-output>
+
+</step>
+
+<step n="6" goal="Write Core Narrative">
+
+<ask>Would you like to:
+
+1. Draft the story yourself with my guidance
+2. Have me write the first draft based on what we've discussed
+3. Co-create it iteratively together
+   </ask>
+
+<if selection="1 or draft themselves">
+  <action>Provide writing prompts and encouragement</action>
+  <action>Offer feedback on drafts they share</action>
+  <action>Suggest refinements for clarity, emotion, flow</action>
+</if>
+
+<if selection="2 or ai writes the next draft based on discussions">
+  <action>Synthesize all gathered elements</action>
+  <action>Write complete narrative in appropriate tone/style</action>
+  <action>Structure according to chosen framework</action>
+  <action>Include vivid details and emotional beats</action>
+  <action>Present draft for feedback and refinement</action>
+</if>
+
+<if selection="3 or work collaboratively with co-creation">
+  <action>Write opening paragraph</action>
+  <action>Get feedback and iterate</action>
+  <action>Build section by section collaboratively</action>
+</if>
+
+<template-output>complete_story, core_narrative</template-output>
+
+</step>
+
+<step n="7" goal="Create Story Variations">
+
+Adapt the story for different contexts and lengths:
+
+<ask>What channels or formats will you use this story in?</ask>
+
+Based on response, create appropriate variations:
+
+1. **Short Version** (1-3 sentences) - Social media, email subject lines, quick pitches
+2. **Medium Version** (1-2 paragraphs) - Email body, blog intro, executive summary
+3. **Extended Version** (full narrative) - Articles, presentations, case studies, website
+
+<template-output>short_version, medium_version, extended_version</template-output>
+
+</step>
+
+<step n="8" goal="Usage Guidelines">
+
+Provide strategic guidance for story deployment:
+
+<ask>Where and how will you use this story?</ask>
+
+<guide>Consider:
+
+- Best channels for this story type
+- Audience-specific adaptations needed
+- Tone/voice consistency with brand
+- Visual or multimedia enhancements
+- Testing and feedback approach
+  </guide>
+
+<template-output>best_channels, audience_considerations, tone_notes, adaptation_suggestions</template-output>
+
+</step>
+
+<step n="9" goal="Refinement AND Next Steps">
+
+Polish and plan forward:
+
+<ask>What parts of the story feel strongest?</ask>
+<ask>What areas could use more refinement?</ask>
+<ask>What's the key resolution or call to action for your story?</ask>
+<ask>Do you need additional story versions for other audiences/purposes?</ask>
+<ask>How will you test this story with your audience?</ask>
+
+<template-output>resolution, refinement_opportunities, additional_versions, feedback_plan</template-output>
+
+</step>
+
+<step n="10" goal="Generate Final Output">
+
+Compile all story components into the structured template:
+
+1. Ensure all story versions are complete and polished
+2. Format according to template structure
+3. Include all strategic guidance and usage notes
+4. Verify tone and voice consistency
+5. Fill all template placeholders with actual content
+
+<action>Write final story document to {output_folder}/story-{{date}}.md</action>
+<action>Confirm completion with: "Story complete, {user_name}! Your narrative has been saved to {output_folder}/story-{{date}}.md"</action>
+
+<template-output>agent_role, agent_name, user_name, date</template-output>
+
+</step>
+
+</workflow>

package/install/templates/_byan/workflow/simple/storytelling/workflow.yaml

@@ -0,0 +1,27 @@
+# Storytelling Workflow Configuration
+name: "storytelling"
+description: "Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose."
+author: "BMad"
+
+# Critical variables load from config_source
+config_source: "{project-root}/_byan/cis/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+date: system-generated
+
+# Context can be provided via data attribute when invoking
+# Example: data="{path}/brand-info.md" provides brand context
+
+# Module path and component files
+installed_path: "{project-root}/_byan/workflow/simple/storytelling"
+template: "{installed_path}/template.md"
+instructions: "{installed_path}/instructions.md"
+
+# Required Data Files
+story_frameworks: "{installed_path}/story-types.csv"
+
+# Output configuration
+default_output_file: "{output_folder}/story-{{date}}.md"
+
+standalone: true

package/install/templates/_byan/workflow/simple/testarch/atdd/instructions.md

@@ -0,0 +1,38 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Acceptance Test-Driven Development (ATDD)
+
+**Workflow ID**: `_byan/connaissance/testarch/atdd`
+**Version**: 5.0 (Step-File Architecture)
+
+---
+
+## Overview
+
+Generates **failing acceptance tests** before implementation (TDD red phase), plus an implementation checklist. Produces tests at appropriate levels (E2E/API/Component) with supporting fixtures and helpers.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This workflow uses **step-file architecture**:
+
+- **Micro-file Design**: Each step is self-contained
+- **JIT Loading**: Only the current step file is in memory
+- **Sequential Enforcement**: Execute steps in order without skipping
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+From `workflow.yaml`, resolve:
+
+- `config_source`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `date`
+- `test_dir`
+
+### 2. First Step
+
+Load, read completely, and execute:
+`{project-root}/_byan/workflow/simple/testarch/atdd/steps-c/step-01-preflight-and-context.md`

package/install/templates/_byan/workflow/simple/testarch/atdd/steps-c/step-01-preflight-and-context.md

@@ -0,0 +1,110 @@
+---
+name: 'step-01-preflight-and-context'
+description: 'Verify prerequisites and load story, framework, and knowledge base'
+nextStepFile: './step-02-generation-mode.md'
+knowledgeIndex: '{project-root}/_byan/connaissance/testarch/tea-index.csv'
+---
+
+# Step 1: Preflight & Context Loading
+
+## STEP GOAL
+
+Verify prerequisites and load all required inputs before generating failing tests.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- 🚫 Halt if requirements are missing
+
+---
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Record outputs before proceeding
+- 📖 Load the next step only when instructed
+
+## CONTEXT BOUNDARIES:
+
+- Available context: config, loaded artifacts, and knowledge fragments
+- Focus: this step's goal only
+- Limits: do not execute future steps
+- Dependencies: prior steps' outputs (if any)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+## 1. Prerequisites (Hard Requirements)
+
+- Story approved with **clear acceptance criteria**
+- Test framework configured (`playwright.config.ts` or `cypress.config.ts`)
+- Development environment available
+
+If any are missing: **HALT** and notify the user.
+
+---
+
+## 2. Load Story Context
+
+- Read story markdown from `{story_file}` (or ask user if not provided)
+- Extract acceptance criteria and constraints
+- Identify affected components and integrations
+
+---
+
+## 3. Load Framework & Existing Patterns
+
+- Read framework config
+- Inspect `{test_dir}` for existing test patterns, fixtures, helpers
+
+## 3.5 Read TEA Config Flags
+
+From `{config_source}`:
+
+- `tea_use_playwright_utils`
+- `tea_use_mcp_enhancements`
+
+---
+
+## 4. Load Knowledge Base Fragments
+
+Use `{knowledgeIndex}` to load:
+
+**Core (always):**
+
+- `data-factories.md`
+- `component-tdd.md`
+- `test-quality.md`
+- `test-healing-patterns.md`
+- `selector-resilience.md`
+- `timing-debugging.md`
+
+**Playwright Utils (if enabled):**
+
+- `overview.md`, `api-request.md`, `network-recorder.md`, `auth-session.md`, `intercept-network-call.md`, `recurse.md`, `log.md`, `file-utils.md`, `network-error-monitor.md`, `fixtures-composition.md`
+
+**Traditional Patterns (if utils disabled):**
+
+- `fixture-architecture.md`
+- `network-first.md`
+
+---
+
+## 5. Confirm Inputs
+
+Summarize loaded inputs and confirm with the user. Then proceed.
+
+Load next step: `{nextStepFile}`
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Step completed in full with required outputs
+
+### ❌ SYSTEM FAILURE:
+
+- Skipped sequence steps or missing outputs
+  **Master Rule:** Skipping steps is FORBIDDEN.

package/install/templates/_byan/workflow/simple/testarch/atdd/workflow.yaml

@@ -0,0 +1,45 @@
+# Test Architect workflow: atdd
+name: testarch-atdd
+description: "Generate failing acceptance tests before implementation using TDD red-green-refactor cycle"
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/_byan/tea/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/_byan/workflow/simple/testarch/atdd"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+template: "{installed_path}/atdd-checklist-template.md"
+
+# Variables and inputs
+variables:
+  test_dir: "{project-root}/tests" # Root test directory
+
+# Output configuration
+default_output_file: "{output_folder}/atdd-checklist-{story_id}.md"
+
+# Required tools
+required_tools:
+  - read_file # Read story markdown, framework config
+  - write_file # Create test files, checklist, factory stubs
+  - create_directory # Create test directories
+  - list_files # Find existing fixtures and helpers
+  - search_repo # Search for similar test patterns
+
+tags:
+  - qa
+  - atdd
+  - test-architect
+  - tdd
+  - red-green-refactor
+
+execution_hints:
+  interactive: false # Minimize prompts
+  autonomous: true # Proceed without user input unless blocked
+  iterative: true

package/install/templates/_byan/workflow/simple/testarch/automate/instructions.md

@@ -0,0 +1,43 @@
+<!-- Powered by BMAD-CORE™ -->
+
+# Test Automation Expansion
+
+**Workflow ID**: `_byan/connaissance/testarch/automate`
+**Version**: 5.0 (Step-File Architecture)
+
+---
+
+## Overview
+
+Expands test automation coverage by generating prioritized tests at the appropriate level (E2E, API, Component, Unit) with supporting fixtures and helpers.
+
+Modes:
+
+- **BMad-Integrated**: Uses story/PRD/test-design artifacts when available
+- **Standalone**: Analyzes existing codebase without BMad artifacts
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This workflow uses **step-file architecture** for disciplined execution:
+
+- **Micro-file Design**: Each step is self-contained
+- **JIT Loading**: Only the current step file is in memory
+- **Sequential Enforcement**: Execute steps in order without skipping
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+From `workflow.yaml`, resolve:
+
+- `config_source`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `date`
+- `test_dir`, `source_dir`, `coverage_target`, `standalone_mode`
+
+### 2. First Step
+
+Load, read completely, and execute:
+`{project-root}/_byan/workflow/simple/testarch/automate/steps-c/step-01-preflight-and-context.md`

package/install/templates/_byan/workflow/simple/testarch/automate/steps-c/step-01-preflight-and-context.md

@@ -0,0 +1,127 @@
+---
+name: 'step-01-preflight-and-context'
+description: 'Determine mode, verify framework, and load context and knowledge'
+nextStepFile: './step-02-identify-targets.md'
+knowledgeIndex: '{project-root}/_byan/connaissance/testarch/tea-index.csv'
+---
+
+# Step 1: Preflight & Context Loading
+
+## STEP GOAL
+
+Determine execution mode, verify framework readiness, and load the necessary artifacts and knowledge fragments.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 Read the entire step file before acting
+- ✅ Speak in `{communication_language}`
+- 🚫 Halt if framework scaffolding is missing
+
+---
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Follow the MANDATORY SEQUENCE exactly
+- 💾 Record outputs before proceeding
+- 📖 Load the next step only when instructed
+
+## CONTEXT BOUNDARIES:
+
+- Available context: config, loaded artifacts, and knowledge fragments
+- Focus: this step's goal only
+- Limits: do not execute future steps
+- Dependencies: prior steps' outputs (if any)
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
+
+## 1. Verify Framework
+
+Ensure a framework exists:
+
+- `playwright.config.ts` or `cypress.config.ts`
+- `package.json` includes test dependencies
+
+If missing: **HALT** with message "Run `framework` workflow first."
+
+---
+
+## 2. Determine Execution Mode
+
+- **BMad-Integrated** if story/tech-spec/test-design artifacts are provided or found
+- **Standalone** if only source code is available
+- If unclear, ask the user which mode to use
+
+---
+
+## 3. Load Context
+
+### BMad-Integrated (if available)
+
+- Story with acceptance criteria
+- PRD and/or tech spec
+- Test-design document (if exists)
+
+### Standalone
+
+- Skip artifacts; proceed to codebase analysis
+
+### Always Load
+
+- Test framework config
+- Existing test structure in `{test_dir}`
+- Existing tests (for coverage gaps)
+
+### Read TEA Config Flags
+
+- From `{config_source}` read `tea_use_playwright_utils`
+
+---
+
+## 4. Load Knowledge Base Fragments
+
+Use `{knowledgeIndex}` and load only what is required.
+
+**Core (always load):**
+
+- `test-levels-framework.md`
+- `test-priorities-matrix.md`
+- `data-factories.md`
+- `selective-testing.md`
+- `ci-burn-in.md`
+- `test-quality.md`
+
+**Playwright Utils (if enabled):**
+
+- `overview.md`, `api-request.md`, `network-recorder.md`, `auth-session.md`, `intercept-network-call.md`, `recurse.md`, `log.md`, `file-utils.md`, `burn-in.md`, `network-error-monitor.md`, `fixtures-composition.md`
+
+**Traditional Patterns (if Playwright Utils disabled):**
+
+- `fixture-architecture.md`
+- `network-first.md`
+
+**Healing (if auto-heal enabled):**
+
+- `test-healing-patterns.md`
+- `selector-resilience.md`
+- `timing-debugging.md`
+
+---
+
+## 5. Confirm Inputs
+
+Summarize loaded artifacts, framework, and knowledge fragments, then proceed.
+
+Load next step: `{nextStepFile}`
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
+
+### ✅ SUCCESS:
+
+- Step completed in full with required outputs
+
+### ❌ SYSTEM FAILURE:
+
+- Skipped sequence steps or missing outputs
+  **Master Rule:** Skipping steps is FORBIDDEN.