siesa-agents 2.1.28 → 2.1.29

package/README.md

@@ -101,8 +101,6 @@ tu-proyecto/
     └── [workflows y configuración de GitHub]
 ```
 
-
-
 ## Soporte
 
 Si encuentras algún problema durante la instalación, por favor verifica:

package/bin/install.js

@@ -2,9 +2,9 @@
 
 const fs = require('fs-extra');
 const path = require('path');
+const { sourceMapsEnabled } = require('process');
 const readline = require('readline');
 
-
 class SiesaBmadInstaller {
   constructor() {
     // Definir las carpetas primero (nombres en el paquete vs nombres finales)
@@ -14,7 +14,8 @@ class SiesaBmadInstaller {
       { source: 'github', target: '.github' },
       { source: 'claude', target: '.claude' },
       { source: 'kiro', target: '.kiro' },
-      { source: 'resources', target: '.resources' }
+      { source: 'resources', target: '.resources' },
+      { source: 'mcp.json', target: '.mcp.json' }
     ];
     
     // Lista de archivos que se preservan automáticamente (no se crean backups)
@@ -39,7 +40,7 @@ class SiesaBmadInstaller {
     console.log('╚════██║██║██╔══╝  ╚════██║██╔══██║    ██╔══██║██║   ██║██╔══╝  ██║╚██╗██║   ██║   ╚════██║');
     console.log('███████║██║███████╗███████║██║  ██║    ██║  ██║╚██████╔╝███████╗██║ ╚████║   ██║   ███████║');
     console.log('╚══════╝╚═╝╚══════╝╚══════╝╚═╝  ╚═╝    ╚═╝  ╚═╝ ╚═════╝ ╚══════╝╚═╝  ╚═══╝   ╚═╝   ╚══════╝');
-    console.log('\n');
+    console.log('');
   }
 
   findPackageDir() {
@@ -163,8 +164,12 @@ class SiesaBmadInstaller {
 
   async getAllFiles(dir) {
     const files = [];
+    const stat = await fs.stat(dir);
+    if (stat.isFile()) {
+      files.push(dir);
+      return files;
+    }
     const items = await fs.readdir(dir);
-
     for (const item of items) {
       const fullPath = path.join(dir, item);
       const stat = await fs.stat(fullPath);
@@ -296,7 +301,6 @@ class SiesaBmadInstaller {
     const backupFiles = await this.findBackupFiles(targetPath);
     
     // Copiar la carpeta preservando technical-preferences.md
-
     await fs.copy(sourcePath, targetPath, {
       overwrite: true,
       recursive: true,

package/bmad-core/agents/dev.md

@@ -71,6 +71,7 @@ commands:
   - explain: teach me what and why you did whatever you just did in detail so I can learn. Explain to me as if you were training a junior engineer.
   - review-qa: run task `apply-qa-fixes.md'
   - run-tests: Execute linting and tests
+  - update-story-jira-status {story}: run task `update-story-jira-status.md` with the provided story file - Update story status in Jira with validation of tasks completion and QA gates
   - exit: Say goodbye as the Developer, and then abandon inhabiting this persona
 
 dependencies:
@@ -79,5 +80,7 @@ dependencies:
   tasks:
     - apply-qa-fixes.md
     - execute-checklist.md
+    - update-story-jira-status.md
+    - validate-jira-auth.md
     - validate-next-story.md
 ```

package/bmad-core/agents/pm.md

@@ -30,12 +30,22 @@ activation-instructions:
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
   - STAY IN CHARACTER!
   - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+  - JIRA CONFIGURATION CHECK: Before executing any Jira-related command (sync-prd-to-jira, create-epic, create-story), ALWAYS check if docs/jira-conf.md exists. If NOT found, inform user that project-specific Jira configuration is required and offer to run `*jira-setup` command to create it interactively.
 agent:
   name: John
   id: pm
   title: Product Manager
   icon: 📋
   whenToUse: Use for creating PRDs, product strategy, feature prioritization, roadmap planning, and stakeholder communication
+jira-config:
+  project-config-file: docs/jira-conf.md
+  global-preferences-file: .bmad-core/data/jira-preferences.md
+  required-project-fields:
+    - cloud-id: Jira Cloud ID (UUID format)
+    - jira-url: Full Jira instance URL
+    - project-key: Jira project key (e.g., PM, PROJ)
+    - project-name: Human-readable project name
+  validation: Auto-check docs/jira-conf.md before Jira operations, prompt for setup if missing
 persona:
   role: Investigative Product Strategist & Market-Savvy PM
   style: Analytical, inquisitive, data-driven, user-focused, pragmatic
@@ -64,7 +74,10 @@ commands:
   - create-prd: run task create-doc.md with template prd-tmpl.yaml
   - create-story: Create user story from requirements (task brownfield-create-story)
   - doc-out: Output full document to current destination file
+  - jira-setup: Configure Jira integration (provider, project, organization)
   - shard-prd: run the task shard-doc.md for the provided prd.md (ask if not found)
+  - sync-epic-files-to-jira: Sync individual epic files from docs/prd/ to Jira (task sync-epic-files-to-jira.md)
+  - sync-prd-to-jira: Automatically create Jira epics and stories from PRD (task sync-prd-to-jira.md)
   - yolo: Toggle Yolo Mode
   - exit: Exit (confirm)
 dependencies:
@@ -72,6 +85,7 @@ dependencies:
     - change-checklist.md
     - pm-checklist.md
   data:
+    - jira-preferences.md
     - technical-preferences.md
   tasks:
     - brownfield-create-epic.md
@@ -80,8 +94,13 @@ dependencies:
     - create-deep-research-prompt.md
     - create-doc.md
     - execute-checklist.md
+    - jira-setup.md
     - shard-doc.md
+    - sync-epic-files-to-jira.md
+    - sync-prd-to-jira.md
+    - validate-jira-auth.md
   templates:
     - brownfield-prd-tmpl.yaml
+    - jira-conf-tmpl.md
     - prd-tmpl.yaml
 ```

package/bmad-core/agents/po.md

@@ -30,6 +30,7 @@ activation-instructions:
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
   - STAY IN CHARACTER!
   - CRITICAL: On activation, ONLY greet user, auto-run `*help`, and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+  - JIRA CONFIGURATION CHECK: Before executing sync-story-to-jira command, ALWAYS check if docs/jira-conf.md exists. If NOT found, inform user that project-specific Jira configuration is required and offer to run `*jira-setup` command to create it interactively.
 agent:
   name: Sarah
   id: po
@@ -37,6 +38,15 @@ agent:
   icon: 📝
   whenToUse: Use for backlog management, story refinement, acceptance criteria, sprint planning, and prioritization decisions
   customization: null
+jira-config:
+  project-config-file: docs/jira-conf.md
+  global-preferences-file: .bmad-core/data/jira-preferences.md
+  required-project-fields:
+    - cloud-id: Jira Cloud ID (UUID format)
+    - jira-url: Full Jira instance URL
+    - project-key: Jira project key (e.g., PM, PROJ)
+    - project-name: Human-readable project name
+  validation: Auto-check docs/jira-conf.md before Jira operations, prompt for setup if missing
 persona:
   role: Technical Product Owner & Process Steward
   style: Meticulous, analytical, detail-oriented, systematic, collaborative
@@ -64,7 +74,11 @@ commands:
   - create-story: Create user story from requirements (task brownfield-create-story)
   - doc-out: Output full document to current destination file
   - execute-checklist-po: Run task execute-checklist (checklist po-master-checklist)
+  - jira-setup: Configure Jira integration (provider, project, organization)
   - shard-doc {document} {destination}: run the task shard-doc against the optionally provided document to the specified destination
+  - sync-story-to-jira {story}: Sync approved story tasks/subtasks to Jira (task sync-story-to-jira)
+  - sync-epic-to-jira {epic-number}: Find all stories matching pattern {epic-number}.*.story.md in docs/stories/, then for EACH story execute the full sync-story-to-jira workflow creating all Jira subtasks (task sync-stories-batch-to-jira with scope epic-{epic-number})
+  - update-epic-status {epic-number}: Batch update status of all stories in an epic (task update-epic-stories-jira-status)
   - validate-story-draft {story}: run the task validate-next-story against the provided story file
   - yolo: Toggle Yolo Mode off on - on will skip doc section confirmations
   - exit: Exit (confirm)
@@ -72,11 +86,19 @@ dependencies:
   checklists:
     - change-checklist.md
     - po-master-checklist.md
+  data:
+    - jira-preferences.md
   tasks:
     - correct-course.md
     - execute-checklist.md
+    - jira-setup.md
     - shard-doc.md
+    - sync-stories-batch-to-jira.md
+    - sync-story-to-jira.md
+    - update-epic-stories-jira-status.md
+    - validate-jira-auth.md
     - validate-next-story.md
   templates:
+    - jira-conf-tmpl.md
     - story-tmpl.yaml
 ```

package/bmad-core/data/jira-preferences.md

@@ -0,0 +1,153 @@
+# Jira Integration Preferences
+
+## Connection Configuration
+
+### Provider Settings
+- **Provider:** `jira`
+- **Cloud ID:** `3b04e1a3-a260-4679-bdc8-0440507fbe26`
+- **Jira URL:** `https://siesa-test-sandbox.atlassian.net`
+
+### Project Configuration
+- **Project Key:** `PM`
+- **Project Name:** `Prueba MCP`
+
+## Issue Type Configuration
+
+### Epic Configuration
+- **Issue Type:** `Epic`
+- **Issue Type ID:** `10317`
+- **Default Epic Name Prefix:** _(none, use clean titles)_
+
+### Story Configuration
+- **Issue Type:** `Story`
+- **Issue Type ID:** `10316`
+- **Default Story Name Prefix:** _(none, use clean titles)_
+
+### Other Available Issue Types
+- **Task:** `10314`
+- **Bug:** `10315`
+- **Subtarea:** `10318`
+
+## Field Mappings
+
+### Standard Fields
+- **Summary:** Maps to Epic/Story title
+- **Description:** Maps to Epic/Story description  
+- **Priority:** Default is `Medium` (options: `Highest`, `High`, `Medium`, `Low`, `Lowest`)
+- **Labels:** Auto-generated from PRD metadata (e.g., `prd-sync`, `automated`, epic name)
+
+### Custom Fields (Proyecto PM)
+
+#### Story Custom Fields (REQUIRED)
+- **Acceptance Criteria:** `customfield_10136` - **MANDATORY for Stories** - Success conditions extracted from PRD
+
+#### Optional Custom Fields
+- **Story Points:** `customfield_10016` - Effort estimation (optional)
+- **Sprint:** `customfield_10020` - Sprint assignment (optional, array type)
+- **Start Date:** `customfield_10015` - Planning date (optional)
+
+#### Epic Custom Fields
+_(No custom fields required for Epics in this project)_
+
+## PRD Parsing Configuration
+
+### Epic Detection
+Epics are identified in PRD by:
+- **Section Headers:** Level 2-3 headers (`##` or `###`) in the PRD containing "Epic", "Feature Set", or "Module"
+- **YAML Frontmatter:** `epics:` section in PRD metadata
+- **Explicit Markers:** `<!-- EPIC: Epic Name -->` in PRD
+
+### Story Detection
+Stories are identified in PRD by:
+- **Subsections:** Level 4+ headers (`####`) under epic sections
+- **List Items:** Numbered or bulleted lists under "User Stories" or "Requirements" sections
+- **User Story Format:** Text matching "As a [role], I want [action], so that [benefit]"
+
+### Content Extraction Rules
+- **Epic Goal:** First paragraph after epic header
+- **Epic Description:** Full content of epic section (required for Jira description field)
+- **Story Description:** Content immediately following story identifier
+- **Acceptance Criteria (REQUIRED):** Sections marked with "Acceptance Criteria", "AC:", "Definition of Done", or checkbox lists - **MUST BE EXTRACTED for all Stories**
+- **Technical Details:** Sections marked with "Technical Notes", "Implementation", or "Tech Stack"
+
+## Automation Preferences
+
+### Batch Creation Settings
+- **Create Epics First:** `true` - Create all epics before stories
+- **Link Stories Automatically:** `true` - Auto-link stories to parent epics
+- **Preserve PRD Structure:** `true` - Maintain hierarchy from PRD
+- **Dry Run Mode:** `false` - Set to `true` to preview without creating
+
+### Naming Conventions
+- **Epic Naming:** `{Epic Name} - {Brief Description}`
+- **Story Naming:** `{User Role}: {Action/Capability}`
+- **Include PRD Reference:** `true` - Add PRD source reference in description
+
+### Default Values
+- **Default Assignee:** `unassigned` (or specify username)
+- **Default Sprint:** `unassigned` (or specify sprint name)
+- **Default Priority:** `Medium`
+- **Default Story Points:** `null` (will be estimated later)
+
+## Error Handling
+
+### Duplicate Detection
+- **Check Existing Issues:** `true` - Prevent duplicate creation
+- **Match Criteria:** `summary` + `labels` containing `prd-sync`
+- **On Duplicate:** `skip` | `update` | `create-new`
+
+### Failed Creation Handling
+- **Continue on Error:** `true` - Continue creating remaining items
+- **Log Failed Items:** `true` - Report items that couldn't be created
+- **Retry Failed:** `false` - Manual retry required
+
+## Important Rules for Proyecto PM
+
+### Story Creation Requirements
+⚠️ **CRITICAL:** When creating Stories in the PM project:
+
+1. **Acceptance Criteria are MANDATORY**
+   - ALWAYS extract acceptance criteria from the PRD
+   - ALWAYS populate `customfield_10136` with acceptance criteria
+   - If no acceptance criteria found in PRD, STOP and request them from user before creating the Story
+   - Format: Use bullet points or numbered lists
+
+2. **Field Population**
+   - `summary`: Story title (required)
+   - `description`: Story description (required)
+   - `customfield_10136`: Acceptance criteria (REQUIRED - cannot be empty)
+   - `customfield_10016`: Story points (optional - leave empty if not in PRD)
+
+3. **Quality Standards**
+   - Acceptance criteria must be clear, testable, and specific
+   - Each criterion should be verifiable
+   - Use format: "- Criterion 1\n- Criterion 2\n- Criterion 3"
+
+### Epic Creation Requirements
+- Epics do NOT require custom fields in this project
+- Use standard `summary` and `description` fields only
+- Description should include the epic goal and full context
+
+## Notes
+
+### Finding Your Custom Field IDs
+The custom field IDs for this project are already configured above. If you need to find others:
+
+1. Go to Jira Settings > Issues > Custom Fields
+2. Click on the custom field you want to use
+3. Look at the URL - the ID is in the format `customfield_XXXXX`
+
+Or use the Jira API:
+```bash
+curl -u email@example.com:api_token \
+  https://siesa-test-sandbox.atlassian.net/rest/api/3/field
+```
+
+### Provider Information
+**Provider = `jira`** means we're using Atlassian Jira Cloud as our issue tracking system.
+Other options exist (GitHub, GitLab, Azure DevOps, Linear) but this project uses Jira.
+
+---
+
+**Last Updated:** 2025-12-10
+**Configuration Version:** 1.0.0

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

@@ -75,10 +75,41 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
 - Ensure file paths, component locations, or module names align with defined structures
 - Document any structural conflicts in "Project Structure Notes" section within the story draft
 
+### 4.5. Elicit Jira Link (If Exists)
+
+```elicit
+path: Check for existing Jira issue
+format: |
+  Does this story already have a Jira issue created?
+  
+  If yes, provide the Jira issue key (e.g., PM-9) or full URL.
+  If no, type 'no' or leave empty.
+  
+  Jira link (or 'no'):
+```
+
+**Action:** Handle Jira link information
+
+- [ ] Accept user input
+- [ ] If provided: Extract Jira key (e.g., PM-9) and construct full URL using jira-conf.md settings
+- [ ] If not provided: Set default message "Not synced to Jira yet"
+- [ ] Store for use in Jira Information section
+
 ### 5. Populate Story Template with Full Context
 
 - Create new story file: `{devStoryLocation}/{epicNum}.{storyNum}.story.md` using Story Template
 - Fill in basic story information: Title, Status (Draft), Story statement, Acceptance Criteria from Epic
+- **`Jira Information` section:**
+  - If Jira key was provided: Populate with key and full URL
+  - If not provided: Set with default message:
+    ```markdown
+    ## Jira Information
+    
+    **Jira Issue Key:** Not synced to Jira yet
+    **Jira URL:** Story will be synced to Jira using sync-story-to-jira task
+    
+    _Note: Tasks will not be created in Jira until this story has an associated Jira issue._
+    ```
 - **`Dev Notes` section (CRITICAL):**
   - CRITICAL: This section MUST contain ONLY information extracted from architecture documents. NEVER invent or assume technical details.
   - Include ALL relevant technical details from Steps 2-3, organized by category: