siesa-agents 2.1.35 → 2.1.37

package/bmad-core/tasks/validate-jira-auth.md

@@ -1,251 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# Validate Jira Authentication Task
-
-## Purpose
-
-Validate that the Jira MCP integration is properly authenticated before executing any Jira operations. This task prevents workflow disruptions caused by expired authentication sessions by proactively checking authentication status and instructing users to re-authenticate when needed.
-
-## When to Use This Task
-
-**CRITICAL:** This task MUST be executed as the FIRST step before ANY Jira MCP operation, including:
-
-- Creating epics or stories in Jira
-- Syncing PRD to Jira
-- Syncing story tasks to Jira  
-- Updating story status
-- Retrieving project information
-- Any call to `mcp_gitkraken_*` tools with `provider: "jira"`
-
-**Do NOT skip this validation** - authentication failures mid-workflow cause confusion and wasted execution.
-
-## Instructions
-
-### Step 1: Attempt Authentication Check
-
-**Action:** Make a lightweight Jira MCP call to verify authentication status
-
-```output
-🔐 Validating Jira authentication...
-```
-
-**Execute Test Call:**
-
-```action
-Call MCP Function: mcp_gitkraken_issues_assigned_to_me
-Parameters:
-  - provider: "jira"
-  - page: 1
-
-This is a lightweight call that will:
-1. Return immediately if authenticated
-2. Fail with authentication error if session expired
-3. Not create or modify any data
-```
-
-### Step 2: Interpret Response
-
-**Expected Outcomes:**
-
-#### ✅ Scenario A: Authentication Valid
-
-**Indicators:**
-- MCP call returns successfully (even if no issues found)
-- Response contains valid data structure
-- No authentication errors in response
-
-**Output:**
-```output
-✅ Jira authentication verified
-✅ MCP connection active
-```
-
-**Action:** Return success and allow workflow to continue
-
----
-
-#### ❌ Scenario B: Authentication Expired/Invalid
-
-**Indicators:**
-- MCP call fails with authentication error
-- Error message contains: "unauthorized", "authentication", "token expired", "session expired"
-- HTTP 401 or 403 error codes
-- No valid response data
-
-**Output:**
-```output
-═══════════════════════════════════════════════════════════════
-  ⚠️  AUTENTICACIÓN DE JIRA REQUERIDA
-═══════════════════════════════════════════════════════════════
-
-❌ La sesión de Jira MCP ha expirado o no está autenticada.
-
-Para continuar con operaciones de Jira, debes re-autenticarte:
-
-📋 PASOS PARA RE-AUTENTICACIÓN:
-
-1. Abre el panel de MCP en VS Code:
-   - Presiona Ctrl+Shift+P (Cmd+Shift+P en Mac)
-   - Busca: "MCP: Show MCP Panel"
-   - O usa el atajo si está configurado
-
-2. En el panel de MCP:
-   - Localiza el servidor "GitKraken Jira"
-   - Haz clic en "Connect" o "Authenticate"
-   - Se abrirá una ventana del navegador
-
-3. Completa la autenticación OAuth:
-   - Inicia sesión en Jira Cloud si es necesario
-   - Autoriza el acceso para GitKraken MCP
-   - Espera la confirmación de conexión exitosa
-
-4. Verifica la conexión:
-   - El icono de GitKraken Jira debe mostrar "Connected"
-   - Cierra el navegador y regresa a VS Code
-
-5. Reintenta el comando:
-   - Vuelve a ejecutar el comando que falló
-   - La autenticación ahora debe estar activa
-
-═══════════════════════════════════════════════════════════════
-
-❌ NO PUEDO CONTINUAR hasta que completes la re-autenticación.
-
-Razón: Las operaciones de Jira requieren autenticación válida para:
-- Crear/actualizar issues
-- Consultar información del proyecto
-- Sincronizar datos entre documentos locales y Jira
-
-Una vez que hayas completado los pasos arriba, confirma escribiendo:
-"autenticado" o "listo" para continuar.
-
-═══════════════════════════════════════════════════════════════
-```
-
-**CRITICAL:** HALT execution completely. Do NOT:
-- Attempt to continue with Jira operations
-- Try to re-authenticate programmatically  
-- Make additional MCP calls
-- Suggest workarounds or alternatives
-
-**Action:** Wait for user confirmation that they have re-authenticated
-
----
-
-#### 🔧 Scenario C: MCP Not Available
-
-**Indicators:**
-- MCP tool not found
-- MCP server not running
-- GitKraken MCP integration not installed
-
-**Output:**
-```output
-═══════════════════════════════════════════════════════════════
-  ⚠️  MCP DE JIRA NO DISPONIBLE
-═══════════════════════════════════════════════════════════════
-
-❌ El servidor MCP de GitKraken no está disponible.
-
-Posibles causas:
-- MCP no está instalado
-- El servidor MCP no está ejecutándose  
-- Configuración de MCP incorrecta
-
-📋 PASOS PARA CONFIGURAR MCP:
-
-1. Verifica que GitKraken MCP esté instalado
-2. Revisa la configuración de MCP en VS Code
-3. Reinicia el servidor MCP si es necesario
-4. Contacta al administrador si el problema persiste
-
-═══════════════════════════════════════════════════════════════
-
-❌ NO PUEDO CONTINUAR sin acceso al MCP de Jira.
-
-HALT execution.
-```
-
-### Step 3: User Confirmation (If Re-auth Required)
-
-```elicit
-path: Wait for user re-authentication confirmation
-format: |
-  ⏳ Esperando confirmación de re-autenticación...
-  
-  Has completado los pasos de autenticación en el panel de MCP?
-  
-  Opciones:
-  1. Sí, estoy autenticado - verificar de nuevo
-  2. Necesito ayuda con la autenticación
-  3. Cancelar operación
-  
-  Ingresa tu selección (1-3):
-```
-
-**If Option 1:** Retry Step 1 to verify authentication
-**If Option 2:** Display detailed troubleshooting guide
-**If Option 3:** Exit task gracefully
-
-### Step 4: Retry Verification (After User Confirms)
-
-**Action:** Repeat Step 1 to confirm authentication is now valid
-
-- [ ] Execute test MCP call again
-- [ ] Verify successful response
-- [ ] Return success if authenticated
-- [ ] If still fails, return to Step 2
-
-**Success Output:**
-```output
-✅ Re-autenticación exitosa
-✅ Conexión a Jira verificada
-✅ Listo para continuar con operaciones de Jira
-```
-
-## Integration Points
-
-**This task should be called from:**
-
-- `sync-prd-to-jira.md` - Before Phase 1, Step 1
-- `sync-story-to-jira.md` - Before Phase 1, Step 1  
-- `update-story-jira-status.md` - Before Phase 1, Step 3
-- `jira-setup.md` - Before Phase 2, Step 3
-- Any other task that uses Jira MCP
-
-**Add this step to task instructions:**
-
-```markdown
-#### Step 0: Validate Jira Authentication (REQUIRED)
-
-**Action:** Execute `validate-jira-auth.md` task
-
-- [ ] Call validate-jira-auth task
-- [ ] Verify authentication is active
-- [ ] Only proceed if validation passes
-
-**If validation fails:** HALT and instruct user to re-authenticate before continuing.
-```
-
-## Error Recovery
-
-**Common Authentication Errors:**
-
-| Error Pattern | Meaning | Solution |
-|---------------|---------|----------|
-| `401 Unauthorized` | Token expired | Re-authenticate via MCP panel |
-| `403 Forbidden` | Insufficient permissions | Check Jira access rights |
-| `oauth_token_expired` | OAuth session expired | Re-authenticate via MCP panel |
-| `ETIMEDOUT` | Network/MCP connection issue | Check MCP server status |
-
-## Notes
-
-- Authentication sessions typically expire after inactivity
-- OAuth tokens may have time-based expiration (e.g., 1 hour, 24 hours)
-- Re-authentication does NOT require reconfiguring project settings
-- `docs/jira-conf.md` configuration remains valid after re-auth
-
----
-
-**Last Updated:** 2025-12-11  
-**Task Version:** 1.0.0

package/bmad-core/tasks/validate-next-story.md

@@ -1,136 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# Validate Next Story Task
-
-## Purpose
-
-To comprehensively validate a story draft before implementation begins, ensuring it is complete, accurate, and provides sufficient context for successful development. This task identifies issues and gaps that need to be addressed, preventing hallucinations and ensuring implementation readiness.
-
-## SEQUENTIAL Task Execution (Do not proceed until current Task is complete)
-
-### 0. Load Core Configuration and Inputs
-
-- Load `.bmad-core/core-config.yaml`
-- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
-- Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`
-- Identify and load the following inputs:
-  - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`)
-  - **Parent epic**: The epic containing this story's requirements
-  - **Architecture documents**: Based on configuration (sharded or monolithic)
-  - **Story template**: `bmad-core/templates/story-tmpl.md` for completeness validation
-
-### 1. Template Completeness Validation
-
-- Load `.bmad-core/templates/story-tmpl.yaml` and extract all section headings from the template
-- **Missing sections check**: Compare story sections against template sections to verify all required sections are present
-- **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`)
-- **Agent section verification**: Confirm all sections from template exist for future agent use
-- **Structure compliance**: Verify story follows template structure and formatting
-
-### 2. File Structure and Source Tree Validation
-
-- **File paths clarity**: Are new/existing files to be created/modified clearly specified?
-- **Source tree relevance**: Is relevant project structure included in Dev Notes?
-- **Directory structure**: Are new directories/components properly located according to project structure?
-- **File creation sequence**: Do tasks specify where files should be created in logical order?
-- **Path accuracy**: Are file paths consistent with project structure from architecture docs?
-
-### 3. UI/Frontend Completeness Validation (if applicable)
-
-- **Component specifications**: Are UI components sufficiently detailed for implementation?
-- **Styling/design guidance**: Is visual implementation guidance clear?
-- **User interaction flows**: Are UX patterns and behaviors specified?
-- **Responsive/accessibility**: Are these considerations addressed if required?
-- **Integration points**: Are frontend-backend integration points clear?
-
-### 4. Acceptance Criteria Satisfaction Assessment
-
-- **AC coverage**: Will all acceptance criteria be satisfied by the listed tasks?
-- **AC testability**: Are acceptance criteria measurable and verifiable?
-- **Missing scenarios**: Are edge cases or error conditions covered?
-- **Success definition**: Is "done" clearly defined for each AC?
-- **Task-AC mapping**: Are tasks properly linked to specific acceptance criteria?
-
-### 5. Validation and Testing Instructions Review
-
-- **Test approach clarity**: Are testing methods clearly specified?
-- **Test scenarios**: Are key test cases identified?
-- **Validation steps**: Are acceptance criteria validation steps clear?
-- **Testing tools/frameworks**: Are required testing tools specified?
-- **Test data requirements**: Are test data needs identified?
-
-### 6. Security Considerations Assessment (if applicable)
-
-- **Security requirements**: Are security needs identified and addressed?
-- **Authentication/authorization**: Are access controls specified?
-- **Data protection**: Are sensitive data handling requirements clear?
-- **Vulnerability prevention**: Are common security issues addressed?
-- **Compliance requirements**: Are regulatory/compliance needs addressed?
-
-### 7. Tasks/Subtasks Sequence Validation
-
-- **Logical order**: Do tasks follow proper implementation sequence?
-- **Dependencies**: Are task dependencies clear and correct?
-- **Granularity**: Are tasks appropriately sized and actionable?
-- **Completeness**: Do tasks cover all requirements and acceptance criteria?
-- **Blocking issues**: Are there any tasks that would block others?
-
-### 8. Anti-Hallucination Verification
-
-- **Source verification**: Every technical claim must be traceable to source documents
-- **Architecture alignment**: Dev Notes content matches architecture specifications
-- **No invented details**: Flag any technical decisions not supported by source documents
-- **Reference accuracy**: Verify all source references are correct and accessible
-- **Fact checking**: Cross-reference claims against epic and architecture documents
-
-### 9. Dev Agent Implementation Readiness
-
-- **Self-contained context**: Can the story be implemented without reading external docs?
-- **Clear instructions**: Are implementation steps unambiguous?
-- **Complete technical context**: Are all required technical details present in Dev Notes?
-- **Missing information**: Identify any critical information gaps
-- **Actionability**: Are all tasks actionable by a development agent?
-
-### 10. Generate Validation Report
-
-Provide a structured validation report including:
-
-#### Template Compliance Issues
-
-- Missing sections from story template
-- Unfilled placeholders or template variables
-- Structural formatting issues
-
-#### Critical Issues (Must Fix - Story Blocked)
-
-- Missing essential information for implementation
-- Inaccurate or unverifiable technical claims
-- Incomplete acceptance criteria coverage
-- Missing required sections
-
-#### Should-Fix Issues (Important Quality Improvements)
-
-- Unclear implementation guidance
-- Missing security considerations
-- Task sequencing problems
-- Incomplete testing instructions
-
-#### Nice-to-Have Improvements (Optional Enhancements)
-
-- Additional context that would help implementation
-- Clarifications that would improve efficiency
-- Documentation improvements
-
-#### Anti-Hallucination Findings
-
-- Unverifiable technical claims
-- Missing source references
-- Inconsistencies with architecture documents
-- Invented libraries, patterns, or standards
-
-#### Final Assessment
-
-- **GO**: Story is ready for implementation
-- **NO-GO**: Story requires fixes before implementation
-- **Implementation Readiness Score**: 1-10 scale
-- **Confidence Level**: High/Medium/Low for successful implementation