siesa-agents 2.1.1 → 2.1.3

package/bmad-core/tasks/create-doc.md

@@ -1,103 +1,103 @@
-<!-- Powered by BMAD™ Core -->
-
-# Create Document from Template (YAML Driven)
-
-## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
-
-**THIS IS AN EXECUTABLE WORKFLOW - NOT REFERENCE MATERIAL**
-
-When this task is invoked:
-
-1. **DISABLE ALL EFFICIENCY OPTIMIZATIONS** - This workflow requires full user interaction
-2. **MANDATORY STEP-BY-STEP EXECUTION** - Each section must be processed sequentially with user feedback
-3. **ELICITATION IS REQUIRED** - When `elicit: true`, you MUST use the 1-9 format and wait for user response
-4. **NO SHORTCUTS ALLOWED** - Complete documents cannot be created without following this workflow
-
-**VIOLATION INDICATOR:** If you create a complete document without user interaction, you have violated this workflow.
-
-## Critical: Template Discovery
-
-If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
-
-## CRITICAL: Mandatory Elicitation Format
-
-**When `elicit: true`, this is a HARD STOP requiring user interaction:**
-
-**YOU MUST:**
-
-1. Present section content
-2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
-3. **STOP and present numbered options 1-9:**
-   - **Option 1:** Always "Proceed to next section"
-   - **Options 2-9:** Select 8 methods from data/elicitation-methods
-   - End with: "Select 1-9 or just type your question/feedback:"
-4. **WAIT FOR USER RESPONSE** - Do not proceed until user selects option or provides feedback
-
-**WORKFLOW VIOLATION:** Creating content for elicit=true sections without user interaction violates this task.
-
-**NEVER ask yes/no questions or use any other format.**
-
-## Processing Flow
-
-1. **Parse YAML template** - Load template metadata and sections
-2. **Set preferences** - Show current mode (Interactive), confirm output file
-3. **Process each section:**
-   - Skip if condition unmet
-   - Check agent permissions (owner/editors) - note if section is restricted to specific agents
-   - Draft content using section instruction
-   - Present content + detailed rationale
-   - **IF elicit: true** → MANDATORY 1-9 options format
-   - Save to file if possible
-4. **Continue until complete**
-
-## Detailed Rationale Requirements
-
-When presenting section content, ALWAYS include rationale that explains:
-
-- Trade-offs and choices made (what was chosen over alternatives and why)
-- Key assumptions made during drafting
-- Interesting or questionable decisions that need user attention
-- Areas that might need validation
-
-## Elicitation Results Flow
-
-After user selects elicitation method (2-9):
-
-1. Execute method from data/elicitation-methods
-2. Present results with insights
-3. Offer options:
-   - **1. Apply changes and update section**
-   - **2. Return to elicitation menu**
-   - **3. Ask any questions or engage further with this elicitation**
-
-## Agent Permissions
-
-When processing sections with agent permission fields:
-
-- **owner**: Note which agent role initially creates/populates the section
-- **editors**: List agent roles allowed to modify the section
-- **readonly**: Mark sections that cannot be modified after creation
-
-**For sections with restricted access:**
-
-- Include a note in the generated document indicating the responsible agent
-- Example: "_(This section is owned by dev-agent and can only be modified by dev-agent)_"
-
-## YOLO Mode
-
-User can type `#yolo` to toggle to YOLO mode (process all sections at once).
-
-## CRITICAL REMINDERS
-
-**❌ NEVER:**
-
-- Ask yes/no questions for elicitation
-- Use any format other than 1-9 numbered options
-- Create new elicitation methods
-
-**✅ ALWAYS:**
-
-- Use exact 1-9 format when elicit: true
-- Select options 2-9 from data/elicitation-methods only
-- Provide detailed rationale explaining decisions
-- End with "Select 1-9 or just type your question/feedback:"
+<!-- Powered by BMAD™ Core -->
+
+# Create Document from Template (YAML Driven)
+
+## ⚠️ CRITICAL EXECUTION NOTICE ⚠️
+
+**THIS IS AN EXECUTABLE WORKFLOW - NOT REFERENCE MATERIAL**
+
+When this task is invoked:
+
+1. **DISABLE ALL EFFICIENCY OPTIMIZATIONS** - This workflow requires full user interaction
+2. **MANDATORY STEP-BY-STEP EXECUTION** - Each section must be processed sequentially with user feedback
+3. **ELICITATION IS REQUIRED** - When `elicit: true`, you MUST use the 1-9 format and wait for user response
+4. **NO SHORTCUTS ALLOWED** - Complete documents cannot be created without following this workflow
+
+**VIOLATION INDICATOR:** If you create a complete document without user interaction, you have violated this workflow.
+
+## Critical: Template Discovery
+
+If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
+
+## CRITICAL: Mandatory Elicitation Format
+
+**When `elicit: true`, this is a HARD STOP requiring user interaction:**
+
+**YOU MUST:**
+
+1. Present section content
+2. Provide detailed rationale (explain trade-offs, assumptions, decisions made)
+3. **STOP and present numbered options 1-9:**
+   - **Option 1:** Always "Proceed to next section"
+   - **Options 2-9:** Select 8 methods from data/elicitation-methods
+   - End with: "Select 1-9 or just type your question/feedback:"
+4. **WAIT FOR USER RESPONSE** - Do not proceed until user selects option or provides feedback
+
+**WORKFLOW VIOLATION:** Creating content for elicit=true sections without user interaction violates this task.
+
+**NEVER ask yes/no questions or use any other format.**
+
+## Processing Flow
+
+1. **Parse YAML template** - Load template metadata and sections
+2. **Set preferences** - Show current mode (Interactive), confirm output file
+3. **Process each section:**
+   - Skip if condition unmet
+   - Check agent permissions (owner/editors) - note if section is restricted to specific agents
+   - Draft content using section instruction
+   - Present content + detailed rationale
+   - **IF elicit: true** → MANDATORY 1-9 options format
+   - Save to file if possible
+4. **Continue until complete**
+
+## Detailed Rationale Requirements
+
+When presenting section content, ALWAYS include rationale that explains:
+
+- Trade-offs and choices made (what was chosen over alternatives and why)
+- Key assumptions made during drafting
+- Interesting or questionable decisions that need user attention
+- Areas that might need validation
+
+## Elicitation Results Flow
+
+After user selects elicitation method (2-9):
+
+1. Execute method from data/elicitation-methods
+2. Present results with insights
+3. Offer options:
+   - **1. Apply changes and update section**
+   - **2. Return to elicitation menu**
+   - **3. Ask any questions or engage further with this elicitation**
+
+## Agent Permissions
+
+When processing sections with agent permission fields:
+
+- **owner**: Note which agent role initially creates/populates the section
+- **editors**: List agent roles allowed to modify the section
+- **readonly**: Mark sections that cannot be modified after creation
+
+**For sections with restricted access:**
+
+- Include a note in the generated document indicating the responsible agent
+- Example: "_(This section is owned by dev-agent and can only be modified by dev-agent)_"
+
+## YOLO Mode
+
+User can type `#yolo` to toggle to YOLO mode (process all sections at once).
+
+## CRITICAL REMINDERS
+
+**❌ NEVER:**
+
+- Ask yes/no questions for elicitation
+- Use any format other than 1-9 numbered options
+- Create new elicitation methods
+
+**✅ ALWAYS:**
+
+- Use exact 1-9 format when elicit: true
+- Select options 2-9 from data/elicitation-methods only
+- Provide detailed rationale explaining decisions
+- End with "Select 1-9 or just type your question/feedback:"

package/bmad-core/tasks/create-entity.md

@@ -1,133 +1,133 @@
-# Create Domain Entity
-
-## Purpose
-Create a domain entity with value objects, aggregates, and business rules following DDD principles.
-
-## Task Configuration
-```yaml
-elicit: true
-interactive: true
-required_params:
-  - entity_name
-  - service_name
-  - properties
-optional_params:
-  - value_objects
-  - business_rules
-  - domain_events
-```
-
-## Task Execution
-
-### Step 1: Elicit Entity Requirements
-Ask user for:
-
-**Entity Name**: What is the entity name? (use PascalCase)
-**Service Name**: Which bounded context does this entity belong to?
-**Properties**: What are the entity properties? (name, type, validation rules)
-**Value Objects**: Any complex properties that should be value objects? (optional)
-**Business Rules**: What business rules should this entity enforce? (optional)
-**Domain Events**: What events should this entity publish? (optional)
-
-### Step 2: Generate Entity Structure
-Create the following files:
-
-```
-src/modules/{service-name}/domain/
-├── entities/
-│   └── {entity}.entity.ts
-├── value-objects/
-│   ├── {entity}-id.value-object.ts
-│   └── {property}.value-object.ts
-├── aggregates/
-│   └── {entity}.aggregate.ts
-└── events/
-    └── {entity}-{action}.event.ts
-```
-
-### Step 3: Create Domain Entity
-Generate entity with:
-- Unique identifier (UUID or custom ID)
-- Properties with proper typing
-- Business rule validation methods
-- Factory methods for creation
-- Domain event publishing
-- Immutability patterns
-
-Example structure:
-```typescript
-export class {Entity}Entity extends AggregateRoot {{
-  private constructor(
-    public readonly id: {Entity}Id,
-    private _property: PropertyValueObject,
-    // ... other properties
-  ) {{
-    super();
-  }}
-
-  static create(props: Create{Entity}Props): {Entity}Entity {{
-    // Validation logic
-    // Business rule enforcement
-    const entity = new {Entity}Entity(/* ... */);
-    entity.addDomainEvent(new {Entity}CreatedEvent(entity.id));
-    return entity;
-  }}
-
-  // Business methods
-  public updateProperty(newValue: PropertyValueObject): void {{
-    // Business rule validation
-    this._property = newValue;
-    this.addDomainEvent(new {Entity}UpdatedEvent(this.id));
-  }}
-
-  // Getters
-  get property(): PropertyValueObject {{
-    return this._property;
-  }}
-}}
-```
-
-### Step 4: Generate Value Objects
-For each value object:
-- Immutable classes with validation
-- Equality based on value, not reference
-- Factory methods with validation
-- Type safety and domain expressiveness
-
-### Step 5: Create Aggregate Root
-If entity is an aggregate root:
-- Extend AggregateRoot base class
-- Manage domain events
-- Enforce consistency boundaries
-- Handle child entity relationships
-
-### Step 6: Generate Domain Events
-For each domain event:
-- Event class with entity data
-- Event handler interfaces
-- Integration with application layer
-- Serialization for external systems
-
-### Step 7: Generate Prisma Schema
-Update Prisma schema with:
-- Entity table definition
-- Proper field types and constraints
-- Relationships with other entities
-- Indexes for performance
-- Migrations for schema changes
-
-### Step 8: Generate Tests
-Create comprehensive tests:
-- Entity business rule tests
-- Value object validation tests
-- Aggregate consistency tests
-- Domain event publishing tests
-- Factory method tests
-
-## Completion Criteria
-- Entity follows DDD patterns
-- Business rules properly enforced
-- Value objects provide type safety
-- Domain events properly implemented
-- Prisma schema updated
+# Create Domain Entity
+
+## Purpose
+Create a domain entity with value objects, aggregates, and business rules following DDD principles.
+
+## Task Configuration
+```yaml
+elicit: true
+interactive: true
+required_params:
+  - entity_name
+  - service_name
+  - properties
+optional_params:
+  - value_objects
+  - business_rules
+  - domain_events
+```
+
+## Task Execution
+
+### Step 1: Elicit Entity Requirements
+Ask user for:
+
+**Entity Name**: What is the entity name? (use PascalCase)
+**Service Name**: Which bounded context does this entity belong to?
+**Properties**: What are the entity properties? (name, type, validation rules)
+**Value Objects**: Any complex properties that should be value objects? (optional)
+**Business Rules**: What business rules should this entity enforce? (optional)
+**Domain Events**: What events should this entity publish? (optional)
+
+### Step 2: Generate Entity Structure
+Create the following files:
+
+```
+src/modules/{service-name}/domain/
+├── entities/
+│   └── {entity}.entity.ts
+├── value-objects/
+│   ├── {entity}-id.value-object.ts
+│   └── {property}.value-object.ts
+├── aggregates/
+│   └── {entity}.aggregate.ts
+└── events/
+    └── {entity}-{action}.event.ts
+```
+
+### Step 3: Create Domain Entity
+Generate entity with:
+- Unique identifier (UUID or custom ID)
+- Properties with proper typing
+- Business rule validation methods
+- Factory methods for creation
+- Domain event publishing
+- Immutability patterns
+
+Example structure:
+```typescript
+export class {Entity}Entity extends AggregateRoot {{
+  private constructor(
+    public readonly id: {Entity}Id,
+    private _property: PropertyValueObject,
+    // ... other properties
+  ) {{
+    super();
+  }}
+
+  static create(props: Create{Entity}Props): {Entity}Entity {{
+    // Validation logic
+    // Business rule enforcement
+    const entity = new {Entity}Entity(/* ... */);
+    entity.addDomainEvent(new {Entity}CreatedEvent(entity.id));
+    return entity;
+  }}
+
+  // Business methods
+  public updateProperty(newValue: PropertyValueObject): void {{
+    // Business rule validation
+    this._property = newValue;
+    this.addDomainEvent(new {Entity}UpdatedEvent(this.id));
+  }}
+
+  // Getters
+  get property(): PropertyValueObject {{
+    return this._property;
+  }}
+}}
+```
+
+### Step 4: Generate Value Objects
+For each value object:
+- Immutable classes with validation
+- Equality based on value, not reference
+- Factory methods with validation
+- Type safety and domain expressiveness
+
+### Step 5: Create Aggregate Root
+If entity is an aggregate root:
+- Extend AggregateRoot base class
+- Manage domain events
+- Enforce consistency boundaries
+- Handle child entity relationships
+
+### Step 6: Generate Domain Events
+For each domain event:
+- Event class with entity data
+- Event handler interfaces
+- Integration with application layer
+- Serialization for external systems
+
+### Step 7: Generate Prisma Schema
+Update Prisma schema with:
+- Entity table definition
+- Proper field types and constraints
+- Relationships with other entities
+- Indexes for performance
+- Migrations for schema changes
+
+### Step 8: Generate Tests
+Create comprehensive tests:
+- Entity business rule tests
+- Value object validation tests
+- Aggregate consistency tests
+- Domain event publishing tests
+- Factory method tests
+
+## Completion Criteria
+- Entity follows DDD patterns
+- Business rules properly enforced
+- Value objects provide type safety
+- Domain events properly implemented
+- Prisma schema updated
 - Comprehensive test coverage

package/bmad-core/tasks/create-feature.md

@@ -1,91 +1,91 @@
-# Create Frontend Feature
-
-## Purpose
-Create a complete feature following Clean Architecture + DDD principles with all necessary layers.
-
-## Task Configuration
-```yaml
-elicit: true
-interactive: true
-required_params:
-  - feature_name
-  - entities
-  - use_cases
-optional_params:
-  - api_endpoints
-  - ui_components
-```
-
-## Task Execution
-
-### Step 1: Elicit Feature Requirements
-Ask user for:
-
-**Feature Name**: What is the name of the feature? (use kebab-case)
-**Domain Entities**: What are the main business entities for this feature?
-**Use Cases**: What are the main use cases/operations users can perform?
-**API Endpoints**: What backend endpoints will this feature consume? (optional)
-**UI Components**: Any specific components you know you'll need? (optional)
-
-### Step 2: Create Feature Structure
-Generate the following structure:
-
-```
-src/features/{feature_name}/
-├── domain/
-│   ├── entities/
-│   ├── repositories/
-│   ├── services/
-│   └── types/
-├── application/
-│   ├── use-cases/
-│   ├── hooks/
-│   └── store/
-├── infrastructure/
-│   ├── repositories/
-│   ├── api/
-│   └── adapters/
-└── presentation/
-    ├── components/
-    ├── pages/
-    └── styles/
-```
-
-### Step 3: Generate Domain Layer
-For each entity:
-- Create TypeScript interfaces/types
-- Define value objects if needed
-- Create repository interfaces
-- Define domain services if complex business rules exist
-
-### Step 4: Generate Application Layer
-For each use case:
-- Create use case implementation
-- Create custom hooks that consume use cases
-- Setup Zustand store for feature state
-- Implement error handling and loading states
-
-### Step 5: Generate Infrastructure Layer
-- Implement repository concrete classes
-- Setup API clients with proper typing
-- Create adapters for external services
-- Configure error handling and retries
-
-### Step 6: Generate Presentation Layer
-- Create feature-specific components
-- Setup routing for feature pages
-- Implement accessibility features
-- Add loading and error states
-
-### Step 7: Generate Tests
-- Unit tests for domain entities and services
-- Integration tests for use cases
-- Component tests for presentation layer
-- API integration tests for infrastructure layer
-
-## Completion Criteria
-- All layers properly implemented
-- Clean Architecture dependencies respected
-- TypeScript compilation successful
-- All tests passing
+# Create Frontend Feature
+
+## Purpose
+Create a complete feature following Clean Architecture + DDD principles with all necessary layers.
+
+## Task Configuration
+```yaml
+elicit: true
+interactive: true
+required_params:
+  - feature_name
+  - entities
+  - use_cases
+optional_params:
+  - api_endpoints
+  - ui_components
+```
+
+## Task Execution
+
+### Step 1: Elicit Feature Requirements
+Ask user for:
+
+**Feature Name**: What is the name of the feature? (use kebab-case)
+**Domain Entities**: What are the main business entities for this feature?
+**Use Cases**: What are the main use cases/operations users can perform?
+**API Endpoints**: What backend endpoints will this feature consume? (optional)
+**UI Components**: Any specific components you know you'll need? (optional)
+
+### Step 2: Create Feature Structure
+Generate the following structure:
+
+```
+src/features/{feature_name}/
+├── domain/
+│   ├── entities/
+│   ├── repositories/
+│   ├── services/
+│   └── types/
+├── application/
+│   ├── use-cases/
+│   ├── hooks/
+│   └── store/
+├── infrastructure/
+│   ├── repositories/
+│   ├── api/
+│   └── adapters/
+└── presentation/
+    ├── components/
+    ├── pages/
+    └── styles/
+```
+
+### Step 3: Generate Domain Layer
+For each entity:
+- Create TypeScript interfaces/types
+- Define value objects if needed
+- Create repository interfaces
+- Define domain services if complex business rules exist
+
+### Step 4: Generate Application Layer
+For each use case:
+- Create use case implementation
+- Create custom hooks that consume use cases
+- Setup Zustand store for feature state
+- Implement error handling and loading states
+
+### Step 5: Generate Infrastructure Layer
+- Implement repository concrete classes
+- Setup API clients with proper typing
+- Create adapters for external services
+- Configure error handling and retries
+
+### Step 6: Generate Presentation Layer
+- Create feature-specific components
+- Setup routing for feature pages
+- Implement accessibility features
+- Add loading and error states
+
+### Step 7: Generate Tests
+- Unit tests for domain entities and services
+- Integration tests for use cases
+- Component tests for presentation layer
+- API integration tests for infrastructure layer
+
+## Completion Criteria
+- All layers properly implemented
+- Clean Architecture dependencies respected
+- TypeScript compilation successful
+- All tests passing
 - Feature integrated with main application