siesa-agents 2.1.40 → 2.1.41

package/bmad/bmm/workflows/4-implementation/create-story/steps/step-05-create-file.md

@@ -1,76 +1,76 @@
----
-name: 'step-05-create-file'
-description: 'Create comprehensive story file'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-05-create-file.md'
-nextStepFile: '{workflow_path}/steps/step-06-finalize.md'
-workflowFile: '{workflow_path}/workflow.md'
-templateFile: '{workflow_path}/template.md'
-
-# Variables
-story_dir: '{implementation_artifacts}'
-
-# Task References
-advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Step 5: Create Ultimate Story File
-
-## STEP GOAL:
-To generate the final `.md` story file containing ALL gathered context, requirements, and specifically the `siesa-ui-kit` mandates if applicable.
-
-## EXECUTION PROTOCOLS:
-- 🎯 Assemble the story file
-- 💾 Write to `{{story_dir}}/{{story_key}}.md`
-
-## INSTRUCTIONS:
-
-### 1. Initialize File
-Create/Overwrite: `{{story_dir}}/{{story_key}}.md`.
-
-### 2. Write Header & Status
-- Title: Story {{epic_num}}.{{story_num}}: {{story_title}}
-- Status: **ready-for-dev**
-
-### 3. Write Story & AC
-- User Story Format (As a... I want... So that...)
-- Detailed Acceptance Criteria (from Step 2).
-
-### 4. Write Technical Implementation Guide (CRITICAL)
-- Architecture Patterns (from Step 3).
-- **Tech Stack & Libraries**:
-  - List all required libraries.
-  - **UI MANDATE**: IF {{has_ui_component}} is TRUE:
-    ```markdown
-    ### 🎨 UI Implementation Requirements (MANDATORY)
-    - **Library**: `siesa-ui-kit`
-    - **Install**: `npm install siesa-ui-kit` (Ensure dependency is present)
-    - **Usage**: You MUST use `siesa-ui-kit` components for all UI elements.
-    - **Constraint**: Do not create custom components if a Kit equivalent exists.
-    ```
-- Testing Requirements.
-- File Structure requirements.
-
-### 5. Write Contextual Intelligence
-- Previous Story Learnings (from Step 2).
-- Git History Context (from Step 2).
-- Latest Web Research (from Step 4).
-
-### 6. Present MENU OPTIONS
-
-Display: "**Story File Created: {{story_key}}.md**"
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Finalize"
-
-#### 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-05-create-file'
+description: 'Create comprehensive story file'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-05-create-file.md'
+nextStepFile: '{workflow_path}/steps/step-06-finalize.md'
+workflowFile: '{workflow_path}/workflow.md'
+templateFile: '{workflow_path}/template.md'
+
+# Variables
+story_dir: '{implementation_artifacts}'
+
+# Task References
+advancedElicitationTask: '{project-root}/_bmad/core/tasks/advanced-elicitation.xml'
+partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+---
+
+# Step 5: Create Ultimate Story File
+
+## STEP GOAL:
+To generate the final `.md` story file containing ALL gathered context, requirements, and specifically the `siesa-ui-kit` mandates if applicable.
+
+## EXECUTION PROTOCOLS:
+- 🎯 Assemble the story file
+- 💾 Write to `{{story_dir}}/{{story_key}}.md`
+
+## INSTRUCTIONS:
+
+### 1. Initialize File
+Create/Overwrite: `{{story_dir}}/{{story_key}}.md`.
+
+### 2. Write Header & Status
+- Title: Story {{epic_num}}.{{story_num}}: {{story_title}}
+- Status: **ready-for-dev**
+
+### 3. Write Story & AC
+- User Story Format (As a... I want... So that...)
+- Detailed Acceptance Criteria (from Step 2).
+
+### 4. Write Technical Implementation Guide (CRITICAL)
+- Architecture Patterns (from Step 3).
+- **Tech Stack & Libraries**:
+  - List all required libraries.
+  - **UI MANDATE**: IF {{has_ui_component}} is TRUE:
+    ```markdown
+    ### 🎨 UI Implementation Requirements (MANDATORY)
+    - **Library**: `siesa-ui-kit`
+    - **Install**: `npm install siesa-ui-kit` (Ensure dependency is present)
+    - **Usage**: You MUST use `siesa-ui-kit` components for all UI elements.
+    - **Constraint**: Do not create custom components if a Kit equivalent exists.
+    ```
+- Testing Requirements.
+- File Structure requirements.
+
+### 5. Write Contextual Intelligence
+- Previous Story Learnings (from Step 2).
+- Git History Context (from Step 2).
+- Latest Web Research (from Step 4).
+
+### 6. Present MENU OPTIONS
+
+Display: "**Story File Created: {{story_key}}.md**"
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Finalize"
+
+#### 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-06-finalize.md

@@ -1,66 +1,66 @@
----
-name: 'step-06-finalize'
-description: 'Update sprint status and finalize'
-
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
-
-# File References
-thisStepFile: '{workflow_path}/steps/step-06-finalize.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 6: Finalize & Handover
-
-## STEP GOAL:
-To update the project tracking (sprint status) and confirm the story is ready for development.
-
-## EXECUTION PROTOCOLS:
-- 🎯 Update sprint-status.yaml
-- 🏁 Complete workflow
-
-## INSTRUCTIONS:
-
-### 1. Update Sprint Status
-Load `{sprint_status}`.
-- Find `development_status` for {{story_key}}.
-- Update status from "backlog" to "ready-for-dev".
-- Save file.
-
-### 2. Validation (Optional)
-Run validation check on the generated story file (structure check).
-
-### 3. Final Report
-Display:
-```markdown
-**🎯 TARGET LOCKED: Story {{story_key}} Ready for Dev!**
-
-**Details:**
-- File: {{story_file}}
-- Status: ready-for-dev
-- UI Mode: {{has_ui_component}} (siesa-ui-kit required: {{has_ui_component}})
-
-**Next Action:**
-- Run `dev-story` to begin implementation.
-```
-
-### 4. Present MENU OPTIONS
-
-Display: "**Workflow Complete.**"
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Finish"
-
-#### Menu Handling Logic:
-- IF A: Execute {advancedElicitationTask}
-- IF P: Execute {partyModeWorkflow}
-- IF C: EXIT workflow (Process Complete)
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed/exit when user selects 'C'
+---
+name: 'step-06-finalize'
+description: 'Update sprint status and finalize'
+
+# Path Definitions
+workflow_path: '{project-root}/_bmad/bmm/workflows/4-implementation/create-story'
+
+# File References
+thisStepFile: '{workflow_path}/steps/step-06-finalize.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 6: Finalize & Handover
+
+## STEP GOAL:
+To update the project tracking (sprint status) and confirm the story is ready for development.
+
+## EXECUTION PROTOCOLS:
+- 🎯 Update sprint-status.yaml
+- 🏁 Complete workflow
+
+## INSTRUCTIONS:
+
+### 1. Update Sprint Status
+Load `{sprint_status}`.
+- Find `development_status` for {{story_key}}.
+- Update status from "backlog" to "ready-for-dev".
+- Save file.
+
+### 2. Validation (Optional)
+Run validation check on the generated story file (structure check).
+
+### 3. Final Report
+Display:
+```markdown
+**🎯 TARGET LOCKED: Story {{story_key}} Ready for Dev!**
+
+**Details:**
+- File: {{story_file}}
+- Status: ready-for-dev
+- UI Mode: {{has_ui_component}} (siesa-ui-kit required: {{has_ui_component}})
+
+**Next Action:**
+- Run `dev-story` to begin implementation.
+```
+
+### 4. Present MENU OPTIONS
+
+Display: "**Workflow Complete.**"
+Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Finish"
+
+#### Menu Handling Logic:
+- IF A: Execute {advancedElicitationTask}
+- IF P: Execute {partyModeWorkflow}
+- IF C: EXIT workflow (Process Complete)
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed/exit when user selects 'C'

package/bmad/bmm/workflows/4-implementation/create-story/template.md

@@ -1,49 +1,49 @@
-# Story {{epic_num}}.{{story_num}}: {{story_title}}
-
-Status: ready-for-dev
-
-<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
-
-## Story
-
-As a {{role}},
-I want {{action}},
-so that {{benefit}}.
-
-## Acceptance Criteria
-
-1. [Add acceptance criteria from epics/PRD]
-
-## Tasks / Subtasks
-
-- [ ] Task 1 (AC: #)
-  - [ ] Subtask 1.1
-- [ ] Task 2 (AC: #)
-  - [ ] Subtask 2.1
-
-## Dev Notes
-
-- Relevant architecture patterns and constraints
-- Source tree components to touch
-- Testing standards summary
-
-### Project Structure Notes
-
-- Alignment with unified project structure (paths, modules, naming)
-- Detected conflicts or variances (with rationale)
-
-### References
-
-- Cite all technical details with source paths and sections, e.g. [Source: docs/<file>.md#Section]
-
-## Dev Agent Record
-
-### Agent Model Used
-
-{{agent_model_name_version}}
-
-### Debug Log References
-
-### Completion Notes List
-
-### File List
+# Story {{epic_num}}.{{story_num}}: {{story_title}}
+
+Status: ready-for-dev
+
+<!-- Note: Validation is optional. Run validate-create-story for quality check before dev-story. -->
+
+## Story
+
+As a {{role}},
+I want {{action}},
+so that {{benefit}}.
+
+## Acceptance Criteria
+
+1. [Add acceptance criteria from epics/PRD]
+
+## Tasks / Subtasks
+
+- [ ] Task 1 (AC: #)
+  - [ ] Subtask 1.1
+- [ ] Task 2 (AC: #)
+  - [ ] Subtask 2.1
+
+## Dev Notes
+
+- Relevant architecture patterns and constraints
+- Source tree components to touch
+- Testing standards summary
+
+### Project Structure Notes
+
+- Alignment with unified project structure (paths, modules, naming)
+- Detected conflicts or variances (with rationale)
+
+### References
+
+- Cite all technical details with source paths and sections, e.g. [Source: docs/<file>.md#Section]
+
+## Dev Agent Record
+
+### Agent Model Used
+
+{{agent_model_name_version}}
+
+### Debug Log References
+
+### Completion Notes List
+
+### File List

package/bmad/bmm/workflows/4-implementation/create-story/workflow.md

@@ -1,58 +1,58 @@
----
-name: create-story
-description: "Create the next user story from epics+stories with enhanced context analysis, including siesa-ui-kit integration for UI components."
-web_bundle: true
----
-
-# Create Story Workflow
-
-**Goal:** Create a comprehensive, ready-for-dev user story file by analyzing epics, architecture, and previous work, ensuring all technical and UI requirements (specifically siesa-ui-kit) are included.
-
-**Your Role:** You are a Technical Product Owner and Context Analyst. Your job is to prevent developer mistakes by providing an exhaustive, "fool-proof" specification for every story. You are obsessive about detail, standards compliance, and providing all necessary context upfront.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This uses **step-file architecture** for disciplined execution:
-
-### Core Principles
-
-- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
-- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
-- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
-- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
-- **Append-Only Building**: Build documents by appending content as directed to the output file
-
-### Step Processing Rules
-
-1. **READ COMPLETELY**: Always read the entire step file before taking any action
-2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
-3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
-4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
-5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
-6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
-
-### Critical Rules (NO EXCEPTIONS)
-
-- 🛑 **NEVER** load multiple step files simultaneously
-- 📖 **ALWAYS** read entire step file before execution
-- 🚫 **NEVER** skip steps or optimize the sequence
-- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
-- 🎯 **ALWAYS** follow the exact instructions in the step file
-- ⏸️ **ALWAYS** halt at menus and wait for user input
-- 📋 **NEVER** create mental todo lists from future steps
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
-
-- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
-
-### 2. First Step EXECUTION
-
-Load, read the full file and then execute `{workflow_path}/steps/step-01-determine-story.md` to begin the workflow.
+---
+name: create-story
+description: "Create the next user story from epics+stories with enhanced context analysis, including siesa-ui-kit integration for UI components."
+web_bundle: true
+---
+
+# Create Story Workflow
+
+**Goal:** Create a comprehensive, ready-for-dev user story file by analyzing epics, architecture, and previous work, ensuring all technical and UI requirements (specifically siesa-ui-kit) are included.
+
+**Your Role:** You are a Technical Product Owner and Context Analyst. Your job is to prevent developer mistakes by providing an exhaustive, "fool-proof" specification for every story. You are obsessive about detail, standards compliance, and providing all necessary context upfront.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
+- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
+- **Append-Only Building**: Build documents by appending content as directed to the output file
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load, read entire file, then execute the next step file
+
+### Critical Rules (NO EXCEPTIONS)
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
+- 🎯 **ALWAYS** follow the exact instructions in the step file
+- ⏸️ **ALWAYS** halt at menus and wait for user input
+- 📋 **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
+
+- `project_name`, `output_folder`, `user_name`, `communication_language`, `document_output_language`
+
+### 2. First Step EXECUTION
+
+Load, read the full file and then execute `{workflow_path}/steps/step-01-determine-story.md` to begin the workflow.

package/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml.bak

@@ -1,63 +1,63 @@
-name: Create Story
-description: This workflow guides the creation of a user story, ensuring it's well-defined and ready for development.
-entry_point: step-01-init
-steps:
-  - id: step-01-init
-    type: instruction
-    description: >
-      Welcome to the Story Creation Workflow! This workflow will help you define a clear and actionable user story.
-      Let's start by gathering some initial information.
-    next: step-02-gather-requirements
-  - id: step-02-gather-requirements
-    type: form
-    fields:
-      - name: story_title
-        label: Story Title
-        type: text
-        required: true
-      - name: as_a
-        label: As a...
-        type: text
-        required: true
-      - name: i_want
-        label: I want...
-        type: text
-        required: true
-      - name: so_that
-        label: So that...
-        type: text
-        required: true
-    next: step-03-acceptance-criteria
-  - id: step-03-acceptance-criteria
-    type: instruction
-    description: >
-      Now, let's define the acceptance criteria for this story. These criteria will help the developers understand
-      when the story is complete.  Please list at least three acceptance criteria.
-    next: step-04-story-points
-  - id: step-04-story-points
-    type: number
-    label: Story Points (Estimate of effort)
-    min: 1
-    max: 13
-    next: step-05-review
-  - id: step-05-review
-    type: review
-    description: >
-      Please review the story details below.  Ensure all information is accurate and complete.
-    fields:
-      - name: story_title
-        label: Story Title
-      - name: as_a
-        label: As a...
-      - name: i_want
-        label: I want...
-      - name: so_that
-        label: So that...
-      - name: acceptance_criteria
-        label: Acceptance Criteria
-      - name: story_points
-        label: Story Points
-    next: step-06-complete
-  - id: step-06-complete
-    type: completion
-    description: Story created successfully!
+name: Create Story
+description: This workflow guides the creation of a user story, ensuring it's well-defined and ready for development.
+entry_point: step-01-init
+steps:
+  - id: step-01-init
+    type: instruction
+    description: >
+      Welcome to the Story Creation Workflow! This workflow will help you define a clear and actionable user story.
+      Let's start by gathering some initial information.
+    next: step-02-gather-requirements
+  - id: step-02-gather-requirements
+    type: form
+    fields:
+      - name: story_title
+        label: Story Title
+        type: text
+        required: true
+      - name: as_a
+        label: As a...
+        type: text
+        required: true
+      - name: i_want
+        label: I want...
+        type: text
+        required: true
+      - name: so_that
+        label: So that...
+        type: text
+        required: true
+    next: step-03-acceptance-criteria
+  - id: step-03-acceptance-criteria
+    type: instruction
+    description: >
+      Now, let's define the acceptance criteria for this story. These criteria will help the developers understand
+      when the story is complete.  Please list at least three acceptance criteria.
+    next: step-04-story-points
+  - id: step-04-story-points
+    type: number
+    label: Story Points (Estimate of effort)
+    min: 1
+    max: 13
+    next: step-05-review
+  - id: step-05-review
+    type: review
+    description: >
+      Please review the story details below.  Ensure all information is accurate and complete.
+    fields:
+      - name: story_title
+        label: Story Title
+      - name: as_a
+        label: As a...
+      - name: i_want
+        label: I want...
+      - name: so_that
+        label: So that...
+      - name: acceptance_criteria
+        label: Acceptance Criteria
+      - name: story_points
+        label: Story Points
+    next: step-06-complete
+  - id: step-06-complete
+    type: completion
+    description: Story created successfully!