siesa-agents 2.1.36 → 2.1.38

package/bmad-core/templates/project-brief-tmpl.yaml

@@ -1,222 +0,0 @@
-# <!-- Powered by BMAD™ Core -->
-template:
-  id: project-brief-template-v2
-  name: Project Brief
-  version: 2.0
-  output:
-    format: markdown
-    filename: docs/brief.md
-    title: "Project Brief: {{project_name}}"
-
-workflow:
-  mode: interactive
-  elicitation: advanced-elicitation
-  custom_elicitation:
-    title: "Project Brief Elicitation Actions"
-    options:
-      - "Expand section with more specific details"
-      - "Validate against similar successful products"
-      - "Stress test assumptions with edge cases"
-      - "Explore alternative solution approaches"
-      - "Analyze resource/constraint trade-offs"
-      - "Generate risk mitigation strategies"
-      - "Challenge scope from MVP minimalist view"
-      - "Brainstorm creative feature possibilities"
-      - "If only we had [resource/capability/time]..."
-      - "Proceed to next section"
-
-sections:
-  - id: introduction
-    instruction: |
-      This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
-
-      Start by asking the user which mode they prefer:
-
-      1. **Interactive Mode** - Work through each section collaboratively
-      2. **YOLO Mode** - Generate complete draft for review and refinement
-
-      Before beginning, understand what inputs are available (brainstorming results, market research, competitive analysis, initial ideas) and gather project context.
-
-  - id: executive-summary
-    title: Executive Summary
-    instruction: |
-      Create a concise overview that captures the essence of the project. Include:
-      - Product concept in 1-2 sentences
-      - Primary problem being solved
-      - Target market identification
-      - Key value proposition
-    template: "{{executive_summary_content}}"
-
-  - id: problem-statement
-    title: Problem Statement
-    instruction: |
-      Articulate the problem with clarity and evidence. Address:
-      - Current state and pain points
-      - Impact of the problem (quantify if possible)
-      - Why existing solutions fall short
-      - Urgency and importance of solving this now
-    template: "{{detailed_problem_description}}"
-
-  - id: proposed-solution
-    title: Proposed Solution
-    instruction: |
-      Describe the solution approach at a high level. Include:
-      - Core concept and approach
-      - Key differentiators from existing solutions
-      - Why this solution will succeed where others haven't
-      - High-level vision for the product
-    template: "{{solution_description}}"
-
-  - id: target-users
-    title: Target Users
-    instruction: |
-      Define and characterize the intended users with specificity. For each user segment include:
-      - Demographic/firmographic profile
-      - Current behaviors and workflows
-      - Specific needs and pain points
-      - Goals they're trying to achieve
-    sections:
-      - id: primary-segment
-        title: "Primary User Segment: {{segment_name}}"
-        template: "{{primary_user_description}}"
-      - id: secondary-segment
-        title: "Secondary User Segment: {{segment_name}}"
-        condition: Has secondary user segment
-        template: "{{secondary_user_description}}"
-
-  - id: goals-metrics
-    title: Goals & Success Metrics
-    instruction: Establish clear objectives and how to measure success. Make goals SMART (Specific, Measurable, Achievable, Relevant, Time-bound)
-    sections:
-      - id: business-objectives
-        title: Business Objectives
-        type: bullet-list
-        template: "- {{objective_with_metric}}"
-      - id: user-success-metrics
-        title: User Success Metrics
-        type: bullet-list
-        template: "- {{user_metric}}"
-      - id: kpis
-        title: Key Performance Indicators (KPIs)
-        type: bullet-list
-        template: "- {{kpi}}: {{definition_and_target}}"
-
-  - id: mvp-scope
-    title: MVP Scope
-    instruction: Define the minimum viable product clearly. Be specific about what's in and what's out. Help user distinguish must-haves from nice-to-haves.
-    sections:
-      - id: core-features
-        title: Core Features (Must Have)
-        type: bullet-list
-        template: "- **{{feature}}:** {{description_and_rationale}}"
-      - id: out-of-scope
-        title: Out of Scope for MVP
-        type: bullet-list
-        template: "- {{feature_or_capability}}"
-      - id: mvp-success-criteria
-        title: MVP Success Criteria
-        template: "{{mvp_success_definition}}"
-
-  - id: post-mvp-vision
-    title: Post-MVP Vision
-    instruction: Outline the longer-term product direction without overcommitting to specifics
-    sections:
-      - id: phase-2-features
-        title: Phase 2 Features
-        template: "{{next_priority_features}}"
-      - id: long-term-vision
-        title: Long-term Vision
-        template: "{{one_two_year_vision}}"
-      - id: expansion-opportunities
-        title: Expansion Opportunities
-        template: "{{potential_expansions}}"
-
-  - id: technical-considerations
-    title: Technical Considerations
-    instruction: Document known technical constraints and preferences. Note these are initial thoughts, not final decisions.
-    sections:
-      - id: platform-requirements
-        title: Platform Requirements
-        template: |
-          - **Target Platforms:** {{platforms}}
-          - **Browser/OS Support:** {{specific_requirements}}
-          - **Performance Requirements:** {{performance_specs}}
-      - id: technology-preferences
-        title: Technology Preferences
-        template: |
-          - **Frontend:** {{frontend_preferences}}
-          - **Backend:** {{backend_preferences}}
-          - **Database:** {{database_preferences}}
-          - **Hosting/Infrastructure:** {{infrastructure_preferences}}
-      - id: architecture-considerations
-        title: Architecture Considerations
-        template: |
-          - **Repository Structure:** {{repo_thoughts}}
-          - **Service Architecture:** {{service_thoughts}}
-          - **Integration Requirements:** {{integration_needs}}
-          - **Security/Compliance:** {{security_requirements}}
-
-  - id: constraints-assumptions
-    title: Constraints & Assumptions
-    instruction: Clearly state limitations and assumptions to set realistic expectations
-    sections:
-      - id: constraints
-        title: Constraints
-        template: |
-          - **Budget:** {{budget_info}}
-          - **Timeline:** {{timeline_info}}
-          - **Resources:** {{resource_info}}
-          - **Technical:** {{technical_constraints}}
-      - id: key-assumptions
-        title: Key Assumptions
-        type: bullet-list
-        template: "- {{assumption}}"
-
-  - id: risks-questions
-    title: Risks & Open Questions
-    instruction: Identify unknowns and potential challenges proactively
-    sections:
-      - id: key-risks
-        title: Key Risks
-        type: bullet-list
-        template: "- **{{risk}}:** {{description_and_impact}}"
-      - id: open-questions
-        title: Open Questions
-        type: bullet-list
-        template: "- {{question}}"
-      - id: research-areas
-        title: Areas Needing Further Research
-        type: bullet-list
-        template: "- {{research_topic}}"
-
-  - id: appendices
-    title: Appendices
-    sections:
-      - id: research-summary
-        title: A. Research Summary
-        condition: Has research findings
-        instruction: |
-          If applicable, summarize key findings from:
-          - Market research
-          - Competitive analysis
-          - User interviews
-          - Technical feasibility studies
-      - id: stakeholder-input
-        title: B. Stakeholder Input
-        condition: Has stakeholder feedback
-        template: "{{stakeholder_feedback}}"
-      - id: references
-        title: C. References
-        template: "{{relevant_links_and_docs}}"
-
-  - id: next-steps
-    title: Next Steps
-    sections:
-      - id: immediate-actions
-        title: Immediate Actions
-        type: numbered-list
-        template: "{{action_item}}"
-      - id: pm-handoff
-        title: PM Handoff
-        content: |
-          This Project Brief provides the full context for {{project_name}}. Please start in 'PRD Generation Mode', review the brief thoroughly to work with the user to create the PRD section by section as the template indicates, asking for any necessary clarification or suggesting improvements.

package/bmad-core/templates/qa-gate-tmpl.yaml

@@ -1,103 +0,0 @@
-# <!-- Powered by BMAD™ Core -->
-template:
-  id: qa-gate-template-v1
-  name: Quality Gate Decision
-  version: 1.0
-  output:
-    format: yaml
-    filename: qa.qaLocation/gates/{{epic_num}}.{{story_num}}-{{story_slug}}.yml
-    title: "Quality Gate: {{epic_num}}.{{story_num}}"
-
-# Required fields (keep these first)
-schema: 1
-story: "{{epic_num}}.{{story_num}}"
-story_title: "{{story_title}}"
-gate: "{{gate_status}}" # PASS|CONCERNS|FAIL|WAIVED
-status_reason: "{{status_reason}}" # 1-2 sentence summary of why this gate decision
-reviewer: "Quinn (Test Architect)"
-updated: "{{iso_timestamp}}"
-
-# Always present but only active when WAIVED
-waiver: { active: false }
-
-# Issues (if any) - Use fixed severity: low | medium | high
-top_issues: []
-
-# Risk summary (from risk-profile task if run)
-risk_summary:
-  totals: { critical: 0, high: 0, medium: 0, low: 0 }
-  recommendations:
-    must_fix: []
-    monitor: []
-
-# Examples section using block scalars for clarity
-examples:
-  with_issues: |
-    top_issues:
-      - id: "SEC-001"
-        severity: high  # ONLY: low|medium|high
-        finding: "No rate limiting on login endpoint"
-        suggested_action: "Add rate limiting middleware before production"
-      - id: "TEST-001"  
-        severity: medium
-        finding: "Missing integration tests for auth flow"
-        suggested_action: "Add test coverage for critical paths"
-
-  when_waived: |
-    waiver:
-      active: true
-      reason: "Accepted for MVP release - will address in next sprint"
-      approved_by: "Product Owner"
-
-# ============ Optional Extended Fields ============
-# Uncomment and use if your team wants more detail
-
-optional_fields_examples:
-  quality_and_expiry: |
-    quality_score: 75  # 0-100 (optional scoring)
-    expires: "2025-01-26T00:00:00Z"  # Optional gate freshness window
-
-  evidence: |
-    evidence:
-      tests_reviewed: 15
-      risks_identified: 3
-      trace:
-        ac_covered: [1, 2, 3]  # AC numbers with test coverage
-        ac_gaps: [4]  # AC numbers lacking coverage
-
-  nfr_validation: |
-    nfr_validation:
-      security: { status: CONCERNS, notes: "Rate limiting missing" }
-      performance: { status: PASS, notes: "" }
-      reliability: { status: PASS, notes: "" }
-      maintainability: { status: PASS, notes: "" }
-
-  history: |
-    history:  # Append-only audit trail
-      - at: "2025-01-12T10:00:00Z"
-        gate: FAIL
-        note: "Initial review - missing tests"
-      - at: "2025-01-12T15:00:00Z"  
-        gate: CONCERNS
-        note: "Tests added but rate limiting still missing"
-
-  risk_summary: |
-    risk_summary:  # From risk-profile task
-      totals:
-        critical: 0
-        high: 0
-        medium: 0
-        low: 0
-      # 'highest' is emitted only when risks exist
-      recommendations:
-        must_fix: []
-        monitor: []
-
-  recommendations: |
-    recommendations:
-      immediate:  # Must fix before production
-        - action: "Add rate limiting to auth endpoints"
-          refs: ["api/auth/login.ts:42-68"]
-      future:  # Can be addressed later
-        - action: "Consider caching for better performance"
-          refs: ["services/data.service.ts"]

package/bmad-core/templates/story-tmpl.yaml

@@ -1,138 +0,0 @@
-# <!-- Powered by BMAD™ Core -->
-template:
-  id: story-template-v2
-  name: Story Document
-  version: 2.0
-  output:
-    format: markdown
-    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.story.md
-    title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}"
-
-workflow:
-  mode: interactive
-  elicitation: advanced-elicitation
-
-agent_config:
-  editable_sections:
-    - Status
-    - Story
-    - Acceptance Criteria
-    - Tasks / Subtasks
-    - Dev Notes
-    - Testing
-    - Change Log
-
-sections:
-  - id: status
-    title: Status
-    type: choice
-    choices: [Draft, Approved, InProgress, Review, Done]
-    instruction: Select the current status of the story
-    owner: scrum-master
-    editors: [scrum-master, dev-agent]
-
-  - id: story
-    title: Story
-    type: template-text
-    template: |
-      **As a** {{role}},
-      **I want** {{action}},
-      **so that** {{benefit}}
-    instruction: Define the user story using the standard format with role, action, and benefit
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master]
-
-  - id: acceptance-criteria
-    title: Acceptance Criteria
-    type: numbered-list
-    instruction: Copy the acceptance criteria numbered list from the epic file
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master]
-
-  - id: tasks-subtasks
-    title: Tasks / Subtasks
-    type: bullet-list
-    instruction: |
-      Break down the story into specific tasks and subtasks needed for implementation.
-      Reference applicable acceptance criteria numbers where relevant.
-    template: |
-      - [ ] Task 1 (AC: # if applicable)
-        - [ ] Subtask1.1...
-      - [ ] Task 2 (AC: # if applicable)
-        - [ ] Subtask 2.1...
-      - [ ] Task 3 (AC: # if applicable)
-        - [ ] Subtask 3.1...
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master, dev-agent]
-
-  - id: dev-notes
-    title: Dev Notes
-    instruction: |
-      Populate relevant information, only what was pulled from actual artifacts from docs folder, relevant to this story:
-      - Do not invent information
-      - If known add Relevant Source Tree info that relates to this story
-      - If there were important notes from previous story that are relevant to this one, include them here
-      - Put enough information in this section so that the dev agent should NEVER need to read the architecture documents, these notes along with the tasks and subtasks must give the Dev Agent the complete context it needs to comprehend with the least amount of overhead the information to complete the story, meeting all AC and completing all tasks+subtasks
-    elicit: true
-    owner: scrum-master
-    editors: [scrum-master]
-    sections:
-      - id: testing-standards
-        title: Testing
-        instruction: |
-          List Relevant Testing Standards from Architecture the Developer needs to conform to:
-          - Test file location
-          - Test standards
-          - Testing frameworks and patterns to use
-          - Any specific testing requirements for this story
-        elicit: true
-        owner: scrum-master
-        editors: [scrum-master]
-
-  - id: change-log
-    title: Change Log
-    type: table
-    columns: [Date, Version, Description, Author]
-    instruction: Track changes made to this story document
-    owner: scrum-master
-    editors: [scrum-master, dev-agent, qa-agent]
-
-  - id: dev-agent-record
-    title: Dev Agent Record
-    instruction: This section is populated by the development agent during implementation
-    owner: dev-agent
-    editors: [dev-agent]
-    sections:
-      - id: agent-model
-        title: Agent Model Used
-        template: "{{agent_model_name_version}}"
-        instruction: Record the specific AI agent model and version used for development
-        owner: dev-agent
-        editors: [dev-agent]
-
-      - id: debug-log-references
-        title: Debug Log References
-        instruction: Reference any debug logs or traces generated during development
-        owner: dev-agent
-        editors: [dev-agent]
-
-      - id: completion-notes
-        title: Completion Notes List
-        instruction: Notes about the completion of tasks and any issues encountered
-        owner: dev-agent
-        editors: [dev-agent]
-
-      - id: file-list
-        title: File List
-        instruction: List all files created, modified, or affected during story implementation
-        owner: dev-agent
-        editors: [dev-agent]
-
-  - id: qa-results
-    title: QA Results
-    instruction: Results from QA Agent QA review of the completed story implementation
-    owner: qa-agent
-    editors: [qa-agent]