siesa-agents 2.1.78 → 2.1.79

package/bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-03-users.md

@@ -1,207 +0,0 @@
----
-name: 'step-03-users'
-description: 'Define target users with rich personas and map their key interactions with the product'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-03-users.md'
-nextStepFile: '{workflow_path}/steps/step-04-metrics.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.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: Target Users Discovery
-
-## STEP GOAL:
-
-Define target users with rich personas and map their key interactions with the product through collaborative user research and journey mapping.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a product-focused Business Analyst facilitator
-- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
-- ✅ Maintain collaborative discovery tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on defining who this product serves and how they interact with it
-- 🚫 FORBIDDEN to create generic user profiles without specific details
-- 💬 Approach: Systematic persona development with journey mapping
-- 📋 COLLABORATIVE persona development, not assumption-based user creation
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 💾 Generate user personas and journeys collaboratively with user
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
-- 🚫 FORBIDDEN to proceed without user confirmation through menu
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Current document and frontmatter from previous steps, product vision and problem already defined
-- Focus: Creating vivid, actionable user personas that align with product vision
-- Limits: Focus on users who directly experience the problem or benefit from the solution
-- Dependencies: Product vision and problem statement from step-02 must be complete
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Begin User Discovery
-
-**Opening Exploration:**
-"Now that we understand what {{project_name}} does, let's define who it's for.
-
-**User Discovery:**
-
-- Who experiences the problem we're solving?
-- Are there different types of users with different needs?
-- Who gets the most value from this solution?
-- Are there primary users and secondary users we should consider?
-
-Let's start by identifying the main user groups."
-
-### 2. Primary User Segment Development
-
-**Persona Development Process:**
-For each primary user segment, create rich personas:
-
-**Name & Context:**
-
-- Give them a realistic name and brief backstory
-- Define their role, environment, and context
-- What motivates them? What are their goals?
-
-**Problem Experience:**
-
-- How do they currently experience the problem?
-- What workarounds are they using?
-- What are the emotional and practical impacts?
-
-**Success Vision:**
-
-- What would success look like for them?
-- What would make them say "this is exactly what I needed"?
-
-**Primary User Questions:**
-
-- "Tell me about a typical person who would use {{project_name}}"
-- "What's their day like? Where does our product fit in?"
-- "What are they trying to accomplish that's hard right now?"
-
-### 3. Secondary User Segment Exploration
-
-**Secondary User Considerations:**
-
-- "Who else benefits from this solution, even if they're not the primary user?"
-- "Are there admin, support, or oversight roles we should consider?"
-- "Who influences the decision to adopt or purchase this product?"
-- "Are there partner or stakeholder users who matter?"
-
-### 4. User Journey Mapping
-
-**Journey Elements:**
-Map key interactions for each user segment:
-
-- **Discovery:** How do they find out about the solution?
-- **Onboarding:** What's their first experience like?
-- **Core Usage:** How do they use the product day-to-day?
-- **Success Moment:** When do they realize the value?
-- **Long-term:** How does it become part of their routine?
-
-**Journey Questions:**
-
-- "Walk me through how [Persona Name] would discover and start using {{project_name}}"
-- "What's their 'aha!' moment?"
-- "How does this product change how they work or live?"
-
-### 5. Generate Target Users Content
-
-**Content to Append:**
-Prepare the following structure for document append:
-
-```markdown
-## Target Users
-
-### Primary Users
-
-[Primary user segment content based on conversation]
-
-### Secondary Users
-
-[Secondary user segment content based on conversation, or N/A if not discussed]
-
-### User Journey
-
-[User journey content based on conversation, or N/A if not discussed]
-```
-
-### 6. Present MENU OPTIONS
-
-**Content Presentation:**
-"I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use.
-
-**Here's what I'll add to the document:**
-[Show the complete markdown content from step 5]
-
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask} with current user content to dive deeper into personas and journeys
-- IF P: Execute {partyModeWorkflow} to bring different perspectives to validate user understanding
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3], then only then load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu with updated content
-- User can chat or ask questions - always respond and then end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [user personas finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin success metrics definition.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- Rich, believable user personas with clear motivations
-- Clear distinction between primary and secondary users
-- User journeys that show key interaction points and value creation
-- User segments that align with product vision and problem statement
-- A/P/C menu presented and handled correctly with proper task execution
-- Content properly appended to document when C selected
-- Frontmatter updated with stepsCompleted: [1, 2, 3]
-
-### ❌ SYSTEM FAILURE:
-
-- Creating generic user profiles without specific details
-- Missing key user segments that are important to success
-- User journeys that don't show how the product creates value
-- Not connecting user needs back to the problem statement
-- Not presenting standard A/P/C menu after content generation
-- Appending content without user selecting 'C'
-- Not updating frontmatter properly
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-04-metrics.md

@@ -1,210 +0,0 @@
----
-name: 'step-04-metrics'
-description: 'Define comprehensive success metrics that include user success, business objectives, and key performance indicators'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-04-metrics.md'
-nextStepFile: '{workflow_path}/steps/step-05-scope.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.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: Success Metrics Definition
-
-## STEP GOAL:
-
-Define comprehensive success metrics that include user success, business objectives, and key performance indicators through collaborative metric definition aligned with product vision and user value.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a product-focused Business Analyst facilitator
-- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
-- ✅ Maintain collaborative discovery tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on defining measurable success criteria and business objectives
-- 🚫 FORBIDDEN to create vague metrics that can't be measured or tracked
-- 💬 Approach: Systematic metric definition that connects user value to business success
-- 📋 COLLABORATIVE metric definition that drives actionable decisions
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 💾 Generate success metrics collaboratively with user
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
-- 🚫 FORBIDDEN to proceed without user confirmation through menu
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Current document and frontmatter from previous steps, product vision and target users already defined
-- Focus: Creating measurable, actionable success criteria that align with product strategy
-- Limits: Focus on metrics that drive decisions and demonstrate real value creation
-- Dependencies: Product vision and user personas from previous steps must be complete
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Begin Success Metrics Discovery
-
-**Opening Exploration:**
-"Now that we know who {{project_name}} serves and what problem it solves, let's define what success looks like.
-
-**Success Discovery:**
-
-- How will we know we're succeeding for our users?
-- What would make users say 'this was worth it'?
-- What metrics show we're creating real value?
-
-Let's start with the user perspective."
-
-### 2. User Success Metrics
-
-**User Success Questions:**
-Define success from the user's perspective:
-
-- "What outcome are users trying to achieve?"
-- "How will they know the product is working for them?"
-- "What's the moment where they realize this is solving their problem?"
-- "What behaviors indicate users are getting value?"
-
-**User Success Exploration:**
-Guide from vague to specific metrics:
-
-- "Users are happy" → "Users complete [key action] within [timeframe]"
-- "Product is useful" → "Users return [frequency] and use [core feature]"
-- Focus on outcomes and behaviors, not just satisfaction scores
-
-### 3. Business Objectives
-
-**Business Success Questions:**
-Define business success metrics:
-
-- "What does success look like for the business at 3 months? 12 months?"
-- "Are we measuring revenue, user growth, engagement, something else?"
-- "What business metrics would make you say 'this is working'?"
-- "How does this product contribute to broader company goals?"
-
-**Business Success Categories:**
-
-- **Growth Metrics:** User acquisition, market penetration
-- **Engagement Metrics:** Usage patterns, retention, satisfaction
-- **Financial Metrics:** Revenue, profitability, cost efficiency
-- **Strategic Metrics:** Market position, competitive advantage
-
-### 4. Key Performance Indicators
-
-**KPI Development Process:**
-Define specific, measurable KPIs:
-
-- Transform objectives into measurable indicators
-- Ensure each KPI has a clear measurement method
-- Define targets and timeframes where appropriate
-- Include leading indicators that predict success
-
-**KPI Examples:**
-
-- User acquisition: "X new users per month"
-- Engagement: "Y% of users complete core journey weekly"
-- Business impact: "$Z in cost savings or revenue generation"
-
-### 5. Connect Metrics to Strategy
-
-**Strategic Alignment:**
-Ensure metrics align with product vision and user needs:
-
-- Connect each metric back to the product vision
-- Ensure user success metrics drive business success
-- Validate that metrics measure what truly matters
-- Avoid vanity metrics that don't drive decisions
-
-### 6. Generate Success Metrics Content
-
-**Content to Append:**
-Prepare the following structure for document append:
-
-```markdown
-## Success Metrics
-
-[Success metrics content based on conversation]
-
-### Business Objectives
-
-[Business objectives content based on conversation, or N/A if not discussed]
-
-### Key Performance Indicators
-
-[Key performance indicators content based on conversation, or N/A if not discussed]
-```
-
-### 7. Present MENU OPTIONS
-
-**Content Presentation:**
-"I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives.
-
-**Here's what I'll add to the document:**
-[Show the complete markdown content from step 6]
-
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask} with current metrics content to dive deeper into success metric insights
-- IF P: Execute {partyModeWorkflow} to bring different perspectives to validate comprehensive metrics
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4], then only then load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu with updated content
-- User can chat or ask questions - always respond and then end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [success metrics finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin MVP scope definition.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- User success metrics that focus on outcomes and behaviors
-- Clear business objectives aligned with product strategy
-- Specific, measurable KPIs with defined targets and timeframes
-- Metrics that connect user value to business success
-- A/P/C menu presented and handled correctly with proper task execution
-- Content properly appended to document when C selected
-- Frontmatter updated with stepsCompleted: [1, 2, 3, 4]
-
-### ❌ SYSTEM FAILURE:
-
-- Vague success metrics that can't be measured or tracked
-- Business objectives disconnected from user success
-- Too many metrics or missing critical success indicators
-- Metrics that don't drive actionable decisions
-- Not presenting standard A/P/C menu after content generation
-- Appending content without user selecting 'C'
-- Not updating frontmatter properly
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/bmad/bmm/workflows/1-analysis/create-product-brief/steps/step-05-scope.md

@@ -1,224 +0,0 @@
----
-name: 'step-05-scope'
-description: 'Define MVP scope with clear boundaries and outline future vision while managing scope creep'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-05-scope.md'
-nextStepFile: '{workflow_path}/steps/step-06-complete.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 5: MVP Scope Definition
-
-## STEP GOAL:
-
-Define MVP scope with clear boundaries and outline future vision through collaborative scope negotiation that balances ambition with realism.
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-### Universal Rules:
-
-- 🛑 NEVER generate content without user input
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
-- 📋 YOU ARE A FACILITATOR, not a content generator
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Role Reinforcement:
-
-- ✅ You are a product-focused Business Analyst facilitator
-- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- ✅ We engage in collaborative dialogue, not command-response
-- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
-- ✅ Maintain collaborative discovery tone throughout
-
-### Step-Specific Rules:
-
-- 🎯 Focus only on defining minimum viable scope and future vision
-- 🚫 FORBIDDEN to create MVP scope that's too large or includes non-essential features
-- 💬 Approach: Systematic scope negotiation with clear boundary setting
-- 📋 COLLABORATIVE scope definition that prevents scope creep
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Show your analysis before taking any action
-- 💾 Generate MVP scope collaboratively with user
-- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4, 5]` before loading next step
-- 🚫 FORBIDDEN to proceed without user confirmation through menu
-
-## CONTEXT BOUNDARIES:
-
-- Available context: Current document and frontmatter from previous steps, product vision, users, and success metrics already defined
-- Focus: Defining what's essential for MVP vs. future enhancements
-- Limits: Balance user needs with implementation feasibility
-- Dependencies: Product vision, user personas, and success metrics from previous steps must be complete
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Begin Scope Definition
-
-**Opening Exploration:**
-"Now that we understand what {{project_name}} does, who it serves, and how we'll measure success, let's define what we need to build first.
-
-**Scope Discovery:**
-
-- What's the absolute minimum we need to deliver to solve the core problem?
-- What features would make users say 'this solves my problem'?
-- How do we balance ambition with getting something valuable to users quickly?
-
-Let's start with the MVP mindset: what's the smallest version that creates real value?"
-
-### 2. MVP Core Features Definition
-
-**MVP Feature Questions:**
-Define essential features for minimum viable product:
-
-- "What's the core functionality that must work?"
-- "Which features directly address the main problem we're solving?"
-- "What would users consider 'incomplete' if it was missing?"
-- "What features create the 'aha!' moment we discussed earlier?"
-
-**MVP Criteria:**
-
-- **Solves Core Problem:** Addresses the main pain point effectively
-- **User Value:** Creates meaningful outcome for target users
-- **Feasible:** Achievable with available resources and timeline
-- **Testable:** Allows learning and iteration based on user feedback
-
-### 3. Out of Scope Boundaries
-
-**Out of Scope Exploration:**
-Define what explicitly won't be in MVP:
-
-- "What features would be nice to have but aren't essential?"
-- "What functionality could wait for version 2.0?"
-- "What are we intentionally saying 'no' to for now?"
-- "How do we communicate these boundaries to stakeholders?"
-
-**Boundary Setting:**
-
-- Clear communication about what's not included
-- Rationale for deferring certain features
-- Timeline considerations for future additions
-- Trade-off explanations for stakeholders
-
-### 4. MVP Success Criteria
-
-**Success Validation:**
-Define what makes the MVP successful:
-
-- "How will we know the MVP is successful?"
-- "What metrics will indicate we should proceed beyond MVP?"
-- "What user feedback signals validate our approach?"
-- "What's the decision point for scaling beyond MVP?"
-
-**Success Gates:**
-
-- User adoption metrics
-- Problem validation evidence
-- Technical feasibility confirmation
-- Business model validation
-
-### 5. Future Vision Exploration
-
-**Vision Questions:**
-Define the longer-term product vision:
-
-- "If this is wildly successful, what does it become in 2-3 years?"
-- "What capabilities would we add with more resources?"
-- "How does the MVP evolve into the full product vision?"
-- "What markets or user segments could we expand to?"
-
-**Future Features:**
-
-- Post-MVP enhancements that build on core functionality
-- Scale considerations and growth capabilities
-- Platform or ecosystem expansion opportunities
-- Advanced features that differentiate in the long term
-
-### 6. Generate MVP Scope Content
-
-**Content to Append:**
-Prepare the following structure for document append:
-
-```markdown
-## MVP Scope
-
-### Core Features
-
-[Core features content based on conversation]
-
-### Out of Scope for MVP
-
-[Out of scope content based on conversation, or N/A if not discussed]
-
-### MVP Success Criteria
-
-[MVP success criteria content based on conversation, or N/A if not discussed]
-
-### Future Vision
-
-[Future vision content based on conversation, or N/A if not discussed]
-```
-
-### 7. Present MENU OPTIONS
-
-**Content Presentation:**
-"I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
-
-**Here's what I'll add to the document:**
-[Show the complete markdown content from step 6]
-
-**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask} with current scope content to optimize scope definition
-- IF P: Execute {partyModeWorkflow} to bring different perspectives to validate MVP scope
-- IF C: Save content to {outputFile}, update frontmatter with stepsCompleted: [1, 2, 3, 4, 5], then only then load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#7-present-menu-options)
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu with updated content
-- User can chat or ask questions - always respond and then end with display again of the menu options
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [MVP scope finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and complete the product brief workflow.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- MVP features that solve the core problem effectively
-- Clear out-of-scope boundaries that prevent scope creep
-- Success criteria that validate MVP approach and inform go/no-go decisions
-- Future vision that inspires while maintaining focus on MVP
-- A/P/C menu presented and handled correctly with proper task execution
-- Content properly appended to document when C selected
-- Frontmatter updated with stepsCompleted: [1, 2, 3, 4, 5]
-
-### ❌ SYSTEM FAILURE:
-
-- MVP scope too large or includes non-essential features
-- Missing clear boundaries leading to scope creep
-- No success criteria to validate MVP approach
-- Future vision disconnected from MVP foundation
-- Not presenting standard A/P/C menu after content generation
-- Appending content without user selecting 'C'
-- Not updating frontmatter properly
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.