siesa-agents 2.1.36 → 2.1.37

package/bmad-core/tasks/index-docs.md

@@ -1,175 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# Index Documentation Task
-
-## Purpose
-
-This task maintains the integrity and completeness of the `docs/index.md` file by scanning all documentation files and ensuring they are properly indexed with descriptions. It handles both root-level documents and documents within subfolders, organizing them hierarchically.
-
-## Task Instructions
-
-You are now operating as a Documentation Indexer. Your goal is to ensure all documentation files are properly cataloged in the central index with proper organization for subfolders.
-
-### Required Steps
-
-1. First, locate and scan:
-   - The `docs/` directory and all subdirectories
-   - The existing `docs/index.md` file (create if absent)
-   - All markdown (`.md`) and text (`.txt`) files in the documentation structure
-   - Note the folder structure for hierarchical organization
-
-2. For the existing `docs/index.md`:
-   - Parse current entries
-   - Note existing file references and descriptions
-   - Identify any broken links or missing files
-   - Keep track of already-indexed content
-   - Preserve existing folder sections
-
-3. For each documentation file found:
-   - Extract the title (from first heading or filename)
-   - Generate a brief description by analyzing the content
-   - Create a relative markdown link to the file
-   - Check if it's already in the index
-   - Note which folder it belongs to (if in a subfolder)
-   - If missing or outdated, prepare an update
-
-4. For any missing or non-existent files found in index:
-   - Present a list of all entries that reference non-existent files
-   - For each entry:
-     - Show the full entry details (title, path, description)
-     - Ask for explicit confirmation before removal
-     - Provide option to update the path if file was moved
-     - Log the decision (remove/update/keep) for final report
-
-5. Update `docs/index.md`:
-   - Maintain existing structure and organization
-   - Create level 2 sections (`##`) for each subfolder
-   - List root-level documents first
-   - Add missing entries with descriptions
-   - Update outdated entries
-   - Remove only entries that were confirmed for removal
-   - Ensure consistent formatting throughout
-
-### Index Structure Format
-
-The index should be organized as follows:
-
-```markdown
-# Documentation Index
-
-## Root Documents
-
-### [Document Title](./document.md)
-
-Brief description of the document's purpose and contents.
-
-### [Another Document](./another.md)
-
-Description here.
-
-## Folder Name
-
-Documents within the `folder-name/` directory:
-
-### [Document in Folder](./folder-name/document.md)
-
-Description of this document.
-
-### [Another in Folder](./folder-name/another.md)
-
-Description here.
-
-## Another Folder
-
-Documents within the `another-folder/` directory:
-
-### [Nested Document](./another-folder/document.md)
-
-Description of nested document.
-```
-
-### Index Entry Format
-
-Each entry should follow this format:
-
-```markdown
-### [Document Title](relative/path/to/file.md)
-
-Brief description of the document's purpose and contents.
-```
-
-### Rules of Operation
-
-1. NEVER modify the content of indexed files
-2. Preserve existing descriptions in index.md when they are adequate
-3. Maintain any existing categorization or grouping in the index
-4. Use relative paths for all links (starting with `./`)
-5. Ensure descriptions are concise but informative
-6. NEVER remove entries without explicit confirmation
-7. Report any broken links or inconsistencies found
-8. Allow path updates for moved files before considering removal
-9. Create folder sections using level 2 headings (`##`)
-10. Sort folders alphabetically, with root documents listed first
-11. Within each section, sort documents alphabetically by title
-
-### Process Output
-
-The task will provide:
-
-1. A summary of changes made to index.md
-2. List of newly indexed files (organized by folder)
-3. List of updated entries
-4. List of entries presented for removal and their status:
-   - Confirmed removals
-   - Updated paths
-   - Kept despite missing file
-5. Any new folders discovered
-6. Any other issues or inconsistencies found
-
-### Handling Missing Files
-
-For each file referenced in the index but not found in the filesystem:
-
-1. Present the entry:
-
-   ```markdown
-   Missing file detected:
-   Title: [Document Title]
-   Path: relative/path/to/file.md
-   Description: Existing description
-   Section: [Root Documents | Folder Name]
-
-   Options:
-
-   1. Remove this entry
-   2. Update the file path
-   3. Keep entry (mark as temporarily unavailable)
-
-   Please choose an option (1/2/3):
-   ```
-
-2. Wait for user confirmation before taking any action
-3. Log the decision for the final report
-
-### Special Cases
-
-1. **Sharded Documents**: If a folder contains an `index.md` file, treat it as a sharded document:
-   - Use the folder's `index.md` title as the section title
-   - List the folder's documents as subsections
-   - Note in the description that this is a multi-part document
-
-2. **README files**: Convert `README.md` to more descriptive titles based on content
-
-3. **Nested Subfolders**: For deeply nested folders, maintain the hierarchy but limit to 2 levels in the main index. Deeper structures should have their own index files.
-
-## Required Input
-
-Please provide:
-
-1. Location of the `docs/` directory (default: `./docs`)
-2. Confirmation of write access to `docs/index.md`
-3. Any specific categorization preferences
-4. Any files or directories to exclude from indexing (e.g., `.git`, `node_modules`)
-5. Whether to include hidden files/folders (starting with `.`)
-
-Would you like to proceed with documentation indexing? Please provide the required input above.

package/bmad-core/tasks/jira-setup.md

@@ -1,396 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# Jira Setup Task
-
-## Purpose
-
-Configure project-specific Jira integration by collecting project information and validating authentication with Jira Cloud. This task interactively guides the user through setup and automatically retrieves project details using the Jira MCP integration.
-
-## When to Use This Task
-
-**Use this task when:**
-
-- Setting up Jira integration for the first time
-- `docs/jira-conf.md` doesn't exist
-- Reconfiguring Jira connection for a different project
-- Jira authentication needs to be validated
-
-**Prerequisites:**
-
-- Jira MCP integration must be available
-- User must have access to a Jira Cloud instance
-- User must know their Jira project key (or be able to find it)
-
-## Instructions
-
-### Phase 1: Pre-Configuration Validation
-
-#### Step 1: Check for Existing Configuration
-
-**Action:** Check if configuration already exists
-
-- [ ] Check if `docs/jira-conf.md` exists
-- [ ] If exists, load current configuration
-- [ ] Display current settings to user
-
-**If Configuration Exists:**
-```elicit
-path: Configuration already exists
-format: |
-  ⚠️ Jira configuration already exists at `docs/jira-conf.md`
-  
-  Current Settings:
-  - Project Key: {{current_project_key}}
-  - Project Name: {{current_project_name}}
-  - Cloud ID: {{current_cloud_id}}
-  
-  Options:
-  1. Keep existing configuration (cancel setup)
-  2. Reconfigure with new project
-  3. Validate and update existing configuration
-  
-  Enter selection (1-3):
-```
-
-**If User Selects Option 1:** Exit task gracefully
-**If User Selects Option 2:** Continue to Step 2
-**If User Selects Option 3:** Skip to Step 4 (validation)
-
-#### Step 2: Elicit Project Key
-
-**CRITICAL:** This step requires user interaction - DO NOT skip or auto-fill
-
-```elicit
-path: Collect Jira project key
-format: |
-  🔧 Jira Project Configuration
-  
-  I need your Jira Project Key to set up the integration.
-  The Cloud ID and Jira URL will be retrieved automatically via MCP.
-  
-  **Jira Project Key**
-  Your project key (e.g., PM, PROJ, SCRUM)
-  
-  💡 Find it in Jira: Project Settings > Details
-  💡 Usually 2-10 uppercase letters
-  
-  Enter Project Key:
-```
-
-**Action:** Validate project key format
-
-- [ ] Ensure not empty
-- [ ] Convert to uppercase if needed
-- [ ] Typically 2-10 characters
-- [ ] Store project key
-- [ ] If invalid, re-prompt user
-
-### Phase 2: Retrieve Project Details via MCP
-
-#### Step 3: Authenticate and Retrieve Cloud ID
-
-**CRITICAL:** Use MCP to authenticate and automatically retrieve Jira Cloud ID
-
-**Note:** If authentication fails here during setup, this is expected for first-time configuration. However, for subsequent operations after setup is complete, always use `validate-jira-auth.md` task to check authentication before proceeding.
-
-**Action:** Use GitKraken MCP to retrieve accessible Jira resources
-
-```output
-🔄 Connecting to Jira via MCP...
-🔄 Retrieving Cloud ID for project: {{project_key}}
-```
-
-**Execute MCP Call:**
-
-```action
-Call MCP Function: mcp_gitkraken_issues_assigned_to_me
-Parameters:
-  - provider: "jira"
-  
-This call will:
-1. Trigger Jira authentication if not already authenticated (browser OAuth flow)
-2. Return issues which contain the cloudId in the response metadata
-3. Extract the Cloud ID from the response
-```
-
-**Expected Outcomes:**
-
-**Authentication Required (First Time):**
-```output
-🔐 Jira Authentication Required
-
-A browser window will open for Jira authentication.
-
-Steps:
-1. Browser opens automatically to Jira login
-2. Log in with your Jira account
-3. Authorize the MCP integration
-4. Return here when authentication is complete
-
-⏳ Waiting for authentication...
-```
-
-**After user authenticates, the MCP call will return with cloudId**
-
-**Success - Cloud ID Retrieved:**
-```output
-✅ Authentication successful!
-✅ Cloud ID retrieved: {{cloud_id}}
-✅ Jira URL detected: {{jira_url}}
-
-Validating project access for: {{project_key}}
-```
-
-**Authentication Failed:**
-```elicit
-path: Authentication failed
-format: |
-  ❌ Failed to authenticate with Jira
-  
-  Error: {{error_message}}
-  
-  Possible causes:
-  - MCP integration not configured
-  - Network issues
-  - Browser blocked OAuth flow
-  - User cancelled authentication
-  
-  Options:
-  1. Retry authentication
-  2. Check MCP server status
-  3. Cancel setup
-  
-  Enter selection (1-3):
-```
-
-**If Option 1:** Retry Step 3
-**If Option 2:** Display MCP troubleshooting help, then retry
-**If Option 3:** Exit task gracefully
-
-#### Step 4: Verify Project Access and Get Project Name
-
-**Action:** Use the retrieved Cloud ID to verify project access and get project details
-
-```output
-🔄 Verifying project access...
-🔄 Retrieving project name for: {{project_key}}
-```
-
-**Execute MCP Call:**
-
-```action
-Call MCP Function: mcp_gitkraken_issues_assigned_to_me
-Parameters:
-  - provider: "jira"
-  
-From the response:
-1. Verify issues from the specified project are accessible
-2. Extract Project Name from issue metadata
-3. Confirm the project exists and user has access
-```
-
-**Alternative - If no issues assigned:**
-```action
-You can also try to search for any issue in the project to verify access.
-The response will contain project metadata including the project name.
-```
-
-**Expected Output:**
-```output
-✅ Project Verification Complete
-
-Retrieved Details:
-- Project Key: {{project_key}}
-- Project Name: {{project_name}} (retrieved from Jira)
-- Cloud ID: {{cloud_id}} (retrieved via MCP)
-- Jira URL: {{jira_url}} (detected from MCP)
-- Access: Confirmed ✓
-
-All information retrieved successfully via MCP.
-```
-
-**Project Not Found:**
-```elicit
-path: Project not accessible
-format: |
-  ❌ Cannot access project: {{project_key}}
-  
-  Possible causes:
-  - Project key is incorrect
-  - User doesn't have access to this project
-  - Project doesn't exist
-  
-  Options:
-  1. Re-enter project key
-  2. Request project access from Jira admin
-  3. Cancel setup
-  
-  Enter selection (1-3):
-```
-
-**If Option 1:** Return to Step 2
-**If Option 2:** Display Jira admin contact info, then exit
-**If Option 3:** Exit task gracefully
-
-### Phase 3: Configuration File Creation
-
-#### Step 5: Create Configuration File
-
-**Action:** Create `docs/jira-conf.md` with validated settings
-
-- [ ] Create `docs/` directory if it doesn't exist
-- [ ] Load template from `.bmad-core/templates/jira-conf-tmpl.md`
-- [ ] Replace placeholders:
-  - `{PROJECT_KEY}` → validated project key
-  - `{PROJECT_NAME}` → project name (or project key if not provided)
-  - `{CLOUD_ID}` → validated cloud ID
-- [ ] Add Jira URL as additional metadata
-- [ ] Write file to `docs/jira-conf.md`
-
-**Template Content:**
-```markdown
-# Jira Project Configuration
-
-**Project Key:** `{{project_key}}`
-**Project Name:** `{{project_name}}`
-**Cloud ID:** `{{cloud_id}}`
-**Jira URL:** `{{jira_url}}`
-
----
-
-_Note: Cloud ID and Jira URL were automatically retrieved via MCP during `*jira-setup`._
-_Last Updated: {{current_date}}_
-```
-
-#### Step 6: Store Authentication Reference
-
-**Action:** Optionally create a reference file in `.claude/instructions.md` for persistent context
-
-```markdown
-Create or update `.claude/instructions.md` with:
-
-# Instrucciones para Jira - Proyecto {{project_key}}
-
-## Configuracion del Proyecto
-- **Cloud ID:** {{cloud_id}}
-- **Project Key:** {{project_key}}
-- **URL:** {{jira_url}}
-
-## Reglas para crear Issues
-
-### Story (Historia de Usuario)
-Al crear una **Story** en el proyecto {{project_key}}, SIEMPRE debes:
-
-1. Solicitar al usuario los "Criterios de Aceptacion" antes de crear el issue
-2. Incluir el campo personalizado para criterios de aceptacion si está disponible
-
-_(Add project-specific Jira instructions here)_
-```
-
-#### Step 7: Final Confirmation
-
-```output
-═══════════════════════════════════════════════════════════════
-  ✅ JIRA SETUP COMPLETE
-═══════════════════════════════════════════════════════════════
-
-Configuration saved to: `docs/jira-conf.md`
-
-Project Details:
-- Project Key: {{project_key}}
-- Project Name: {{project_name}}
-- Cloud ID: {{cloud_id}}
-- Jira URL: {{jira_url}}
-- Authentication: ✅ Verified
-
-Available Commands:
-- `*sync-prd-to-jira` - Sync PRD epics and stories to Jira
-- `*create-epic` - Create individual epic in Jira
-- `*create-story` - Create individual story in Jira
-- `*sync-story-to-jira` - Sync story tasks/subtasks to Jira
-
-Next Steps:
-1. Use these commands to sync your documentation with Jira
-2. All Jira operations will now use the configured project
-3. Re-run `*jira-setup` anytime to reconfigure
-
-═══════════════════════════════════════════════════════════════
-```
-
-## Success Criteria
-
-The setup is successful when:
-
-1. User provided valid Jira URL, Project Key, and Cloud ID
-2. MCP Jira authentication completed successfully
-3. Project access verified
-4. Configuration file created at `docs/jira-conf.md`
-5. All settings validated and working
-
-## Error Handling
-
-### Invalid URL Format
-```output
-❌ Invalid Jira URL format
-
-Expected: https://yourcompany.atlassian.net
-Received: {{invalid_url}}
-
-Please enter a valid Jira Cloud URL.
-```
-
-### Invalid Cloud ID Format
-```output
-❌ Invalid Cloud ID format
-
-Expected: UUID format (e.g., 3b04e1a3-a260-4679-bdc8-0440507fbe26)
-Received: {{invalid_cloud_id}}
-
-Please enter a valid Cloud ID.
-```
-
-### Authentication Timeout
-```output
-⏱️ Authentication timeout
-
-The authentication process took too long or was cancelled.
-
-Options:
-1. Retry authentication
-2. Check MCP integration status
-3. Cancel setup
-
-Enter selection (1-3):
-```
-
-### MCP Not Available
-```output
-❌ Jira MCP Integration Not Available
-
-The GitKraken MCP integration for Jira is not available.
-
-Please ensure:
-1. MCP is properly installed and configured
-2. GitKraken MCP server is running
-3. Jira provider is enabled in MCP settings
-
-Cannot proceed without MCP integration.
-```
-
-## Important Notes
-
-- **User Input Required:** Only Project Key needs to be provided by user
-- **Automatic Retrieval:** Cloud ID and Jira URL are retrieved automatically via MCP
-- **Authentication:** MCP handles OAuth flow automatically via browser
-- **Project Name:** Retrieved from Jira metadata automatically
-- **Validation:** Always validate authentication before saving configuration
-- **Re-configuration:** Safe to run multiple times - will prompt before overwriting
-- **Template Dependency:** Requires `.bmad-core/templates/jira-conf-tmpl.md`
-- **MCP Dependency:** Requires GitKraken MCP with Jira integration
-
-## Related Commands
-
-- `*sync-prd-to-jira` - Sync PRD to Jira (requires this setup)
-- `*create-epic` - Create Jira epic (requires this setup)
-- `*create-story` - Create Jira story (requires this setup)
-- `*sync-story-to-jira` - Sync story tasks (requires this setup)

package/bmad-core/tasks/kb-mode-interaction.md

@@ -1,77 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# KB Mode Interaction Task
-
-## Purpose
-
-Provide a user-friendly interface to the BMad knowledge base without overwhelming users with information upfront.
-
-## Instructions
-
-When entering KB mode (\*kb-mode), follow these steps:
-
-### 1. Welcome and Guide
-
-Announce entering KB mode with a brief, friendly introduction.
-
-### 2. Present Topic Areas
-
-Offer a concise list of main topic areas the user might want to explore:
-
-**What would you like to know more about?**
-
-1. **Setup & Installation** - Getting started with BMad
-2. **Workflows** - Choosing the right workflow for your project
-3. **Web vs IDE** - When to use each environment
-4. **Agents** - Understanding specialized agents and their roles
-5. **Documents** - PRDs, Architecture, Stories, and more
-6. **Agile Process** - How BMad implements Agile methodologies
-7. **Configuration** - Customizing BMad for your needs
-8. **Best Practices** - Tips for effective BMad usage
-
-Or ask me about anything else related to BMad-Method!
-
-### 3. Respond Contextually
-
-- Wait for user's specific question or topic selection
-- Provide focused, relevant information from the knowledge base
-- Offer to dive deeper or explore related topics
-- Keep responses concise unless user asks for detailed explanations
-
-### 4. Interactive Exploration
-
-- After answering, suggest related topics they might find helpful
-- Maintain conversational flow rather than data dumping
-- Use examples when appropriate
-- Reference specific documentation sections when relevant
-
-### 5. Exit Gracefully
-
-When user is done or wants to exit KB mode:
-
-- Summarize key points discussed if helpful
-- Remind them they can return to KB mode anytime with \*kb-mode
-- Suggest next steps based on what was discussed
-
-## Example Interaction
-
-**User**: \*kb-mode
-
-**Assistant**: I've entered KB mode and have access to the full BMad knowledge base. I can help you with detailed information about any aspect of BMad-Method.
-
-**What would you like to know more about?**
-
-1. **Setup & Installation** - Getting started with BMad
-2. **Workflows** - Choosing the right workflow for your project
-3. **Web vs IDE** - When to use each environment
-4. **Agents** - Understanding specialized agents and their roles
-5. **Documents** - PRDs, Architecture, Stories, and more
-6. **Agile Process** - How BMad implements Agile methodologies
-7. **Configuration** - Customizing BMad for your needs
-8. **Best Practices** - Tips for effective BMad usage
-
-Or ask me about anything else related to BMad-Method!
-
-**User**: Tell me about workflows
-
-**Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]