siesa-agents 2.1.40 → 2.1.42

package/bmad/bmm/workflows/4-implementation/create-story/steps/step-01-determine-story.md

@@ -1,85 +1,85 @@
----
-name: 'step-01-determine-story'
-description: 'Determine which story to work on next'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-01-determine-story.md'
-nextStepFile: '{workflow_path}/steps/step-02-analyze.md'
-workflowFile: '{workflow_path}/workflow.md'
-
-# Variables
-sprint_status: '{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 1: Determine Target Story
-
-## STEP GOAL:
-To identify exactly which user story needs to be created, either from user input or by auto-discovering the next backlog item from the sprint status.
-
-## 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
-
-### Step-Specific Rules:
-- 🎯 Focus only on identifying the story ID (e.g., "1-2") and Title
-- 🚫 FORBIDDEN to analyze deep context yet
-- 💬 Ask strictly for story ID if not found automatically
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Identify story to create
-- 💾 Set {{story_id}}, {{epic_num}}, {{story_num}}, {{story_key}} memory variables
-- 📖 No file output in this step, only memory state
-
-## INSTRUCTIONS:
-
-### 1. Check User Input
-Check if the user provided a story path or ID (e.g., "1-2-user-auth").
-- IF YES: Parse it, set {{story_id}} variables, and [GO TO Section 4]
-- IF NO: Proceed to Section 2
-
-### 2. Auto-Discovery
-Check if `{sprint_status}` file exists.
-- IF NO: Display options to user:
-  1. Run `sprint-planning` (Recommended)
-  2. Enter specific epic-story number
-  3. Quit
-  [Wait for selection]
-
-- IF YES: Load and read `{sprint_status}`.
-  - Parse `development_status` section.
-  - Find FIRST story where status is "backlog".
-  - IF NONE FOUND: Display "No backlog stories found" and HALT.
-  - IF FOUND: Extract `epic_num`, `story_num`, `story_title`.
-  - Set variables.
-
-### 3. Verify Epic Status
-Check the status of the Epic {{epic_num}} in `sprint_status`.
-- If "done": HALT. Cannot add to done epic.
-- If "backlog": Update to "in-progress" in `sprint_status` (save file).
-- If "in-progress": Continue.
-
-### 4. Present MENU OPTIONS
-
-Display: "**Target Story Identified: {{story_id}} - {{story_title}}**"
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Analysis"
-
-#### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Load, read entire file, then execute {nextStepFile}
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
+---
+name: 'step-01-determine-story'
+description: 'Determine which story to work on next'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-01-determine-story.md'
+nextStepFile: '{workflow_path}/steps/step-02-analyze.md'
+workflowFile: '{workflow_path}/workflow.md'
+
+# Variables
+sprint_status: '{implementation_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 1: Determine Target Story
+
+## STEP GOAL:
+To identify exactly which user story needs to be created, either from user input or by auto-discovering the next backlog item from the sprint status.
+
+## 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
+
+### Step-Specific Rules:
+- 🎯 Focus only on identifying the story ID (e.g., "1-2") and Title
+- 🚫 FORBIDDEN to analyze deep context yet
+- 💬 Ask strictly for story ID if not found automatically
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Identify story to create
+- 💾 Set {{story_id}}, {{epic_num}}, {{story_num}}, {{story_key}} memory variables
+- 📖 No file output in this step, only memory state
+
+## INSTRUCTIONS:
+
+### 1. Check User Input
+Check if the user provided a story path or ID (e.g., "1-2-user-auth").
+- IF YES: Parse it, set {{story_id}} variables, and [GO TO Section 4]
+- IF NO: Proceed to Section 2
+
+### 2. Auto-Discovery
+Check if `{sprint_status}` file exists.
+- IF NO: Display options to user:
+  1. Run `sprint-planning` (Recommended)
+  2. Enter specific epic-story number
+  3. Quit
+  [Wait for selection]
+
+- IF YES: Load and read `{sprint_status}`.
+  - Parse `development_status` section.
+  - Find FIRST story where status is "backlog".
+  - IF NONE FOUND: Display "No backlog stories found" and HALT.
+  - IF FOUND: Extract `epic_num`, `story_num`, `story_title`.
+  - Set variables.
+
+### 3. Verify Epic Status
+Check the status of the Epic {{epic_num}} in `sprint_status`.
+- If "done": HALT. Cannot add to done epic.
+- If "backlog": Update to "in-progress" in `sprint_status` (save file).
+- If "in-progress": Continue.
+
+### 4. Present MENU OPTIONS
+
+Display: "**Target Story Identified: {{story_id}} - {{story_title}}**"
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Analysis"
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: Load, read entire file, then execute {nextStepFile}
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'

package/bmad/bmm/workflows/4-implementation/create-story/steps/step-02-analyze.md

@@ -1,67 +1,67 @@
----
-name: 'step-02-analyze'
-description: 'Load and analyze core artifacts'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-02-analyze.md'
-nextStepFile: '{workflow_path}/steps/step-03-architecture.md'
-workflowFile: '{workflow_path}/workflow.md'
-
-# Variables
-output_folder: '{implementation_artifacts}'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 2: Load and Analyze Core Artifacts
-
-## STEP GOAL:
-To gather all necessary context from Epics, previous stories, and Git history to build a solid foundation for the new story.
-
-## EXECUTION PROTOCOLS:
-- 🎯 Deep analysis of available artifacts
-- 💾 Extract key requirements into memory/context
-
-## INSTRUCTIONS:
-
-### 1. Discover Inputs
-Identify available files matching patterns:
-- Epics: `{output_folder}/*epic*.md`
-- PRD: `{output_folder}/*prd*.md`
-- Architecture: `{output_folder}/*architecture*.md`
-- Review findings.
-
-### 2. Epic Analysis
-Load the relevant Epic file ({{epic_num}}).
-- Extract "Epic Objectives" and "Business Value".
-- Extract THIS specific story's requirements (User Story, AC).
-- Extract technical constraints listed in the Epic.
-
-### 3. Previous Story Intelligence
-Check if {{story_num}} > 1.
-- IF YES: Look for `{{story_dir}}/{{epic_num}}-{{previous_story_num}}-*.md`.
-- IF FOUND: Read it. Extract "Dev Notes", "Learnings", "Testing Approaches".
-
-### 4. Git Intelligence
-Check if this is a git repo.
-- IF YES: Get last 5 commit titles.
-- Analyze patterns relevant to this story (naming, file locations).
-
-### 5. Present MENU OPTIONS
-
-Display: "**Artifact Analysis Complete.**"
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Architecture"
-
-#### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Load, read entire file, then execute {nextStepFile}
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
+---
+name: 'step-02-analyze'
+description: 'Load and analyze core artifacts'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-02-analyze.md'
+nextStepFile: '{workflow_path}/steps/step-03-architecture.md'
+workflowFile: '{workflow_path}/workflow.md'
+
+# Variables
+output_folder: '{implementation_artifacts}'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 2: Load and Analyze Core Artifacts
+
+## STEP GOAL:
+To gather all necessary context from Epics, previous stories, and Git history to build a solid foundation for the new story.
+
+## EXECUTION PROTOCOLS:
+- 🎯 Deep analysis of available artifacts
+- 💾 Extract key requirements into memory/context
+
+## INSTRUCTIONS:
+
+### 1. Discover Inputs
+Identify available files matching patterns:
+- Epics: `{output_folder}/*epic*.md`
+- PRD: `{output_folder}/*prd*.md`
+- Architecture: `{output_folder}/*architecture*.md`
+- Review findings.
+
+### 2. Epic Analysis
+Load the relevant Epic file ({{epic_num}}).
+- Extract "Epic Objectives" and "Business Value".
+- Extract THIS specific story's requirements (User Story, AC).
+- Extract technical constraints listed in the Epic.
+
+### 3. Previous Story Intelligence
+Check if {{story_num}} > 1.
+- IF YES: Look for `{{story_dir}}/{{epic_num}}-{{previous_story_num}}-*.md`.
+- IF FOUND: Read it. Extract "Dev Notes", "Learnings", "Testing Approaches".
+
+### 4. Git Intelligence
+Check if this is a git repo.
+- IF YES: Get last 5 commit titles.
+- Analyze patterns relevant to this story (naming, file locations).
+
+### 5. Present MENU OPTIONS
+
+Display: "**Artifact Analysis Complete.**"
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Architecture"
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: Load, read entire file, then execute {nextStepFile}
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'

package/bmad/bmm/workflows/4-implementation/create-story/steps/step-03-architecture.md

@@ -1,71 +1,71 @@
----
-name: 'step-03-architecture'
-description: 'Architecture analysis and tech stack validation'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-03-architecture.md'
-nextStepFile: '{workflow_path}/steps/step-04-web-research.md'
-workflowFile: '{workflow_path}/workflow.md'
-
-# Variables
-output_folder: '{implementation_artifacts}'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 3: Architecture Intelligence & Compliance
-
-## STEP GOAL:
-To extract architectural constraints and SPECIFICALLY detect Frontend/UI requirements to enforce `siesa-ui-kit` usage.
-
-## EXECUTION PROTOCOLS:
-- 🎯 Analyze architecture documents
-- 🕵️ Detect UI/Frontend requirements in the current story
-- 💾 Set {{has_ui_component}} flag and {{siesa_instructions}}
-
-## INSTRUCTIONS:
-
-### 1. Load Architecture
-Load `{output_folder}/*architecture*.md`.
-- Analyze: Technical Stack, Code Structure, API Patterns, Database Schemas.
-
-### 2. UI/Frontend Detection (CRITICAL)
-Analyze the Story Requirements (from previous step) and Architecture.
-- ASK: "Does this story involve creating views, components, or user interfaces?"
-- LOOK FOR keywords: "Page", "View", "Button", "Form", "Screen", "UI", "Frontend", "React", "Vue", "Component".
-
-### 3. Siesa UI Kit Enforcement
-IF {{has_ui_component}} IS TRUE:
-- **MANDATE**: Store the following requirements for the final story:
-  1.  **Installation**: `npm install siesa-ui-kit` for installation.
-  2.  **Usage**: "You MUST use components and patterns from `siesa-ui-kit` for all UI elements."
-  3.  **Pattern**: "Do not build custom UI components if a `siesa-ui-kit` equivalent exists."
-- Log: "✅ UI Story Detected - siesa-ui-kit requirements injected."
-
-IF {{has_ui_component}} IS FALSE:
-- Log: "ℹ️ No specific UI requirements detected. Standard backend/logic rules apply."
-
-### 4. Extract Other Constraints
-- Security: Auth/Authz rules.
-- Performance: Caching, specific queries.
-- Testing: Standards for this module.
-
-### 5. Present MENU OPTIONS
-
-Display: "**Architecture & UI Analysis Complete.**"
-Display: "**UI Detected:** {{has_ui_component}}"
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Research"
-
-#### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Load, read entire file, then execute {nextStepFile}
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
+---
+name: 'step-03-architecture'
+description: 'Architecture analysis and tech stack validation'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-03-architecture.md'
+nextStepFile: '{workflow_path}/steps/step-04-web-research.md'
+workflowFile: '{workflow_path}/workflow.md'
+
+# Variables
+output_folder: '{implementation_artifacts}'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 3: Architecture Intelligence & Compliance
+
+## STEP GOAL:
+To extract architectural constraints and SPECIFICALLY detect Frontend/UI requirements to enforce `siesa-ui-kit` usage.
+
+## EXECUTION PROTOCOLS:
+- 🎯 Analyze architecture documents
+- 🕵️ Detect UI/Frontend requirements in the current story
+- 💾 Set {{has_ui_component}} flag and {{siesa_instructions}}
+
+## INSTRUCTIONS:
+
+### 1. Load Architecture
+Load `{output_folder}/*architecture*.md`.
+- Analyze: Technical Stack, Code Structure, API Patterns, Database Schemas.
+
+### 2. UI/Frontend Detection (CRITICAL)
+Analyze the Story Requirements (from previous step) and Architecture.
+- ASK: "Does this story involve creating views, components, or user interfaces?"
+- LOOK FOR keywords: "Page", "View", "Button", "Form", "Screen", "UI", "Frontend", "React", "Vue", "Component".
+
+### 3. Siesa UI Kit Enforcement
+IF {{has_ui_component}} IS TRUE:
+- **MANDATE**: Store the following requirements for the final story:
+  1.  **Installation**: `npm install siesa-ui-kit` for installation.
+  2.  **Usage**: "You MUST use components and patterns from `siesa-ui-kit` for all UI elements."
+  3.  **Pattern**: "Do not build custom UI components if a `siesa-ui-kit` equivalent exists."
+- Log: "✅ UI Story Detected - siesa-ui-kit requirements injected."
+
+IF {{has_ui_component}} IS FALSE:
+- Log: "ℹ️ No specific UI requirements detected. Standard backend/logic rules apply."
+
+### 4. Extract Other Constraints
+- Security: Auth/Authz rules.
+- Performance: Caching, specific queries.
+- Testing: Standards for this module.
+
+### 5. Present MENU OPTIONS
+
+Display: "**Architecture & UI Analysis Complete.**"
+Display: "**UI Detected:** {{has_ui_component}}"
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Research"
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: Load, read entire file, then execute {nextStepFile}
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'

package/bmad/bmm/workflows/4-implementation/create-story/steps/step-04-web-research.md

@@ -1,58 +1,58 @@
----
-name: 'step-04-web-research'
-description: 'Web research for latest technical specifics'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-04-web-research.md'
-nextStepFile: '{workflow_path}/steps/step-05-create-file.md'
-workflowFile: '{workflow_path}/workflow.md'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 4: Web Research & Verification
-
-## STEP GOAL:
-To ensure the developer has the absolute latest information on libraries (including `siesa-ui-kit` if relevant) and APIs.
-
-## EXECUTION PROTOCOLS:
-- 🎯 Research latest versions and best practices
-- 💾 Summarize technical specifics for the story
-
-## INSTRUCTIONS:
-
-### 1. Identify Research Targets
-Based on Architecture and Story:
-- List critical libraries/frameworks.
-- **Siesa Check**: If {{has_ui_component}} is TRUE, include `siesa-ui-kit` in research list (check for specific version requirements if public, or internal docs).
-
-### 2. Execute Research
-For each target:
-- Find latest stable version.
-- check for breaking changes relevant to this story.
-- Find specific documentation links for required components.
-
-### 3. Synthesize Findings
-Create a "Latest Tech Info" block:
-- "Library X v.Y.Z recommended"
-- "Specific API endpoint documentation: [Link]"
-- "Security alerts: [Details]"
-
-### 4. Present MENU OPTIONS
-
-Display: "**Tech Research Complete.**"
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Creation"
-
-#### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: Load, read entire file, then execute {nextStepFile}
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
+---
+name: 'step-04-web-research'
+description: 'Web research for latest technical specifics'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-04-web-research.md'
+nextStepFile: '{workflow_path}/steps/step-05-create-file.md'
+workflowFile: '{workflow_path}/workflow.md'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 4: Web Research & Verification
+
+## STEP GOAL:
+To ensure the developer has the absolute latest information on libraries (including `siesa-ui-kit` if relevant) and APIs.
+
+## EXECUTION PROTOCOLS:
+- 🎯 Research latest versions and best practices
+- 💾 Summarize technical specifics for the story
+
+## INSTRUCTIONS:
+
+### 1. Identify Research Targets
+Based on Architecture and Story:
+- List critical libraries/frameworks.
+- **Siesa Check**: If {{has_ui_component}} is TRUE, include `siesa-ui-kit` in research list (check for specific version requirements if public, or internal docs).
+
+### 2. Execute Research
+For each target:
+- Find latest stable version.
+- check for breaking changes relevant to this story.
+- Find specific documentation links for required components.
+
+### 3. Synthesize Findings
+Create a "Latest Tech Info" block:
+- "Library X v.Y.Z recommended"
+- "Specific API endpoint documentation: [Link]"
+- "Security alerts: [Details]"
+
+### 4. Present MENU OPTIONS
+
+Display: "**Tech Research Complete.**"
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Creation"
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: Load, read entire file, then execute {nextStepFile}
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'