npm - siesa-agents - Versions diffs - 2.1.39 → 2.1.41 - Mend

siesa-agents 2.1.39 → 2.1.41

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1072) hide show

package/_bmad/bmm/workflows/2-plan-workflows/prd/steps/step-11-complete.md DELETED Viewed

@@ -1,186 +0,0 @@
----
-name: 'step-11-complete'
-description: 'Complete the PRD workflow, update status files, and suggest next steps'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd'
-# File References
-thisStepFile: '{workflow_path}/steps/step-11-complete.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/prd.md'
----
-# Step 11: Workflow Completion
-**Final Step - Complete the PRD**
-## MANDATORY EXECUTION RULES (READ FIRST):
-- ✅ THIS IS A FINAL STEP - Workflow completion required
-- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
-- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
-- 🛑 NO content generation - this is a wrap-up step
-- 📋 FINALIZE document and update workflow status
-- 💬 FOCUS on completion, next steps, and suggestions
-- 🎯 UPDATE workflow status files with completion information
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-## EXECUTION PROTOCOLS:
-- 🎯 Show your analysis before taking any action
-- 💾 Update the main workflow status file with completion information
-- 📖 Suggest potential next workflow steps for the user
-- 🚫 DO NOT load additional steps after this one
-## TERMINATION STEP PROTOCOLS:
-- This is a FINAL step - workflow completion required
-- Output any remaining content if needed (none for this step)
-- Update the main workflow status file with finalized document
-- Suggest potential next steps for the user
-- Mark workflow as complete in status tracking
-## CONTEXT BOUNDARIES:
-- Complete PRD document is available from all previous steps
-- Workflow frontmatter shows all completed steps
-- All collaborative content has been generated and saved
-- Focus on completion, validation, and next steps
-## YOUR TASK:
-Complete the PRD workflow, update status files, and suggest next steps for the project.
-## WORKFLOW COMPLETION SEQUENCE:
-### 1. Announce Workflow Completion
-Inform user that the PRD is complete:
-"🎉 **PRD Complete, {{user_name}}!**
-I've successfully collaborated with you to create a comprehensive Product Requirements Document for {{project_name}}.
-**What we've accomplished:**
-- ✅ Executive Summary with vision and product differentiator
-- ✅ Success Criteria with measurable outcomes and scope definition
-- ✅ User Journeys covering all interaction patterns
-- ✅ Domain-specific requirements (if applicable)
-- ✅ Innovation analysis (if applicable)
-- ✅ Project-type specific technical requirements
-- ✅ Comprehensive Functional Requirements (capability contract)
-- ✅ Non-Functional Requirements for quality attributes
-**The complete PRD is now available at:** `{outputFile}`
-This document is now ready to guide UX design, technical architecture, and development planning."
-### 2. Workflow Status Update
-Update the main workflow status file if there is one:
-- Load `{status_file}` from workflow configuration (if exists)
-- Update workflow_status["prd"] = "{default_output_file}"
-- Save file, preserving all comments and structure
-- Mark current timestamp as completion time
-### 3. Suggest Next Steps
-Provide guidance on logical next workflows:
-**Typical Next Workflows:**
-**Immediate Next Steps:**
-1. `workflow create-ux-design` - UX Design (if UI exists)
-   - User journey insights from step-04 will inform interaction design
-   - Functional requirements from step-09 define design scope
-2. `workflow create-architecture` - Technical architecture
-   - Project-type requirements from step-07 guide technical decisions
-   - Non-functional requirements from step-10 inform architecture choices
-3. `workflow create-epics-and-stories` - Epic breakdown
-   - Functional requirements from step-09 become epics and stories
-   - Scope definition from step-03 guides sprint planning
-**Strategic Considerations:**
-- UX design and architecture can happen in parallel
-- Epics/stories are richer when created after UX/architecture
-**What would be most valuable to tackle next?**
-### 4. Document Quality Check
-Perform final validation of the PRD:
-**Completeness Check:**
-- Does the executive summary clearly communicate the vision?
-- Are success criteria specific and measurable?
-- Do user journeys cover all major user types?
-- Are functional requirements comprehensive and testable?
-- Are non-functional requirements relevant and specific?
-**Consistency Check:**
-- Do all sections align with the product differentiator?
-- Is scope consistent across all sections?
-- Are requirements traceable to user needs and success criteria?
-### 5. Final Completion Confirmation
-- Confirm completion with user and summarize what you have done.
-- Update frontmatter: add this final step name to the end of the steps completed array.
-## SUCCESS METRICS:
-✅ PRD document contains all required sections
-✅ All collaborative content properly saved to document
-✅ Workflow status file updated with completion information
-✅ Clear next step guidance provided to user
-✅ Document quality validation completed
-✅ User acknowledges completion and understands next options
-## FAILURE MODES:
-❌ Not updating workflow status file with completion information
-❌ Missing clear next step guidance for user
-❌ Not confirming document completeness with user
-❌ Workflow not properly marked as complete in status tracking
-❌ User unclear about what happens next
-❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
-❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
-❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
-## WORKFLOW COMPLETION CHECKLIST:
-### Document Structure Complete:
-- [ ] Executive Summary with vision and differentiator
-- [ ] Success Criteria with measurable outcomes
-- [ ] Product Scope (MVP, Growth, Vision)
-- [ ] User Journeys (comprehensive coverage)
-- [ ] Domain Requirements (if applicable)
-- [ ] Innovation Analysis (if applicable)
-- [ ] Project-Type Requirements
-- [ ] Functional Requirements (capability contract)
-- [ ] Non-Functional Requirements
-### Process Complete:
-- [ ] All steps completed with user confirmation
-- [ ] All content saved to document
-- [ ] Frontmatter properly updated
-- [ ] Workflow status file updated
-- [ ] Next steps clearly communicated
-## FINAL REMINDER:
-This workflow is now complete. The PRD serves as the foundation for all subsequent product development activities. All design, architecture, and development work should trace back to the requirements and vision documented in this PRD.
-**Congratulations on completing the Product Requirements Document for {{project_name}}!** 🎉

package/_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md DELETED Viewed

@@ -1,63 +0,0 @@
----
-name: create-prd
-description: Creates a comprehensive PRD through collaborative step-by-step discovery between two product managers working as peers.
-main_config: '{project-root}/_bmad/bmm/config.yaml'
-web_bundle: true
----
-# PRD Workflow
-**Goal:** Create comprehensive PRDs through collaborative step-by-step discovery between two product managers working as peers.
-**Your Role:** You are a product-focused PM facilitator collaborating with an expert peer. This is a partnership, not a client-vendor relationship. You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision. Work together as equals. You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
----
-## 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 {main_config} and resolve:
-- `project_name`, `output_folder`, `planning_artifacts`, `user_name`
-- `communication_language`, `document_output_language`, `user_skill_level`
-- `date` as system-generated current datetime
-### 2. First Step EXECUTION
-YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`.
-Load, read the full file and then execute `steps/step-01-init.md` to begin the workflow.

package/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-01-document-discovery.md DELETED Viewed

@@ -1,190 +0,0 @@
----
-name: 'step-01-document-discovery'
-description: 'Discover and inventory all project documents, handling duplicates and organizing file structure'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
-# File References
-thisStepFile: '{workflow_path}/steps/step-01-document-discovery.md'
-nextStepFile: '{workflow_path}/steps/step-02-prd-analysis.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
-templateFile: '{workflow_path}/templates/readiness-report-template.md'
----
-# Step 1: Document Discovery
-## STEP GOAL:
-To discover, inventory, and organize all project documents, identifying duplicates and determining which versions to use for the assessment.
-## 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
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-### Role Reinforcement:
-- ✅ You are an expert Product Manager and Scrum Master
-- ✅ Your focus is on finding organizing and documenting what exists
-- ✅ You identify ambiguities and ask for clarification
-- ✅ Success is measured in clear file inventory and conflict resolution
-### Step-Specific Rules:
-- 🎯 Focus ONLY on finding and organizing files
-- 🚫 Don't read or analyze file contents
-- 💬 Identify duplicate documents clearly
-- 🚪 Get user confirmation on file selections
-## EXECUTION PROTOCOLS:
-- 🎯 Search for all document types systematically
-- 💾 Group sharded files together
-- 📖 Flag duplicates for user resolution
-- 🚫 FORBIDDEN to proceed with unresolved duplicates
-## DOCUMENT DISCOVERY PROCESS:
-### 1. Initialize Document Discovery
-"Beginning **Document Discovery** to inventory all project files.
-I will:
-1. Search for all required documents (PRD, Architecture, Epics, UX)
-2. Group sharded documents together
-3. Identify any duplicates (whole + sharded versions)
-4. Present findings for your confirmation"
-### 2. Document Search Patterns
-Search for each document type using these patterns:
-#### A. PRD Documents
-- Whole: `{planning_artifacts}/*prd*.md`
-- Sharded: `{planning_artifacts}/*prd*/index.md` and related files
-#### B. Architecture Documents
-- Whole: `{planning_artifacts}/*architecture*.md`
-- Sharded: `{planning_artifacts}/*architecture*/index.md` and related files
-#### C. Epics & Stories Documents
-- Whole: `{planning_artifacts}/*epic*.md`
-- Sharded: `{planning_artifacts}/*epic*/index.md` and related files
-#### D. UX Design Documents
-- Whole: `{planning_artifacts}/*ux*.md`
-- Sharded: `{planning_artifacts}/*ux*/index.md` and related files
-### 3. Organize Findings
-For each document type found:
-```
-## [Document Type] Files Found
-**Whole Documents:**
-- [filename.md] ([size], [modified date])
-**Sharded Documents:**
-- Folder: [foldername]/
-  - index.md
-  - [other files in folder]
-```
-### 4. Identify Critical Issues
-#### Duplicates (CRITICAL)
-If both whole and sharded versions exist:
-```
-⚠️ CRITICAL ISSUE: Duplicate document formats found
-- PRD exists as both whole.md AND prd/ folder
-- YOU MUST choose which version to use
-- Remove or rename the other version to avoid confusion
-```
-#### Missing Documents (WARNING)
-If required documents not found:
-```
-⚠️ WARNING: Required document not found
-- Architecture document not found
-- Will impact assessment completeness
-```
-### 5. Add Initial Report Section
-Initialize {outputFile} with {templateFile}.
-### 6. Present Findings and Get Confirmation
-Display findings and ask:
-"**Document Discovery Complete**
-[Show organized file list]
-**Issues Found:**
-- [List any duplicates requiring resolution]
-- [List any missing documents]
-**Required Actions:**
-- If duplicates exist: Please remove/rename one version
-- Confirm which documents to use for assessment
-**Ready to proceed?** [C] Continue after resolving issues"
-### 7. Present MENU OPTIONS
-Display: **Select an Option:** [C] Continue to File Validation
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed with 'C' selection
-- If duplicates identified, insist on resolution first
-- User can clarify file locations or request additional searches
-#### Menu Handling Logic:
-- IF C: Save document inventory to {outputFile}, update frontmatter with completed step and files being included, and only then load read fully and execute {nextStepFile}
-- IF Any other comments or queries: help user respond then redisplay menu
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN C is selected and document inventory is saved will you load {nextStepFile} to begin file validation.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- All document types searched systematically
-- Files organized and inventoried clearly
-- Duplicates identified and flagged for resolution
-- User confirmed file selections
-### ❌ SYSTEM FAILURE:
-- Not searching all document types
-- Ignoring duplicate document conflicts
-- Proceeding without resolving critical issues
-- Not saving document inventory
-**Master Rule:** Clear file identification is essential for accurate assessment.

package/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/steps/step-02-prd-analysis.md DELETED Viewed

@@ -1,178 +0,0 @@
----
-name: 'step-02-prd-analysis'
-description: 'Read and analyze PRD to extract all FRs and NFRs for coverage validation'
-# Path Definitions
-workflow_path: '{project-root}/_bmad/bmm/workflows/3-solutioning/implementation-readiness'
-# File References
-thisStepFile: '{workflow_path}/steps/step-02-prd-analysis.md'
-nextStepFile: '{workflow_path}/steps/step-03-epic-coverage-validation.md'
-workflowFile: '{workflow_path}/workflow.md'
-outputFile: '{planning_artifacts}/implementation-readiness-report-{{date}}.md'
-epicsFile: '{planning_artifacts}/*epic*.md' # Will be resolved to actual file
----
-# Step 2: PRD Analysis
-## STEP GOAL:
-To fully read and analyze the PRD document (whole or sharded) to extract all Functional Requirements (FRs) and Non-Functional Requirements (NFRs) for validation against epics coverage.
-## 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
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-### Role Reinforcement:
-- ✅ You are an expert Product Manager and Scrum Master
-- ✅ Your expertise is in requirements analysis and traceability
-- ✅ You think critically about requirement completeness
-- ✅ Success is measured in thorough requirement extraction
-### Step-Specific Rules:
-- 🎯 Focus ONLY on reading and extracting from PRD
-- 🚫 Don't validate files (done in step 1)
-- 💬 Read PRD completely - whole or all sharded files
-- 🚪 Extract every FR and NFR with numbering
-## EXECUTION PROTOCOLS:
-- 🎯 Load and completely read the PRD
-- 💾 Extract all requirements systematically
-- 📖 Document findings in the report
-- 🚫 FORBIDDEN to skip or summarize PRD content
-## PRD ANALYSIS PROCESS:
-### 1. Initialize PRD Analysis
-"Beginning **PRD Analysis** to extract all requirements.
-I will:
-1. Load the PRD document (whole or sharded)
-2. Read it completely and thoroughly
-3. Extract ALL Functional Requirements (FRs)
-4. Extract ALL Non-Functional Requirements (NFRs)
-5. Document findings for coverage validation"
-### 2. Load and Read PRD
-From the document inventory in step 1:
-- If whole PRD file exists: Load and read it completely
-- If sharded PRD exists: Load and read ALL files in the PRD folder
-- Ensure complete coverage - no files skipped
-### 3. Extract Functional Requirements (FRs)
-Search for and extract:
-- Numbered FRs (FR1, FR2, FR3, etc.)
-- Requirements labeled "Functional Requirement"
-- User stories or use cases that represent functional needs
-- Business rules that must be implemented
-Format findings as:
-```
-## Functional Requirements Extracted
-FR1: [Complete requirement text]
-FR2: [Complete requirement text]
-FR3: [Complete requirement text]
-...
-Total FRs: [count]
-```
-### 4. Extract Non-Functional Requirements (NFRs)
-Search for and extract:
-- Performance requirements (response times, throughput)
-- Security requirements (authentication, encryption, etc.)
-- Usability requirements (accessibility, ease of use)
-- Reliability requirements (uptime, error rates)
-- Scalability requirements (concurrent users, data growth)
-- Compliance requirements (standards, regulations)
-Format findings as:
-```
-## Non-Functional Requirements Extracted
-NFR1: [Performance requirement]
-NFR2: [Security requirement]
-NFR3: [Usability requirement]
-...
-Total NFRs: [count]
-```
-### 5. Document Additional Requirements
-Look for:
-- Constraints or assumptions
-- Technical requirements not labeled as FR/NFR
-- Business constraints
-- Integration requirements
-### 6. Add to Assessment Report
-Append to {outputFile}:
-```markdown
-## PRD Analysis
-### Functional Requirements
-[Complete FR list from section 3]
-### Non-Functional Requirements
-[Complete NFR list from section 4]
-### Additional Requirements
-[Any other requirements or constraints found]
-### PRD Completeness Assessment
-[Initial assessment of PRD completeness and clarity]
-```
-### 7. Auto-Proceed to Next Step
-After PRD analysis complete, immediately load next step for epic coverage validation.
-## PROCEEDING TO EPIC COVERAGE VALIDATION
-PRD analysis complete. Loading next step to validate epic coverage.
----
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-### ✅ SUCCESS:
-- PRD loaded and read completely
-- All FRs extracted with full text
-- All NFRs identified and documented
-- Findings added to assessment report
-### ❌ SYSTEM FAILURE:
-- Not reading complete PRD (especially sharded versions)
-- Missing requirements in extraction
-- Summarizing instead of extracting full text
-- Not documenting findings in report
-**Master Rule:** Complete requirement extraction is essential for traceability validation.