## Key Changes ### 1. Time Estimate Prohibition (All Modules) - Added critical warnings against providing ANY time estimates (hours/days/weeks/months) - Acknowledges AI has fundamentally changed development speed - Applied to 33 workflow instruction files across BMB, BMGD, BMM, and CIS modules - Updated workflow creation guide with prohibition guidelines ### 2. Enhanced Epic Creation Workflow - Added intelligent UPDATE vs CREATE mode detection - Detects available context (UX, Architecture, Domain brief, Product brief) - Progressive enhancement: creates basic epics, then enriches with UX/Architecture - Living document approach with continuous updates - Added 305 lines of sophisticated workflow logic ### 3. Workflow Status Initialization Refactoring - Simplified from 893 to 318 lines (65% reduction) - Streamlined state detection: CLEAN, PLANNING, ACTIVE, LEGACY, UNCLEAR - Cleaner path selection and initialization logic - Removed redundant complexity while maintaining functionality ### 4. Workflow Path Updates - Updated all 4 workflow paths (enterprise/method × brownfield/greenfield) - Added multiple optional epic creation steps at different phases: - After PRD (basic structure) - After UX Design (with interaction context) - After Architecture (final with full context) - Changed PRD output description from "with epics and stories" to "with FRs and NFRs" ### 5. Architecture & Innovation Updates - Made epics input optional in architecture workflow (falls back to PRD FRs) - Updated innovation strategy phases to remove time-based language - Phases now: Immediate Impact → Foundation Building → Scale & Optimization ### Files Changed - 33 instruction files updated with time estimate prohibition - 2 workflow.yaml files updated (create-epics-and-stories, architecture) - 4 workflow path YAML files updated - 1 workflow creation guide enhanced This refactor significantly improves workflow intelligence, removes harmful time-based planning assumptions, and creates more adaptive, context-aware workflows that better leverage AI capabilities.
10 KiB
Storytelling Workflow Instructions
Workflow
The workflow execution engine is governed by: {project_root}/{bmad_folder}/core/tasks/workflow.xml You MUST have already loaded and processed: {project_root}/{bmad_folder}/cis/workflows/storytelling/workflow.yaml Communicate all responses in {communication_language} ⚠️ 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.Check if context data was provided with workflow invocation
Load the context document from the data file path Study the background information, brand details, or subject matter Use the provided context to inform story development Acknowledge the focused storytelling goal I see we're crafting a story based on the context provided. What specific angle or emphasis would you like? Proceed with context gathering 1. What's the purpose of this story? (e.g., marketing, pitch, brand narrative, case study) 2. Who is your target audience? 3. What key messages or takeaways do you want the audience to have? 4. Any constraints? (length, tone, medium, existing brand guidelines)Wait for user response before proceeding. This context shapes the narrative approach.
story_purpose, target_audience, key_messages
Load story frameworks from {story_frameworks} CSV file Parse: story_type, name, description, key_elements, best_for
Based on the context from Step 1, present framework options:
I can help craft your story using these proven narrative frameworks:Transformation Narratives:
- Hero's Journey - Classic transformation arc with adventure and return
- Pixar Story Spine - Emotional structure building tension to resolution
- Customer Journey Story - Before/after transformation narrative
- Challenge-Overcome Arc - Dramatic obstacle-to-victory structure
Strategic Narratives:
- Brand Story - Values, mission, and unique positioning
- Pitch Narrative - Persuasive problem-to-solution structure
- Vision Narrative - Future-focused aspirational story
- Origin Story - Foundational narrative of how it began
Specialized Narratives:
- Data Storytelling - Transform insights into compelling narrative
- Emotional Hooks - Craft powerful opening and touchpoints
Which framework best fits your purpose? (Enter 1-10, or ask for my recommendation)
Analyze story_purpose, target_audience, and key_messages Recommend best-fit framework with clear rationale Based on your {{story_purpose}} for {{target_audience}}, I recommend: **{{framework_name}}** because {{rationale}}story_type, framework_name
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. - 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 truthBased on selected framework, gather key story elements:
Reference key_elements from selected story_type in CSV Parse key_elements (pipe-separated) into individual components Guide user through each element with targeted questions
For Hero's Journey:
- Who/what is the hero of this story?
- What's their ordinary world before the adventure?
- What call to adventure disrupts their world?
- What trials/challenges do they face?
- How are they transformed by the journey?
- What wisdom do they bring back?
For Pixar Story Spine:
- Once upon a time, what was the situation?
- Every day, what was the routine?
- Until one day, what changed?
- Because of that, what happened next?
- And because of that? (continue chain)
- Until finally, how was it resolved?
For Brand Story:
- What was the origin spark for this brand?
- What core values drive every decision?
- How does this impact customers/users?
- What makes this different from alternatives?
- Where is this heading in the future?
For Pitch Narrative:
- What's the problem landscape you're addressing?
- What's your vision for the solution?
- What proof/traction validates this approach?
- What action do you want the audience to take?
For Data Storytelling:
- What context does the audience need?
- What's the key data revelation/insight?
- What patterns explain this insight?
- So what? Why does this matter?
- What actions should this insight drive?
story_beats, character_voice, conflict_tension, transformation
Stories stick when they resonate emotionally. Develop the emotional journey:
What emotion should the audience feel at the beginning? What emotional shift happens at the turning point? What emotion should they carry away at the end? Where are the emotional peaks (high tension/joy)? Where are the valleys (low points/struggle)?
Help them identify:
- Relatable struggles that create empathy
- Surprising moments that capture attention
- Personal stakes that make it matter
- Satisfying payoffs that create resolution
emotional_arc, emotional_touchpoints
The first moment determines if they keep reading/listening.
What surprising fact, question, or statement could open this story? What's the most intriguing part of this story to lead with?
A strong hook:
- Surprises or challenges assumptions
- Raises an urgent question
- Creates immediate relatability
- Promises valuable payoff
- Uses vivid, concrete details
opening_hook
Would you like to:
- Draft the story yourself with my guidance
- Have me write the first draft based on what we've discussed
- Co-create it iteratively together
complete_story, core_narrative
Adapt the story for different contexts and lengths:
What channels or formats will you use this story in?
Based on response, create appropriate variations:
- Short Version (1-3 sentences) - Social media, email subject lines, quick pitches
- Medium Version (1-2 paragraphs) - Email body, blog intro, executive summary
- Extended Version (full narrative) - Articles, presentations, case studies, website
short_version, medium_version, extended_version
Provide strategic guidance for story deployment:
Where and how will you use this story?
Consider:
- Best channels for this story type
- Audience-specific adaptations needed
- Tone/voice consistency with brand
- Visual or multimedia enhancements
- Testing and feedback approach
best_channels, audience_considerations, tone_notes, adaptation_suggestions
Polish and plan forward:
What parts of the story feel strongest? What areas could use more refinement? What's the key resolution or call to action for your story? Do you need additional story versions for other audiences/purposes? How will you test this story with your audience?
resolution, refinement_opportunities, additional_versions, feedback_plan
Compile all story components into the structured template:
- Ensure all story versions are complete and polished
- Format according to template structure
- Include all strategic guidance and usage notes
- Verify tone and voice consistency
- Fill all template placeholders with actual content
Write final story document to {output_folder}/story-{{date}}.md Confirm completion with: "Story complete, {user_name}! Your narrative has been saved to {output_folder}/story-{{date}}.md"
agent_role, agent_name, user_name, date