siesa-agents 2.1.35 → 2.1.37

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

@@ -0,0 +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'

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

@@ -0,0 +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'

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

@@ -0,0 +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'

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

@@ -0,0 +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'

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

@@ -0,0 +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'

package/_bmad/bmm/workflows/4-implementation/create-story/steps/step-06-finalize.md

@@ -0,0 +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'

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

@@ -0,0 +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

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

@@ -0,0 +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.

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

@@ -0,0 +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!

package/_bmad/bmm/workflows/4-implementation/dev-story/checklist.md

@@ -0,0 +1,85 @@
+---
+title: 'Enhanced Dev Story Definition of Done Checklist'
+validation-target: 'Story markdown ({{story_path}})'
+validation-criticality: 'HIGHEST'
+required-inputs:
+  - 'Story markdown file with enhanced Dev Notes containing comprehensive implementation context'
+  - 'Completed Tasks/Subtasks section with all items marked [x]'
+  - 'Updated File List section with all changed files'
+  - 'Updated Dev Agent Record with implementation notes'
+optional-inputs:
+  - 'Test results output'
+  - 'CI logs'
+  - 'Linting reports'
+validation-rules:
+  - 'Only permitted story sections modified: Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, Status'
+  - 'All implementation requirements from story Dev Notes must be satisfied'
+  - 'Definition of Done checklist must pass completely'
+  - 'Enhanced story context must contain sufficient technical guidance'
+---
+
+# 🎯 Enhanced Definition of Done Checklist
+
+**Critical validation:** Story is truly ready for review only when ALL items below are satisfied
+
+## 📋 Context & Requirements Validation
+
+- [ ] **Story Context Completeness:** Dev Notes contains ALL necessary technical requirements, architecture patterns, and implementation guidance
+- [ ] **Architecture Compliance:** Implementation follows all architectural requirements specified in Dev Notes
+- [ ] **Technical Specifications:** All technical specifications (libraries, frameworks, versions) from Dev Notes are implemented correctly
+- [ ] **Previous Story Learnings:** Previous story insights incorporated (if applicable) and build upon appropriately
+
+## ✅ Implementation Completion
+
+- [ ] **All Tasks Complete:** Every task and subtask marked complete with [x]
+    - "Dependency Management (Auto-install/update)"
+    - "Strict AI Instruction for UI Kit usage"
+    - "Intelligent Exception Handling for custom components"
+    - "Validation of UI requirements vs UI Kit usage"
+- [ ] **Acceptance Criteria Satisfaction:** Implementation satisfies EVERY Acceptance Criterion in the story
+- [ ] **No Ambiguous Implementation:** Clear, unambiguous implementation that meets story requirements
+- [ ] **Edge Cases Handled:** Error conditions and edge cases appropriately addressed
+- [ ] **UI Kit Compliance:** All UI elements use siesa-ui-kit (no custom styles/components unless exception logged and approved)
+- [ ] **Dependencies Within Scope:** Only uses dependencies specified in story or project-context.md
+
+## 🧪 Testing & Quality Assurance
+
+- [ ] **Unit Tests:** Unit tests added/updated for ALL core functionality introduced/changed by this story
+- [ ] **Integration Tests:** Integration tests added/updated for component interactions when story requirements demand them
+- [ ] **End-to-End Tests:** End-to-end tests created for critical user flows when story requirements specify them
+- [ ] **Test Coverage:** Tests cover acceptance criteria and edge cases from story Dev Notes
+- [ ] **Regression Prevention:** ALL existing tests pass (no regressions introduced)
+- [ ] **Code Quality:** Linting and static checks pass when configured in project
+- [ ] **Test Framework Compliance:** Tests use project's testing frameworks and patterns from Dev Notes
+
+## 📝 Documentation & Tracking
+
+- [ ] **File List Complete:** File List includes EVERY new, modified, or deleted file (paths relative to repo root)
+- [ ] **Dev Agent Record Updated:** Contains relevant Implementation Notes and/or Debug Log for this work
+- [ ] **Change Log Updated:** Change Log includes clear summary of what changed and why
+- [ ] **Review Follow-ups:** All review follow-up tasks (marked [AI-Review]) completed and corresponding review items marked resolved (if applicable)
+- [ ] **Story Structure Compliance:** Only permitted sections of story file were modified
+
+## 🔚 Final Status Verification
+
+- [ ] **Story Status Updated:** Story Status set to "review"
+- [ ] **Sprint Status Updated:** Sprint status updated to "review" (when sprint tracking is used)
+- [ ] **Quality Gates Passed:** All quality checks and validations completed successfully
+- [ ] **No HALT Conditions:** No blocking issues or incomplete work remaining
+- [ ] **User Communication Ready:** Implementation summary prepared for user review
+
+## 🎯 Final Validation Output
+
+```
+Definition of Done: {{PASS/FAIL}}
+
+✅ **Story Ready for Review:** {{story_key}}
+📊 **Completion Score:** {{completed_items}}/{{total_items}} items passed
+🔍 **Quality Gates:** {{quality_gates_status}}
+📋 **Test Results:** {{test_results_summary}}
+📝 **Documentation:** {{documentation_status}}
+```
+
+**If FAIL:** List specific failures and required actions before story can be marked Ready for Review
+
+**If PASS:** Story is fully ready for code review and production consideration