bmad-method 4.14.1 → 4.16.0

package/.bmad-core/data/technical-preferences.md

@@ -0,0 +1,3 @@
+# User-Defined Preferred Patterns and Preferences
+
+None Listed

package/.bmad-core/install-manifest.yml

@@ -0,0 +1,196 @@
+version: 4.14.1
+installed_at: '2025-06-26T02:40:53.157Z'
+install_type: full
+agent: null
+ide_setup: null
+ides_setup:
+  - cursor
+  - claude-code
+  - windsurf
+  - roo
+  - cline
+  - gemini
+files:
+  - path: .bmad-core/core-config.yml
+    hash: 8ccd25183820a4a9
+    modified: false
+  - path: .bmad-core/workflows/greenfield-ui.yml
+    hash: fed0d7f34062ff95
+    modified: false
+  - path: .bmad-core/workflows/greenfield-service.yml
+    hash: 9250ed616aecfb6c
+    modified: false
+  - path: .bmad-core/workflows/greenfield-fullstack.yml
+    hash: 6d650ead514b3cd8
+    modified: false
+  - path: .bmad-core/workflows/brownfield-ui.yml
+    hash: 00ba2e9c095151d0
+    modified: false
+  - path: .bmad-core/workflows/brownfield-service.yml
+    hash: 8b7748bb6010c557
+    modified: false
+  - path: .bmad-core/workflows/brownfield-fullstack.yml
+    hash: 0317b34832a19627
+    modified: false
+  - path: .bmad-core/utils/workflow-management.md
+    hash: 6c9da44e60ec257f
+    modified: false
+  - path: .bmad-core/utils/web-agent-startup-instructions.md
+    hash: 27ee619b1a953aa6
+    modified: false
+  - path: .bmad-core/utils/template-format.md
+    hash: c91208908af1dc78
+    modified: false
+  - path: .bmad-core/utils/file-resolution-context.md
+    hash: a17fd3670e680f0c
+    modified: false
+  - path: .bmad-core/templates/story-tmpl.md
+    hash: 3d8d98f09c3bcd3a
+    modified: false
+  - path: .bmad-core/templates/project-brief-tmpl.md
+    hash: 4574687e30632eed
+    modified: false
+  - path: .bmad-core/templates/prd-tmpl.md
+    hash: b5d75306c428615b
+    modified: false
+  - path: .bmad-core/templates/market-research-tmpl.md
+    hash: 3e0481172cc9f056
+    modified: false
+  - path: .bmad-core/templates/fullstack-architecture-tmpl.md
+    hash: 969ca155b5832956
+    modified: false
+  - path: .bmad-core/templates/front-end-spec-tmpl.md
+    hash: fb4866eaeb8722fb
+    modified: false
+  - path: .bmad-core/templates/front-end-architecture-tmpl.md
+    hash: 84025d1fc469d2c5
+    modified: false
+  - path: .bmad-core/templates/competitor-analysis-tmpl.md
+    hash: d4e25586a643f8ca
+    modified: false
+  - path: .bmad-core/templates/brownfield-prd-tmpl.md
+    hash: 3c6039fa53337ba3
+    modified: false
+  - path: .bmad-core/templates/brownfield-architecture-tmpl.md
+    hash: c7b0962d7e856aae
+    modified: false
+  - path: .bmad-core/templates/architecture-tmpl.md
+    hash: b8daeb43d0196ee1
+    modified: false
+  - path: .bmad-core/tasks/shard-doc.md
+    hash: 0a04158f420a09df
+    modified: false
+  - path: .bmad-core/tasks/review-story.md
+    hash: cb88d2aed30afe7d
+    modified: false
+  - path: .bmad-core/tasks/kb-mode-interaction.md
+    hash: 97623a1fbcb686e4
+    modified: false
+  - path: .bmad-core/tasks/index-docs.md
+    hash: 349f0ddf65dd71fe
+    modified: false
+  - path: .bmad-core/tasks/generate-ai-frontend-prompt.md
+    hash: 1298309d4e874b0b
+    modified: false
+  - path: .bmad-core/tasks/execute-checklist.md
+    hash: e83f4ae155bb5db8
+    modified: false
+  - path: .bmad-core/tasks/document-project.md
+    hash: 6daded58e413997d
+    modified: false
+  - path: .bmad-core/tasks/doc-migration-task.md
+    hash: 6a86e5d9cd386452
+    modified: false
+  - path: .bmad-core/tasks/create-next-story.md
+    hash: be7699b750a382e3
+    modified: false
+  - path: .bmad-core/tasks/create-doc.md
+    hash: 63ef4f97bfd66c1b
+    modified: false
+  - path: .bmad-core/tasks/create-deep-research-prompt.md
+    hash: a104cb9b17cde3b7
+    modified: false
+  - path: .bmad-core/tasks/correct-course.md
+    hash: 4da2f889fbc8b457
+    modified: false
+  - path: .bmad-core/tasks/core-dump.md
+    hash: 44ac4d753c5ff573
+    modified: false
+  - path: .bmad-core/tasks/brownfield-create-story.md
+    hash: 6e5cd0247836c4de
+    modified: false
+  - path: .bmad-core/tasks/brownfield-create-epic.md
+    hash: 1b2b6c8b67a176ee
+    modified: false
+  - path: .bmad-core/tasks/brainstorming-techniques.md
+    hash: 075818b207444cb2
+    modified: false
+  - path: .bmad-core/tasks/advanced-elicitation.md
+    hash: 0950e5318989db16
+    modified: false
+  - path: .bmad-core/data/technical-preferences.md
+    hash: 6530bed845540b0d
+    modified: false
+  - path: .bmad-core/data/bmad-kb.md
+    hash: cc192f1a55b71304
+    modified: false
+  - path: .bmad-core/checklists/story-draft-checklist.md
+    hash: 28d5c2d3e9088320
+    modified: false
+  - path: .bmad-core/checklists/story-dod-checklist.md
+    hash: 06ab7e73a69f930a
+    modified: false
+  - path: .bmad-core/checklists/po-master-checklist.md
+    hash: 89d2dc785aa0e8a7
+    modified: false
+  - path: .bmad-core/checklists/pm-checklist.md
+    hash: 139209e205a92628
+    modified: false
+  - path: .bmad-core/checklists/change-checklist.md
+    hash: 5f2e21564d452d35
+    modified: false
+  - path: .bmad-core/checklists/architect-checklist.md
+    hash: 99f4655b9ff99dd1
+    modified: false
+  - path: .bmad-core/agents/ux-expert.md
+    hash: db26962b08a17c7b
+    modified: false
+  - path: .bmad-core/agents/sm.md
+    hash: 92ff5d6215ca2dcb
+    modified: false
+  - path: .bmad-core/agents/qa.md
+    hash: be99105e59b52422
+    modified: false
+  - path: .bmad-core/agents/po.md
+    hash: 76d33c1721142f31
+    modified: false
+  - path: .bmad-core/agents/pm.md
+    hash: 40f796bdefcd14c6
+    modified: false
+  - path: .bmad-core/agents/dev.md
+    hash: 3e65e0ce05572906
+    modified: false
+  - path: .bmad-core/agents/bmad-orchestrator.md
+    hash: c26017d6501d2e06
+    modified: false
+  - path: .bmad-core/agents/bmad-master.md
+    hash: 1a35aa8a54c996d0
+    modified: false
+  - path: .bmad-core/agents/architect.md
+    hash: 8c7f7244f7394781
+    modified: false
+  - path: .bmad-core/agents/analyst.md
+    hash: f04c2ac401442edc
+    modified: false
+  - path: .bmad-core/agent-teams/team-no-ui.yml
+    hash: db791eaa9b060ad3
+    modified: false
+  - path: .bmad-core/agent-teams/team-ide-minimal.yml
+    hash: 600b6795116fd74e
+    modified: false
+  - path: .bmad-core/agent-teams/team-fullstack.yml
+    hash: 8adda579fff343cd
+    modified: false
+  - path: .bmad-core/agent-teams/team-all.yml
+    hash: 788067c0fd19c76d
+    modified: false

package/.bmad-core/tasks/advanced-elicitation.md

@@ -0,0 +1,92 @@
+# Advanced Elicitation Task
+
+## Purpose
+
+- Provide optional reflective and brainstorming actions to enhance content quality
+- Enable deeper exploration of ideas through structured elicitation techniques
+- Support iterative refinement through multiple analytical perspectives
+
+## Task Instructions
+
+### 1. Section Context and Review
+
+[[LLM: When invoked after outputting a section:
+
+1. First, provide a brief 1-2 sentence summary of what the user should look for in the section just presented (e.g., "Please review the technology choices for completeness and alignment with your project needs. Pay special attention to version numbers and any missing categories.")
+
+2. If the section contains Mermaid diagrams, explain each diagram briefly before offering elicitation options (e.g., "The component diagram shows the main system modules and their interactions. Notice how the API Gateway routes requests to different services.")
+
+3. If the section contains multiple distinct items (like multiple components, multiple patterns, etc.), inform the user they can apply elicitation actions to:
+
+   - The entire section as a whole
+   - Individual items within the section (specify which item when selecting an action)
+
+4. Then present the action list as specified below.]]
+
+### 2. Ask for Review and Present Action List
+
+[[LLM: Ask the user to review the drafted section. In the SAME message, inform them that they can suggest additions, removals, or modifications, OR they can select an action by number from the 'Advanced Reflective, Elicitation & Brainstorming Actions'. If there are multiple items in the section, mention they can specify which item(s) to apply the action to. Then, present ONLY the numbered list (0-9) of these actions. Conclude by stating that selecting 9 will proceed to the next section. Await user selection. If an elicitation action (0-8) is chosen, execute it and then re-offer this combined review/elicitation choice. If option 9 is chosen, or if the user provides direct feedback, proceed accordingly.]]
+
+**Present the numbered list (0-9) with this exact format:**
+
+```text
+**Advanced Reflective, Elicitation & Brainstorming Actions**
+Choose an action (0-9 - 9 to bypass - HELP for explanation of these options):
+
+0. Expand or Contract for Audience
+1. Explain Reasoning (CoT Step-by-Step)
+2. Critique and Refine
+3. Analyze Logical Flow and Dependencies
+4. Assess Alignment with Overall Goals
+5. Identify Potential Risks and Unforeseen Issues
+6. Challenge from Critical Perspective (Self or Other Persona)
+7. Explore Diverse Alternatives (ToT-Inspired)
+8. Hindsight is 20/20: The 'If Only...' Reflection
+9. Proceed / No Further Actions
+```
+
+### 2. Processing Guidelines
+
+**Do NOT show:**
+
+- The full protocol text with `[[LLM: ...]]` instructions
+- Detailed explanations of each option unless executing or the user asks, when giving the definition you can modify to tie its relevance
+- Any internal template markup
+
+**After user selection from the list:**
+
+- Execute the chosen action according to the protocol instructions below
+- Ask if they want to select another action or proceed with option 9 once complete
+- Continue until user selects option 9 or indicates completion
+
+## Action Definitions
+
+0. Expand or Contract for Audience
+   [[LLM: Ask the user whether they want to 'expand' on the content (add more detail, elaborate) or 'contract' it (simplify, clarify, make more concise). Also, ask if there's a specific target audience they have in mind. Once clarified, perform the expansion or contraction from your current role's perspective, tailored to the specified audience if provided.]]
+
+1. Explain Reasoning (CoT Step-by-Step)
+   [[LLM: Explain the step-by-step thinking process, characteristic of your role, that you used to arrive at the current proposal for this content.]]
+
+2. Critique and Refine
+   [[LLM: From your current role's perspective, review your last output or the current section for flaws, inconsistencies, or areas for improvement, and then suggest a refined version reflecting your expertise.]]
+
+3. Analyze Logical Flow and Dependencies
+   [[LLM: From your role's standpoint, examine the content's structure for logical progression, internal consistency, and any relevant dependencies. Confirm if elements are presented in an effective order.]]
+
+4. Assess Alignment with Overall Goals
+   [[LLM: Evaluate how well the current content contributes to the stated overall goals of the document, interpreting this from your specific role's perspective and identifying any misalignments you perceive.]]
+
+5. Identify Potential Risks and Unforeseen Issues
+   [[LLM: Based on your role's expertise, brainstorm potential risks, overlooked edge cases, or unintended consequences related to the current content or proposal.]]
+
+6. Challenge from Critical Perspective (Self or Other Persona)
+   [[LLM: Adopt a critical perspective on the current content. If the user specifies another role or persona (e.g., 'as a customer', 'as [Another Persona Name]'), critique the content or play devil's advocate from that specified viewpoint. If no other role is specified, play devil's advocate from your own current persona's viewpoint, arguing against the proposal or current content and highlighting weaknesses or counterarguments specific to your concerns. This can also randomly include YAGNI when appropriate, such as when trimming the scope of an MVP, the perspective might challenge the need for something to cut MVP scope.]]
+
+7. Explore Diverse Alternatives (ToT-Inspired)
+   [[LLM: From your role's perspective, first broadly brainstorm a range of diverse approaches or solutions to the current topic. Then, from this wider exploration, select and present 2 distinct alternatives, detailing the pros, cons, and potential implications you foresee for each.]]
+
+8. Hindsight is 20/20: The 'If Only...' Reflection
+   [[LLM: In your current persona, imagine it's a retrospective for a project based on the current content. What's the one 'if only we had known/done X...' that your role would humorously or dramatically highlight, along with the imagined consequences?]]
+
+9. Proceed / No Further Actions
+   [[LLM: Acknowledge the user's choice to finalize the current work, accept the AI's last output as is, or move on to the next step without selecting another action from this list. Prepare to proceed accordingly.]]

package/.bmad-core/tasks/brainstorming-techniques.md

@@ -0,0 +1,238 @@
+# Brainstorming Techniques Task
+
+This task provides a comprehensive toolkit of creative brainstorming techniques for ideation and innovative thinking. The analyst can use these techniques to facilitate productive brainstorming sessions with users.
+
+## Process
+
+### 1. Session Setup
+
+[[LLM: Begin by understanding the brainstorming context and goals. Ask clarifying questions if needed to determine the best approach.]]
+
+1. **Establish Context**
+
+   - Understand the problem space or opportunity area
+   - Identify any constraints or parameters
+   - Determine session goals (divergent exploration vs. focused ideation)
+
+2. **Select Technique Approach**
+   - Option A: User selects specific techniques
+   - Option B: Analyst recommends techniques based on context
+   - Option C: Random technique selection for creative variety
+   - Option D: Progressive technique flow (start broad, narrow down)
+
+### 2. Core Brainstorming Techniques
+
+#### Creative Expansion Techniques
+
+1. **"What If" Scenarios**
+   [[LLM: Generate provocative what-if questions that challenge assumptions and expand thinking beyond current limitations.]]
+
+   - What if we had unlimited resources?
+   - What if this problem didn't exist?
+   - What if we approached this from a child's perspective?
+   - What if we had to solve this in 24 hours?
+
+2. **Analogical Thinking**
+   [[LLM: Help user draw parallels between their challenge and other domains, industries, or natural systems.]]
+
+   - "How might this work like [X] but for [Y]?"
+   - Nature-inspired solutions (biomimicry)
+   - Cross-industry pattern matching
+   - Historical precedent analysis
+
+3. **Reversal/Inversion**
+   [[LLM: Flip the problem or approach it from the opposite angle to reveal new insights.]]
+
+   - What if we did the exact opposite?
+   - How could we make this problem worse? (then reverse)
+   - Start from the end goal and work backward
+   - Reverse roles or perspectives
+
+4. **First Principles Thinking**
+   [[LLM: Break down to fundamental truths and rebuild from scratch.]]
+   - What are the absolute fundamentals here?
+   - What assumptions can we challenge?
+   - If we started from zero, what would we build?
+   - What laws of physics/economics/human nature apply?
+
+#### Structured Ideation Frameworks
+
+1. **SCAMPER Method**
+   [[LLM: Guide through each SCAMPER prompt systematically.]]
+
+   - **S** = Substitute: What can be substituted?
+   - **C** = Combine: What can be combined or integrated?
+   - **A** = Adapt: What can be adapted from elsewhere?
+   - **M** = Modify/Magnify: What can be emphasized or reduced?
+   - **P** = Put to other uses: What else could this be used for?
+   - **E** = Eliminate: What can be removed or simplified?
+   - **R**= Reverse/Rearrange: What can be reversed or reordered?
+
+2. **Six Thinking Hats**
+   [[LLM: Cycle through different thinking modes, spending focused time in each.]]
+
+   - White Hat: Facts and information
+   - Red Hat: Emotions and intuition
+   - Black Hat: Caution and critical thinking
+   - Yellow Hat: Optimism and benefits
+   - Green Hat: Creativity and alternatives
+   - Blue Hat: Process and control
+
+3. **Mind Mapping**
+   [[LLM: Create text-based mind maps with clear hierarchical structure.]]
+
+   ```plaintext
+   Central Concept
+   ├── Branch 1
+   │   ├── Sub-idea 1.1
+   │   └── Sub-idea 1.2
+   ├── Branch 2
+   │   ├── Sub-idea 2.1
+   │   └── Sub-idea 2.2
+   └── Branch 3
+       └── Sub-idea 3.1
+   ```
+
+#### Collaborative Techniques
+
+1. **"Yes, And..." Building**
+   [[LLM: Accept every idea and build upon it without judgment. Encourage wild ideas and defer criticism.]]
+
+   - Accept the premise of each idea
+   - Add to it with "Yes, and..."
+   - Build chains of connected ideas
+   - Explore tangents freely
+
+2. **Brainwriting/Round Robin**
+   [[LLM: Simulate multiple perspectives by generating ideas from different viewpoints.]]
+
+   - Generate ideas from stakeholder perspectives
+   - Build on previous ideas in rounds
+   - Combine unrelated ideas
+   - Cross-pollinate concepts
+
+3. **Random Stimulation**
+   [[LLM: Use random words, images, or concepts as creative triggers.]]
+   - Random word association
+   - Picture/metaphor inspiration
+   - Forced connections between unrelated items
+   - Constraint-based creativity
+
+#### Deep Exploration Techniques
+
+1. **Five Whys**
+   [[LLM: Dig deeper into root causes and underlying motivations.]]
+
+   - Why does this problem exist? → Answer → Why? (repeat 5 times)
+   - Uncover hidden assumptions
+   - Find root causes, not symptoms
+   - Identify intervention points
+
+2. **Morphological Analysis**
+   [[LLM: Break down into parameters and systematically explore combinations.]]
+
+   - List key parameters/dimensions
+   - Identify possible values for each
+   - Create combination matrix
+   - Explore unusual combinations
+
+3. **Provocation Technique (PO)**
+   [[LLM: Make deliberately provocative statements to jar thinking.]]
+   - PO: Cars have square wheels
+   - PO: Customers pay us to take products
+   - PO: The problem solves itself
+   - Extract useful ideas from provocations
+
+### 3. Technique Selection Guide
+
+[[LLM: Help user select appropriate techniques based on their needs.]]
+
+**For Initial Exploration:**
+
+- What If Scenarios
+- First Principles
+- Mind Mapping
+
+**For Stuck/Blocked Thinking:**
+
+- Random Stimulation
+- Reversal/Inversion
+- Provocation Technique
+
+**For Systematic Coverage:**
+
+- SCAMPER
+- Morphological Analysis
+- Six Thinking Hats
+
+**For Deep Understanding:**
+
+- Five Whys
+- Analogical Thinking
+- First Principles
+
+**For Team/Collaborative Settings:**
+
+- Brainwriting
+- "Yes, And..."
+- Six Thinking Hats
+
+### 4. Session Flow Management
+
+[[LLM: Guide the brainstorming session with appropriate pacing and technique transitions.]]
+
+1. **Warm-up Phase** (5-10 min)
+
+   - Start with accessible techniques
+   - Build creative confidence
+   - Establish "no judgment" atmosphere
+
+2. **Divergent Phase** (20-30 min)
+
+   - Use expansion techniques
+   - Generate quantity over quality
+   - Encourage wild ideas
+
+3. **Convergent Phase** (15-20 min)
+
+   - Group and categorize ideas
+   - Identify patterns and themes
+   - Select promising directions
+
+4. **Synthesis Phase** (10-15 min)
+   - Combine complementary ideas
+   - Refine and develop concepts
+   - Prepare summary of insights
+
+### 5. Output Format
+
+[[LLM: Present brainstorming results in an organized, actionable format.]]
+
+**Session Summary:**
+
+- Techniques used
+- Number of ideas generated
+- Key themes identified
+
+**Idea Categories:**
+
+1. **Immediate Opportunities** - Ideas that could be implemented now
+2. **Future Innovations** - Ideas requiring more development
+3. **Moonshots** - Ambitious, transformative ideas
+4. **Insights & Learnings** - Key realizations from the session
+
+**Next Steps:**
+
+- Which ideas to explore further
+- Recommended follow-up techniques
+- Suggested research areas
+
+## Important Notes
+
+- Maintain energy and momentum throughout the session
+- Defer judgment - all ideas are valid during generation
+- Quantity leads to quality - aim for many ideas
+- Build on ideas collaboratively
+- Document everything - even "silly" ideas can spark breakthroughs
+- Take breaks if energy flags
+- End with clear next actions

package/.bmad-core/tasks/brownfield-create-epic.md

@@ -0,0 +1,160 @@
+# Create Brownfield Epic Task
+
+## Purpose
+
+Create a single epic for smaller brownfield enhancements that don't require the full PRD and Architecture documentation process. This task is for isolated features or modifications that can be completed within a focused scope.
+
+## When to Use This Task
+
+**Use this task when:**
+
+- The enhancement can be completed in 1-3 stories
+- No significant architectural changes are required
+- The enhancement follows existing project patterns
+- Integration complexity is minimal
+- Risk to existing system is low
+
+**Use the full brownfield PRD/Architecture process when:**
+
+- The enhancement requires multiple coordinated stories
+- Architectural planning is needed
+- Significant integration work is required
+- Risk assessment and mitigation planning is necessary
+
+## Instructions
+
+### 1. Project Analysis (Required)
+
+Before creating the epic, gather essential information about the existing project:
+
+**Existing Project Context:**
+
+- [ ] Project purpose and current functionality understood
+- [ ] Existing technology stack identified
+- [ ] Current architecture patterns noted
+- [ ] Integration points with existing system identified
+
+**Enhancement Scope:**
+
+- [ ] Enhancement clearly defined and scoped
+- [ ] Impact on existing functionality assessed
+- [ ] Required integration points identified
+- [ ] Success criteria established
+
+### 2. Epic Creation
+
+Create a focused epic following this structure:
+
+#### Epic Title
+
+{{Enhancement Name}} - Brownfield Enhancement
+
+#### Epic Goal
+
+{{1-2 sentences describing what the epic will accomplish and why it adds value}}
+
+#### Epic Description
+
+**Existing System Context:**
+
+- Current relevant functionality: {{brief description}}
+- Technology stack: {{relevant existing technologies}}
+- Integration points: {{where new work connects to existing system}}
+
+**Enhancement Details:**
+
+- What's being added/changed: {{clear description}}
+- How it integrates: {{integration approach}}
+- Success criteria: {{measurable outcomes}}
+
+#### Stories
+
+List 1-3 focused stories that complete the epic:
+
+1. **Story 1:** {{Story title and brief description}}
+2. **Story 2:** {{Story title and brief description}}
+3. **Story 3:** {{Story title and brief description}}
+
+#### Compatibility Requirements
+
+- [ ] Existing APIs remain unchanged
+- [ ] Database schema changes are backward compatible
+- [ ] UI changes follow existing patterns
+- [ ] Performance impact is minimal
+
+#### Risk Mitigation
+
+- **Primary Risk:** {{main risk to existing system}}
+- **Mitigation:** {{how risk will be addressed}}
+- **Rollback Plan:** {{how to undo changes if needed}}
+
+#### Definition of Done
+
+- [ ] All stories completed with acceptance criteria met
+- [ ] Existing functionality verified through testing
+- [ ] Integration points working correctly
+- [ ] Documentation updated appropriately
+- [ ] No regression in existing features
+
+### 3. Validation Checklist
+
+Before finalizing the epic, ensure:
+
+**Scope Validation:**
+
+- [ ] Epic can be completed in 1-3 stories maximum
+- [ ] No architectural documentation is required
+- [ ] Enhancement follows existing patterns
+- [ ] Integration complexity is manageable
+
+**Risk Assessment:**
+
+- [ ] Risk to existing system is low
+- [ ] Rollback plan is feasible
+- [ ] Testing approach covers existing functionality
+- [ ] Team has sufficient knowledge of integration points
+
+**Completeness Check:**
+
+- [ ] Epic goal is clear and achievable
+- [ ] Stories are properly scoped
+- [ ] Success criteria are measurable
+- [ ] Dependencies are identified
+
+### 4. Handoff to Story Manager
+
+Once the epic is validated, provide this handoff to the Story Manager:
+
+---
+
+**Story Manager Handoff:**
+
+"Please develop detailed user stories for this brownfield epic. Key considerations:
+
+- This is an enhancement to an existing system running {{technology stack}}
+- Integration points: {{list key integration points}}
+- Existing patterns to follow: {{relevant existing patterns}}
+- Critical compatibility requirements: {{key requirements}}
+- Each story must include verification that existing functionality remains intact
+
+The epic should maintain system integrity while delivering {{epic goal}}."
+
+---
+
+## Success Criteria
+
+The epic creation is successful when:
+
+1. Enhancement scope is clearly defined and appropriately sized
+2. Integration approach respects existing system architecture
+3. Risk to existing functionality is minimized
+4. Stories are logically sequenced for safe implementation
+5. Compatibility requirements are clearly specified
+6. Rollback plan is feasible and documented
+
+## Important Notes
+
+- This task is specifically for SMALL brownfield enhancements
+- If the scope grows beyond 3 stories, consider the full brownfield PRD process
+- Always prioritize existing system integrity over new functionality
+- When in doubt about scope or complexity, escalate to full brownfield planning