npm - siesa-agents - Versions diffs - 2.1.78 → 2.1.80 - Mend

siesa-agents 2.1.78 → 2.1.80

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (968) hide show

package/bmad/bmm/workflows/2-plan-workflows/prd/steps/step-03-success.md DELETED Viewed

@@ -1,290 +0,0 @@
----
-name: 'step-03-success'
-description: 'Define comprehensive success criteria covering user, business, and technical success'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-# File References
-thisStepFile: '{workflow_path}/steps/step-03-success.md'
-nextStepFile: '{workflow_path}/steps/step-04-journeys.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/prd.md'
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-# Step 3: Success Criteria Definition
-**Progress: Step 3 of 11** - Next: User Journey Mapping
-## MANDATORY EXECUTION RULES (READ FIRST):
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ ALWAYS treat this as collaborative discovery between PM peers
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on defining what winning looks like for this product
-- 🎯 COLLABORATIVE discovery, not assumption-based goal setting
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-## EXECUTION PROTOCOLS:
-- 🎯 Show your analysis before taking any action
-- ⚠️ Present A/P/C menu after generating success criteria content
-- 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-## COLLABORATION MENUS (A/P/C):
-This step will generate content and present choices:
-- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper insights about success metrics
-- **P (Party Mode)**: Bring multiple perspectives to define comprehensive success criteria
-- **C (Continue)**: Save the content to the document and proceed to next step
-## PROTOCOL INTEGRATION:
-- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
-- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
-- PROTOCOLS always return to this step's A/P/C menu
-- User accepts/rejects protocol changes before proceeding
-## CONTEXT BOUNDARIES:
-- Current document and frontmatter from previous steps are available
-- Executive Summary and Project Classification already exist in document
-- Input documents from step-01 are available (product briefs, research, brainstorming)
-- No additional data files needed for this step
-- Focus on measurable, specific success criteria
-- LEVERAGE existing input documents to inform success criteria
-## YOUR TASK:
-Define comprehensive success criteria that cover user success, business success, and technical success, using input documents as a foundation while allowing user refinement.
-## SUCCESS DISCOVERY SEQUENCE:
-### 1. Begin Success Definition Conversation
-**Check Input Documents for Success Indicators:**
-Analyze product brief, research, and brainstorming documents for success criteria already mentioned.
-**If Input Documents Contain Success Criteria:**
-"Looking at your product brief and research, I see some initial success criteria already defined:
-**From your brief:**
-{{extracted_success_criteria_from_brief}}
-**From research:**
-{{extracted_success_criteria_from_research}}
-**From brainstorming:**
-{{extracted_success_criteria_from_brainstorming}}
-This gives us a great foundation. Let's refine and expand on these initial thoughts:
-**User Success First:**
-Based on what we have, how would you refine these user success indicators:
-- {{refined_user_success_from_documents}}
-- Are there other user success metrics we should consider?
-**What would make a user say 'this was worth it'** beyond what's already captured?"
-**If No Success Criteria in Input Documents:**
-Start with user-centered success:
-"Now that we understand what makes {{project_name}} special, let's define what success looks like.
-**User Success First:**
-- What would make a user say 'this was worth it'?
-- What's the moment where they realize this solved their problem?
-- After using {{project_name}}, what outcome are they walking away with?
-Let's start with the user experience of success."
-### 2. Explore User Success Metrics
-Listen for specific user outcomes and help make them measurable:
-- Guide from vague to specific: NOT "users are happy" → "users complete [key action] within [timeframe]"
-- Ask about emotional success: "When do they feel delighted/relieved/empowered?"
-- Identify success moments: "What's the 'aha!' moment?"
-- Define completion scenarios: "What does 'done' look like for the user?"
-### 3. Define Business Success
-Transition to business metrics:
-"Now let's look at success from the business perspective.
-**Business Success:**
-- What does success look like at 3 months? 12 months?
-- Are we measuring revenue, user growth, engagement, something else?
-- What metric would make you say 'this is working'?
-Help me understand what success means for your business."
-### 4. Challenge Vague Metrics
-Push for specificity on business metrics:
-- "10,000 users" → "What kind of users? Doing what?"
-- "99.9% uptime" → "What's the real concern - data loss? Failed payments?"
-- "Fast" → "How fast, and what specifically needs to be fast?"
-- "Good adoption" → "What percentage adoption by when?"
-### 5. Connect to Product Differentiator
-Tie success metrics back to what makes the product special:
-"So success means users experience [differentiator] and achieve [outcome]. Does that capture it?"
-Adapt success criteria to context:
-- Consumer: User love, engagement, retention
-- B2B: ROI, efficiency, adoption
-- Developer tools: Developer experience, community
-- Regulated: Compliance, safety, validation
-- GovTech: Government compliance, accessibility, procurement
-### 6. Smart Scope Negotiation
-Guide scope definition through success lens:
-"The Scoping Game:
-1. What must work for this to be useful? → MVP
-2. What makes it competitive? → Growth
-3. What's the dream version? → Vision
-Challenge scope creep conversationally:
-- Could that wait until after launch?
-- Is that essential for proving the concept?
-For complex domains, include compliance minimums in MVP."
-### 7. Generate Success Criteria Content
-Prepare the content to append to the document:
-#### Content Structure:
-When saving to document, append these Level 2 and Level 3 sections:
-```markdown
-## Success Criteria
-### User Success
-[Content about user success criteria based on conversation]
-### Business Success
-[Content about business success metrics based on conversation]
-### Technical Success
-[Content about technical success requirements based on conversation]
-### Measurable Outcomes
-[Content about specific measurable outcomes based on conversation]
-## Product Scope
-### MVP - Minimum Viable Product
-[Content about MVP scope based on conversation]
-### Growth Features (Post-MVP)
-[Content about growth features based on conversation]
-### Vision (Future)
-[Content about future vision based on conversation]
-```
-### 8. Present Content and Menu
-Show the generated content and present choices:
-"I've drafted our success criteria and scope definition based on our conversation.
-**Here's what I'll add to the document:**
-[Show the complete markdown content from step 7]
-**What would you like to do?**
-[A] Advanced Elicitation - Let's dive deeper and refine these success metrics
-[P] Party Mode - Bring in different perspectives on success criteria
-[C] Continue - Save success criteria and move to User Journey Mapping (Step 4 of 11)"
-### 9. Handle Menu Selection
-#### If 'A' (Advanced Elicitation):
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current success criteria content
-- Process the enhanced success metrics that come back
-- Ask user: "Accept these improvements to the success criteria? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-#### If 'P' (Party Mode):
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current success criteria
-- Process the collaborative improvements to metrics and scope
-- Ask user: "Accept these changes to the success criteria? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-#### If 'C' (Continue):
-- Append the final content to `{outputFile}`
-- Update frontmatter: add this step to the end of the steps completed array
-- Load `./step-04-journeys.md`
-## APPEND TO DOCUMENT:
-When user selects 'C', append the content directly to the document using the structure from step 7.
-## SUCCESS METRICS:
-✅ User success criteria clearly identified and made measurable
-✅ Business success metrics defined with specific targets
-✅ Success criteria connected to product differentiator
-✅ Scope properly negotiated (MVP, Growth, Vision)
-✅ A/P/C menu presented and handled correctly
-✅ Content properly appended to document when C selected
-## FAILURE MODES:
-❌ Accepting vague success metrics without pushing for specificity
-❌ Not connecting success criteria back to product differentiator
-❌ Missing scope negotiation and leaving it undefined
-❌ Generating content without real user input on what success looks like
-❌ Not presenting A/P/C menu after content generation
-❌ Appending content without user selecting 'C'
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-## DOMAIN CONSIDERATIONS:
-If working in regulated domains (healthcare, fintech, govtech):
-- Include compliance milestones in success criteria
-- Add regulatory approval timelines to MVP scope
-- Consider audit requirements as technical success metrics
-## NEXT STEP:
-After user selects 'C' and content is saved to document, load `./step-04-journeys.md` to map user journeys.
-Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!

package/bmad/bmm/workflows/2-plan-workflows/prd/steps/step-04-journeys.md DELETED Viewed

@@ -1,291 +0,0 @@
----
-name: 'step-04-journeys'
-description: 'Map ALL user types that interact with the system with narrative story-based journeys'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-# File References
-thisStepFile: '{workflow_path}/steps/step-04-journeys.md'
-nextStepFile: '{workflow_path}/steps/step-05-domain.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/prd.md'
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-# Step 4: User Journey Mapping
-**Progress: Step 4 of 11** - Next: Domain Requirements
-## MANDATORY EXECUTION RULES (READ FIRST):
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- ✅ ALWAYS treat this as collaborative discovery between PM peers
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- 💬 FOCUS on mapping ALL user types that interact with the system
-- 🎯 CRITICAL: No journey = no functional requirements = product doesn't exist
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-## EXECUTION PROTOCOLS:
-- 🎯 Show your analysis before taking any action
-- ⚠️ Present A/P/C menu after generating journey content
-- 💾 ONLY save when user chooses C (Continue)
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
-- 🚫 FORBIDDEN to load next step until C is selected
-## COLLABORATION MENUS (A/P/C):
-This step will generate content and present choices:
-- **A (Advanced Elicitation)**: Use discovery protocols to develop deeper journey insights
-- **P (Party Mode)**: Bring multiple perspectives to map comprehensive user journeys
-- **C (Continue)**: Save the content to the document and proceed to next step
-## PROTOCOL INTEGRATION:
-- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
-- When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md
-- PROTOCOLS always return to this step's A/P/C menu
-- User accepts/rejects protocol changes before proceeding
-## CONTEXT BOUNDARIES:
-- Current document and frontmatter from previous steps are available
-- Success criteria and scope already defined
-- Input documents from step-01 are available (product briefs with user personas)
-- Every human interaction with the system needs a journey
-## YOUR TASK:
-Create compelling narrative user journeys that leverage existing personas from product briefs and identify additional user types needed for comprehensive coverage.
-## JOURNEY MAPPING SEQUENCE:
-### 1. Leverage Existing Users & Identify Additional Types
-**Check Input Documents for Existing Personas:**
-Analyze product brief, research, and brainstorming documents for user personas already defined.
-**If User Personas Exist in Input Documents:**
-"I found some fantastic user personas in your product brief! Let me introduce them and see if we need to expand our cast of characters.
-**From your brief:**
-{{extracted_personas_from_brief_with_details}}
-These are great starting points! Their stories already give us insight into what they need from {{project_name}}.
-**Beyond your identified users, who else touches this system?**
-Based on your product type and scope, we might need:
-{{suggest_additional_user_types_based_on_project_context}}
-What additional user types should we consider for this product?"
-**If No Personas in Input Documents:**
-Start with comprehensive user type discovery:
-"Now that we know what success looks like, let's map out ALL the people who will interact with {{project_name}}.
-**Beyond primary users, who else touches this system?**
-Consider:
-- End users (the primary focus)
-- Admins - manage users, settings, content
-- Moderators - review flagged content, enforce rules
-- Support staff - help users, investigate issues
-- API consumers - if dev tool or platform
-- Internal ops - analytics, monitoring, billing
-What user types should we map for this product?"
-### 2. Create Narrative Story-Based Journeys
-For each user type, create compelling narrative journeys that tell their story:
-#### Narrative Journey Creation Process:
-**If Using Existing Persona from Input Documents:**
-"Let's tell {{persona_name}}'s story with {{project_name}}.
-**Their Story So Far:**
-{{persona_backstory_from_brief}}
-**How {{project_name}} Changes Their Life:**
-{{how_product_helps_them}}
-Let's craft their journey narrative - where do we meet them in their story, and how does {{project_name}} help them write their next chapter?"
-**If Creating New Persona:**
-"Let's bring this user type to life with a compelling story.
-**Creating Their Character:**
-- **Name**: Give them a realistic name and personality
-- **Situation**: What's happening in their life/work that creates the need?
-- **Goal**: What do they desperately want to achieve?
-- **Obstacle**: What's standing in their way right now?
-**How {{project_name}} Becomes Their Solution:**
-{{how_product_solves_their_story}}
-Now let's map their journey narrative."
-**Story-Based Journey Mapping:**
-"Let's craft this as a story with our hero (the user) facing challenges and finding solutions through {{project_name}}:
-**Story Structure:**
-- **Opening Scene**: Where and how do we meet them? What's their current pain?
-- **Rising Action**: What steps do they take? What do they discover?
-- **Climax**: The critical moment where {{project_name}} delivers real value
-- **Resolution**: How does their situation improve? What's their new reality?
-**Use This Narrative Format such as this example:**
-```markdown
-**Journey 1: Maria Santos - Reclaiming Her Creative Time**
-Maria is a freelance graphic designer who loves creating beautiful logos but spends hours every week managing client projects, sending invoices, and chasing payments. She feels like she's running a small business instead of doing what she loves. Late one night, while searching for invoicing tools, she discovers CreativeFlow and decides to give it a try.
-The next morning, instead of her usual 30-minute project management routine, she spends 5 minutes setting up her first client in CreativeFlow. The system automatically generates a professional invoice and even suggests follow-up emails based on her communication patterns. When a client asks for a project update, Maria can share a beautiful progress link instead of digging through emails.
-The breakthrough comes when she lands a major corporate client who's impressed by her "organized and professional" project setup. Six months later, Maria has doubled her client base and spends 80% of her time actually designing - exactly what she always wanted.
-```
-### 3. Guide Journey Exploration
-For each journey, facilitate detailed exploration:
-- "What happens at each step specifically?"
-- "What could go wrong here? What's the recovery path?"
-- "What information do they need to see/hear?"
-- "What's their emotional state at each point?"
-- "Where does this journey succeed or fail?"
-### 4. Connect Journeys to Requirements
-After each journey, explicitly state:
-"This journey reveals requirements for:
-- List specific capability areas (e.g., onboarding, meal planning, admin dashboard)
-- Help user see how different journeys create different feature sets"
-### 5. Aim for Comprehensive Coverage
-Guide toward complete journey set:
-- **Primary user** - happy path (core experience)
-- **Primary user** - edge case (different goal, error recovery)
-- **Secondary user** (admin, moderator, support, etc.)
-- **API consumer** (if applicable)
-Ask: "Another journey? We should cover [suggest uncovered user type]"
-### 6. Generate User Journey Content
-Prepare the content to append to the document:
-#### Content Structure:
-When saving to document, append these Level 2 and Level 3 sections:
-```markdown
-## User Journeys
-[All journey narratives based on conversation]
-### Journey Requirements Summary
-[Summary of capabilities revealed by journeys based on conversation]
-```
-### 7. Present Content and Menu
-Show the generated journey content and present choices:
-"I've mapped out the user journeys based on our conversation. Each journey reveals different capabilities needed for {{project_name}}.
-**Here's what I'll add to the document:**
-[Show the complete markdown content from step 6]
-**What would you like to do?**
-[A] Advanced Elicitation - Let's dive deeper into these user journeys
-[P] Party Mode - Bring different perspectives to ensure we have all journeys
-[C] Continue - Save this and move to Domain Requirements (Step 5 of 11)"
-### 8. Handle Menu Selection
-#### If 'A' (Advanced Elicitation):
-- Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml with the current journey content
-- Process the enhanced journey insights that come back
-- Ask user: "Accept these improvements to the user journeys? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-#### If 'P' (Party Mode):
-- Execute {project-root}/_bmad/core/workflows/party-mode/workflow.md with the current journeys
-- Process the collaborative journey improvements and additions
-- Ask user: "Accept these changes to the user journeys? (y/n)"
-- If yes: Update content with improvements, then return to A/P/C menu
-- If no: Keep original content, then return to A/P/C menu
-#### If 'C' (Continue):
-- Append the final content to `{outputFile}`
-- Update frontmatter: add this step name to the end of the steps completed array
-- Load `{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-05-domain.md` (or determine if step is optional based on domain complexity)
-## APPEND TO DOCUMENT:
-When user selects 'C', append the content directly to the document using the structure from step 6.
-## SUCCESS METRICS:
-✅ Existing personas from product briefs leveraged when available
-✅ All user types identified (not just primary users)
-✅ Rich narrative storytelling for each persona and journey
-✅ Complete story-based journey mapping with emotional arc
-✅ Journey requirements clearly connected to capabilities needed
-✅ Minimum 3-4 compelling narrative journeys covering different user types
-✅ A/P/C menu presented and handled correctly
-✅ Content properly appended to document when C selected
-## FAILURE MODES:
-❌ Ignoring existing personas from product briefs
-❌ Only mapping primary user journeys and missing secondary users
-❌ Creating generic journeys without rich persona details and narrative
-❌ Missing emotional storytelling elements that make journeys compelling
-❌ Missing critical decision points and failure scenarios
-❌ Not connecting journeys to required capabilities
-❌ Not having enough journey diversity (admin, support, API, etc.)
-❌ Not presenting A/P/C menu after content generation
-❌ Appending content without user selecting 'C'
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-## JOURNEY TYPES TO ENSURE:
-**Minimum Coverage:**
-1. **Primary User - Success Path**: Core experience journey
-2. **Primary User - Edge Case**: Error recovery, alternative goals
-3. **Admin/Operations User**: Management, configuration, monitoring
-4. **Support/Troubleshooting**: Help, investigation, issue resolution
-5. **API/Integration** (if applicable): Developer/technical user journey
-## NEXT STEP:
-After user selects 'C' and content is saved to document, load `./step-05-domain.md`.
-Remember: Do NOT proceed to step-05 until user explicitly selects 'C' from the A/P/C menu and content is saved!