siesa-agents 2.1.35 → 2.1.37

package/bmad-core/tasks/update-epic-stories-jira-status.md

@@ -1,799 +0,0 @@
-<!-- Powered by BMAD™ Core -->
-
-# Update Epic Stories Status Task
-
-## Purpose
-
-Batch update the status of all stories within an epic in Jira by transitioning them to a selected target state. This task validates that each story meets all prerequisites before allowing the transition, including checking that all tasks/subtasks are completed and QA gates have passed.
-
-## When to Use This Task
-
-**Use this task when:**
-
-- Epic implementation is complete and all stories need to move to next state
-- You want to transition multiple stories to the same status simultaneously
-- Stories within an epic are ready for batch status change (Ready for Review, Done, In Testing, etc.)
-- After completing `sync-epic-to-jira` and stories are ready for status update
-
-**Prerequisites:**
-
-- Story documents exist in `docs/stories/` matching epic pattern (e.g., `1.*.story.md` for epic 1)
-- Stories have been synced to Jira with valid issue keys
-- Jira preferences configured in `.bmad-core/data/jira-preferences.md`
-- Project-specific Jira configuration in `docs/jira-conf.md`
-- Available transitions configured or fetchable from Jira
-
-## Instructions
-
-### Phase 1: Epic Identification & Story Discovery
-
-#### Step 0: Validate Jira Authentication (REQUIRED)
-
-**CRITICAL:** Validate authentication BEFORE any Jira operations
-
-**Action:** Execute authentication check
-
-- [ ] Call `validate-jira-auth.md` task
-- [ ] Verify authentication is active
-- [ ] Only proceed if validation passes
-
-**If validation fails:** HALT and instruct user to re-authenticate via MCP panel before continuing.
-
----
-
-#### Step 1: Identify Target Epic
-
-**Input Parameter:** `{epic-number}` - Epic number provided by user when calling this task
-
-**Action:** Validate and identify epic scope
-
-- [ ] Check if `{epic-number}` parameter was provided when task was called
-- [ ] If NOT provided, use elicitation below to prompt user
-- [ ] If provided, extract epic number (e.g., "epic-1" → "1", "1" → "1")
-- [ ] Validate epic number format (must be numeric)
-
-```elicit
-path: Prompt for epic number if not provided as parameter
-condition: Only show if {epic-number} parameter is missing
-format: |
-  Which epic's stories should be updated in Jira?
-
-  Options:
-  1. Specify epic number (e.g., 1, 2, 3)
-  2. List available epics in docs/prd/
-
-  Enter epic number:
-```
-
-#### Step 2: Search for Stories in Epic
-
-**Action:** USE GLOB TOOL to search `docs/stories/` directory for stories matching epic pattern
-
-- [ ] Construct glob pattern: `docs/stories/{{epic_number}}.*.story.md`
-- [ ] Use Glob tool with constructed pattern
-- [ ] Store list of found story files
-- [ ] Count total stories found
-
-**Example Patterns:**
-- Epic 1: `docs/stories/1.*.story.md` → finds `1.1.story.md`, `1.2.story.md`, etc.
-- Epic 2: `docs/stories/2.*.story.md` → finds `2.1.story.md`, `2.2.story.md`, etc.
-
-**If No Stories Found:**
-```output
-❌ No stories found for epic {{epic_number}}
-
-Search pattern: docs/stories/{{epic_number}}.*.story.md
-Directory: docs/stories/
-
-Possible reasons:
-- Epic has no stories yet
-- Story files don't follow naming convention (N.M.story.md)
-- Epic number is incorrect
-
-Resolution:
-1. Verify epic number
-2. Check docs/stories/ directory contents
-3. Create stories using `*create-story` command
-
-HALT execution.
-```
-
-**Expected Output:**
-```output
-📋 Epic {{epic_number}} - Stories Found: {{story_count}}
-
-Stories:
-{{for each story}}
-{{index}}. {{filename}}
-{{end for}}
-```
-
-#### Step 3: Load and Validate Story Metadata
-
-**Action:** Read each story file EFFICIENTLY (sections only) and extract key metadata
-
-**CRITICAL - Read ONLY these sections per story:**
-
-**For EACH story file found, extract from specific sections:**
-- [ ] **Metadata section** (first ~30 lines):
-  - Story title
-  - Current status
-  - Jira issue key
-- [ ] **## Tasks / Subtasks section**:
-  - All tasks and subtasks (with checkbox status `[x]` or `[ ]`)
-  - Count total vs completed
-- [ ] **## QA Gates section** (if present):
-  - Gate names and statuses
-- [ ] **DO NOT read entire document** - focus only on these sections for efficiency
-
-**Data Structure to Build:**
-```javascript
-stories = [
-  {
-    filename: "1.1.auth.story.md",
-    title: "User Authentication",
-    status: "Ready for Review",
-    jiraKey: "PM-10",
-    totalTasks: 5,
-    completedTasks: 5,
-    qaGates: [
-      {name: "Code Quality", status: "PASS"},
-      {name: "Security Review", status: "PASS"}
-    ],
-    hasJiraKey: true
-  },
-  // ... more stories
-]
-```
-
-**Validation Per Story:**
-- [ ] Check if Jira issue key exists in story
-- [ ] Parse tasks/subtasks structure
-- [ ] Count total vs completed tasks
-- [ ] Extract QA gate information (if section exists)
-
-**Stories Classification:**
-```output
-Stories Metadata:
-
-Valid Stories (have Jira keys):
-{{for each story with jira_key}}
-✓ {{filename}} - {{title}}
-  Jira: {{jira_key}} | Status: {{status}}
-  Tasks: {{completed}}/{{total}} | QA Gates: {{gate_count}}
-{{end for}}
-
-Invalid Stories (missing Jira keys):
-{{for each story without jira_key}}
-⊘ {{filename}} - {{title}}
-  Reason: No Jira key found (not synced yet)
-{{end for}}
-
-Summary:
-- Total Stories: {{total_count}}
-- Valid for Update: {{valid_count}}
-- Invalid (no Jira key): {{invalid_count}}
-```
-
-**If All Stories Invalid:**
-```output
-❌ No valid stories found for epic {{epic_number}}
-
-All stories are missing Jira keys. Stories must be synced to Jira first.
-
-Resolution:
-1. Run `*sync-epic-to-jira {{epic_number}}` to sync stories
-2. Retry this command after sync completes
-
-HALT execution.
-```
-
-#### Step 4: Load Jira Configuration
-
-**Action:** Read configuration for Jira connection details
-
-- [ ] Load `.bmad-core/data/jira-preferences.md`
-- [ ] Load `docs/jira-conf.md`
-- [ ] Extract provider, project key, cloud ID
-- [ ] Verify all required connection details present
-
-**Required Configuration in `docs/jira-conf.md`:**
-```markdown
-**Project Key:** PM
-**Project Name:** Prueba MCP
-**Cloud ID:** 3b04e1a3-a260-4679-bdc8-0440507fbe26
-**Jira URL:** https://siesa-test-sandbox.atlassian.net
-```
-
-**If Configuration Missing:**
-```output
-⚠️ Jira configuration not found in `docs/jira-conf.md`.
-
-Please run the `*jira-setup` command first to configure project-specific Jira integration.
-
-Required details:
-- Project Key
-- Cloud ID
-- Jira URL
-
-HALT execution until configuration is complete.
-```
-
-### Phase 2: Load or Fetch Available Statuses (ONE TIME)
-
-#### Step 5: Check for Cached Statuses in jira-conf.md
-
-**Action:** Check if statuses are already cached in configuration
-
-- [ ] Read `docs/jira-conf.md` file
-- [ ] Look for "Available Story Statuses" section
-- [ ] Check if section exists and contains status list (lines starting with `-`)
-- [ ] If statuses found: parse and use them (go to Step 7)
-- [ ] If statuses NOT found: proceed to Step 6 to fetch from Jira
-
-**Expected Cached Format:**
-```markdown
-## Available Story Statuses
-
-- To Do
-- In Progress
-- Done
-```
-
-#### Step 6: Fetch Statuses from Jira via MCP (If Not Cached)
-
-**Action:** Query Jira MCP to get available transitions for a story in the epic
-
-**Strategy:** Get transitions from first valid story with Jira key
-
-- [ ] Select first story from valid stories list
-- [ ] Extract its Jira key (e.g., PM-10)
-- [ ] Call MCP tool `mcp__atlassian__getTransitionsForJiraIssue`
-- [ ] Extract transition names from response
-- [ ] Build formatted status list
-- [ ] Proceed to Step 6b to cache them
-
-**MCP Call:**
-```
-Tool: mcp__atlassian__getTransitionsForJiraIssue
-Parameters:
-  - cloudId: {{cloud_id}}
-  - issueIdOrKey: {{first_story_jira_key}}
-```
-
-**Extract Statuses from Response:**
-```json
-{
-  "transitions": [
-    {"id": "10", "name": "To Do", "to": {"name": "To Do"}},
-    {"id": "20", "name": "In Progress", "to": {"name": "In Progress"}},
-    {"id": "30", "name": "Done", "to": {"name": "Done"}}
-  ]
-}
-```
-
-- Parse transition names or `to.name` values
-- Deduplicate status list
-- Sort alphabetically or by workflow order
-
-**If MCP Call Fails:**
-```output
-❌ Unable to retrieve statuses from Jira via MCP.
-
-Attempted to query transitions for: {{first_story_jira_key}}
-
-Possible causes:
-- MCP connection issue
-- Invalid Jira credentials
-- Issue doesn't exist or no permissions
-
-Manual Configuration Required:
-Please add statuses manually to `docs/jira-conf.md`:
-
-## Available Story Statuses
-
-- To Do
-- In Progress
-- Done
-
-HALT execution.
-```
-
-#### Step 6b: Cache Statuses in jira-conf.md
-
-**Action:** Write fetched statuses to configuration file for future use
-
-- [ ] Read current `docs/jira-conf.md` content
-- [ ] Locate insertion point (after Jira URL, before closing notes)
-- [ ] Format statuses as markdown list
-- [ ] Insert "Available Story Statuses" section
-- [ ] Write updated content back to file
-
-**Insert Format:**
-```markdown
-## Available Story Statuses
-
-_Automatically retrieved from Jira on {{date}}. Edit this list if your workflow changes._
-
-{{#each statuses}}
-- {{name}}
-{{/each}}
-```
-
-**Success Output:**
-```output
-✅ Statuses retrieved from Jira and cached in jira-conf.md
-
-Found {{status_count}} available statuses:
-{{#each statuses}}
-- {{name}}
-{{/each}}
-
-These statuses are now cached for future use.
-```
-
-#### Step 7: Present Available Statuses to User (ONE TIME)
-
-**CRITICAL ELICITATION - DO NOT SKIP THIS STEP**
-
-**Action:** Display current story statuses and available target statuses, then WAIT for user selection
-
-- [ ] Display epic number and valid story count
-- [ ] List current status of each story in epic
-- [ ] Display numbered list of available statuses from jira-conf.md (or fetched from Jira)
-- [ ] **HALT and WAIT** for user to select target status
-- [ ] Accept user input (number selection)
-- [ ] Validate selection is within range (1 to status count)
-- [ ] Extract selected status name from the list
-- [ ] Store selected status for use in Phase 3
-
-**Output Format:**
-```output
-Epic {{epic_number}} - Status Update
-
-Stories ready for update: {{valid_count}}
-
-Current Story Statuses:
-1. {{filename_1}}: {{current_status_1}}
-2. {{filename_2}}: {{current_status_2}}
-3. {{filename_3}}: {{current_status_3}}
-
-Available Target Statuses:
-1. To Do
-2. In Progress
-3. Ready for Review
-4. Done
-
-Select target status to apply to ALL stories (enter number 1-{{status_count}}):
-```
-
-**Wait for User Input - DO NOT PROCEED without user selection**
-
-**After User Selection:**
-- [ ] Validate user entered a number
-- [ ] Validate number is within valid range
-- [ ] Extract status name from list (e.g., if user enters "4", extract "Done")
-- [ ] Store selected status name
-- [ ] Proceed to Step 7b for confirmation
-
-#### Step 7b: Confirm Batch Update Plan
-
-**CRITICAL CONFIRMATION - DO NOT SKIP**
-
-**Action:** Display batch update plan and get final confirmation
-
-```output
-═══════════════════════════════════════════════════════════════
-  BATCH STATUS UPDATE PLAN
-═══════════════════════════════════════════════════════════════
-
-Epic: {{epic_number}}
-Target Status: {{selected_status_name}}
-
-Stories to Update: {{valid_count}}
-{{for each story}}
-- {{filename}} ({{current_status}} → {{selected_status_name}})
-{{end for}}
-
-Each story will be validated for:
-✓ 100% task completion
-{{if selected_status is "Done"}}✓ All QA gates PASS{{/if}}
-✓ Valid workflow transition
-
-Continue with batch update? (yes/no):
-```
-
-**Wait for User Confirmation - DO NOT PROCEED without "yes"**
-
-- [ ] Accept user input
-- [ ] If "yes" or "y": Proceed to Step 8
-- [ ] If "no" or "n": HALT and display cancellation message
-- [ ] If invalid: Re-prompt for yes/no
-
-**If User Confirms:**
-```output
-✓ Confirmed. Starting batch update with target status: {{selected_status_name}}
-```
-
-**If User Cancels:**
-```output
-❌ Batch update cancelled by user.
-
-No changes were made to stories or Jira issues.
-```
-HALT execution.
-
-### Phase 3: Batch Validation & Update
-
-#### Step 8: Validate and Update Each Story
-
-**CRITICAL:** This is an iterative process. For EACH story in the valid stories list, perform validation and update.
-
-```output
-═══════════════════════════════════════════════════════════════
-  BATCH STATUS UPDATE STARTING
-  Epic: {{epic_number}}
-  Target Status: {{selected_status}}
-  Stories: {{valid_count}}
-═══════════════════════════════════════════════════════════════
-```
-
-**FOR EACH STORY - Execute Validation & Update:**
-
-```action
-LOOP: For each story in valid_stories list, execute validation and update:
-
-─────────────────────────────────────────────────────────────
-Processing Story {{index}}/{{total}}: {{filename}}
-─────────────────────────────────────────────────────────────
-
-A. VALIDATE TASK COMPLETION (Read from ## Tasks / Subtasks section only)
-   - Read ONLY the ## Tasks / Subtasks section from story file
-   - Count total tasks and subtasks (both top-level and nested)
-   - Count completed tasks (marked [x])
-   - Calculate completion rate
-   - Requirement: 100% completion
-
-   If completion < 100%:
-     ❌ SKIP: Incomplete tasks
-     Record reason: "{{completed}}/{{total}} tasks completed ({{percentage}}%)"
-     Add to failed_stories list
-     CONTINUE to next story
-
-B. VALIDATE QA GATES (Conditional - Only if target status is "Done", Read from ## QA Gates section only)
-   - Read ONLY the ## QA Gates section from story file (if exists)
-   - If no QA gates section: PASS validation
-   - If QA gates exist and target status is "Done":
-     - Parse all gate statuses from the section
-     - Verify all gates show "PASS"
-     - Reject if any gate is: FAIL, CONCERN, or WAIVED
-
-   If QA gates validation fails:
-     ❌ SKIP: QA gates not passed
-     Record reason: "QA gates: {{gate_name}} = {{status}}"
-     Add to failed_stories list
-     CONTINUE to next story
-
-C. GET AVAILABLE TRANSITIONS FOR THIS STORY
-   - Call MCP tool: mcp__atlassian__getTransitionsForJiraIssue
-   - Parameters:
-     - cloudId: {{cloud_id}}
-     - issueIdOrKey: {{story_jira_key}}
-   - Extract available transition IDs and names
-   - Find transition ID matching {{selected_status}}
-
-   If transition not available:
-     ❌ SKIP: Transition not available
-     Record reason: "Status '{{selected_status}}' not available from current state"
-     Add to failed_stories list
-     CONTINUE to next story
-
-D. EXECUTE JIRA TRANSITION
-   - Call MCP tool: mcp__atlassian__transitionJiraIssue
-   - Parameters:
-     - cloudId: {{cloud_id}}
-     - issueIdOrKey: {{story_jira_key}}
-     - transition: {"id": "{{transition_id}}"}
-
-   If transition fails:
-     ❌ SKIP: Jira API error
-     Record reason: "Jira error: {{error_message}}"
-     Add to failed_stories list
-     CONTINUE to next story
-
-E. UPDATE LOCAL STORY FILE (Update metadata section only)
-   - Read story file content (or just metadata section for efficiency)
-   - Find status field line in metadata: **Status:** {{old_status}}
-   - Replace with: **Status:** {{selected_status}}
-   - Write updated content back to file
-   - DO NOT modify any other sections (Tasks, QA Gates, etc.)
-
-   If file update fails:
-     ⚠️ WARNING: Jira updated but local file failed
-     Record reason: "Local file update failed: {{error}}"
-     Add to partially_succeeded list
-     Mark Jira as updated
-
-F. RECORD SUCCESS
-   - Add to successful_stories list
-   - Record: filename, jira_key, old_status, new_status
-   - Display: ✓ {{filename}} → {{jira_key}} ({{old_status}} → {{new_status}})
-
-─────────────────────────────────────────────────────────────
-✓ Story {{index}}/{{total}} PROCESSED
-─────────────────────────────────────────────────────────────
-
-CONTINUE TO NEXT STORY IN LOOP...
-```
-
-**Progress Tracking:**
-```output
-Batch Progress: [{{index}}/{{total}}] {{percentage}}%
-
-Successful:
-{{for each successful story}}
-✓ {{filename}} → {{jira_key}} ({{old_status}} → {{new_status}})
-{{end for}}
-
-Failed ({{failed_count}}):
-{{for each failed story}}
-❌ {{filename}}: {{reason}}
-{{end for}}
-
-{{if current story}}
-⟳ Processing: {{current_filename}}...
-{{end if}}
-```
-
-### Phase 4: Completion & Reporting
-
-#### Step 9: Generate Batch Update Report
-
-```output
-═══════════════════════════════════════════════════════════════
-  BATCH STATUS UPDATE COMPLETE
-═══════════════════════════════════════════════════════════════
-
-Epic: {{epic_number}}
-Target Status: {{selected_status}}
-Execution Time: {{duration}}
-
-## Results Summary
-
-| # | Story File | Jira Key | Old Status | New Status | Result |
-|---|------------|----------|------------|------------|--------|
-{{for each story}}
-| {{index}} | {{filename}} | {{jira_key}} | {{old_status}} | {{new_status}} | {{status_icon}} |
-{{end for}}
-
-## Statistics
-
-- Total Stories in Epic: {{total_count}}
-- Valid for Update: {{valid_count}}
-- Successfully Updated: {{success_count}}
-- Failed: {{failed_count}}
-- Skipped (no Jira key): {{no_key_count}}
-- Partially Succeeded (Jira updated, local file failed): {{partial_count}}
-
-## Successfully Updated Stories
-
-{{for each successful story}}
-✅ {{filename}}
-   Jira: {{jira_key}}
-   Status: {{old_status}} → {{new_status}}
-   Tasks: {{completed}}/{{total}} completed
-   {{if qa_gates}}QA Gates: All PASS{{/if}}
-{{end for}}
-
-## Failed Stories
-
-{{for each failed story}}
-❌ {{filename}}
-   Jira: {{jira_key}}
-   Current Status: {{current_status}}
-   Reason: {{failure_reason}}
-
-   Resolution:
-   {{if reason is "incomplete tasks"}}
-   - Complete remaining tasks before updating status
-   - Currently: {{completed}}/{{total}} tasks completed
-   {{else if reason is "qa gates"}}
-   - Resolve QA gate issues
-   - Current gates: {{gate_statuses}}
-   {{else if reason is "transition not available"}}
-   - Check Jira workflow for valid transitions from {{current_status}}
-   - Selected status '{{selected_status}}' may not be accessible
-   {{else}}
-   - Review error message: {{error_message}}
-   {{/if}}
-{{end for}}
-
-{{if no_key_count > 0}}
-## Skipped Stories (No Jira Key)
-
-{{for each no_key_story}}
-⊘ {{filename}} - Not synced to Jira yet
-{{end for}}
-
-Resolution:
-- Run `*sync-epic-to-jira {{epic_number}}` to sync these stories first
-{{/if}}
-
-{{if partial_count > 0}}
-## Partially Succeeded (Jira Updated, Local File Failed)
-
-{{for each partial story}}
-⚠️ {{filename}}
-   Jira: {{jira_key}} successfully updated to {{new_status}}
-   But local file update failed: {{error}}
-
-   Resolution:
-   - Manually update Status field in {{filename}} to: {{new_status}}
-{{end for}}
-{{/if}}
-
-## Jira Board Links
-
-- Project Board: {{jira_url}}/jira/software/projects/{{project_key}}/boards
-- Backlog: {{jira_url}}/jira/software/projects/{{project_key}}/backlog
-
-## Next Steps
-
-{{if success_count == valid_count}}
-✅ All stories successfully updated!
-1. Review updated stories in Jira
-2. Stories are ready for next workflow stage
-{{else}}
-⚠️ Some stories failed to update
-1. Review failure reasons above
-2. Fix issues with failed stories
-3. Re-run this command or use `*update-story-jira-status` for individual stories
-{{/if}}
-
-═══════════════════════════════════════════════════════════════
-```
-
-**Completion Checklist:**
-- [ ] All stories processed
-- [ ] Success/failure lists populated
-- [ ] Local story files updated for successful transitions
-- [ ] User notified with detailed report
-- [ ] Failure reasons clearly documented
-
-## Error Handling
-
-### Common Errors and Solutions
-
-**Error: No Stories Found**
-```output
-❌ No stories found for epic {{epic_number}}
-
-Check:
-- Epic number is correct
-- Story files exist in docs/stories/
-- Files follow naming pattern: {{epic}}.{{story}}.story.md
-
-Resolution:
-1. Verify epic number
-2. List files: ls docs/stories/{{epic_number}}.*.story.md
-3. Create stories if needed
-```
-
-**Error: All Stories Missing Jira Keys**
-```output
-❌ All stories in epic {{epic_number}} lack Jira keys
-
-Stories found: {{count}}
-Stories with Jira keys: 0
-
-Resolution:
-1. Run `*sync-epic-to-jira {{epic_number}}` to sync stories to Jira first
-2. Retry status update after sync completes
-```
-
-**Error: Invalid Target Status**
-```output
-❌ Target status "{{selected_status}}" is not available
-
-This may occur if:
-- Status name is misspelled
-- Workflow doesn't include this status
-- Status was removed after caching
-
-Resolution:
-1. Delete "Available Story Statuses" section from docs/jira-conf.md
-2. Re-run command to re-fetch current statuses from Jira
-```
-
-**Error: Jira Connection Failed**
-```output
-❌ Unable to connect to Jira
-
-Possible causes:
-- Invalid credentials in jira-preferences.md
-- Network connectivity issues
-- Jira API rate limit exceeded
-
-Resolution:
-1. Verify Jira configuration in docs/jira-conf.md
-2. Re-authenticate using MCP panel
-3. Retry operation
-```
-
-**Error: Permission Denied**
-```output
-❌ Insufficient permissions for story {{jira_key}}
-
-Required permissions:
-- Transition Issues
-- Edit Issues
-
-Resolution:
-1. Contact your Jira administrator for permissions
-2. Verify you have access to project {{project_key}}
-```
-
-## Configuration Reference
-
-### Required Configuration Files
-
-**`docs/jira-conf.md`:**
-```markdown
-# Jira Project Configuration
-
-**Project Key:** PM
-**Project Name:** Prueba MCP
-**Cloud ID:** 3b04e1a3-a260-4679-bdc8-0440507fbe26
-**Jira URL:** https://siesa-test-sandbox.atlassian.net
-
-## Available Story Statuses
-
-- To Do
-- In Progress
-- Done
-```
-
-**`.bmad-core/data/jira-preferences.md`:**
-Must contain Jira connection details and authentication credentials.
-
-### How Statuses are Managed (Smart Caching)
-
-This task uses **intelligent status caching** (same as update-story-jira-status):
-
-**Flow:**
-1. First checks if statuses are cached in `docs/jira-conf.md`
-2. If cached: Uses cached statuses (fast, no API calls)
-3. If NOT cached: Queries Jira via MCP to fetch current statuses from first valid story
-4. Caches fetched statuses in `jira-conf.md` for future use
-5. Presents statuses to user for ONE TIME selection (applies to all stories)
-
-**Benefits:**
-- ✅ **One-time user prompt**: Select status once for entire epic
-- ✅ **Token-efficient**: Cached statuses avoid repeated MCP calls
-- ✅ **Always accurate**: Sources from actual Jira workflow
-- ✅ **Transparent**: Cached in readable markdown format
-
-**Refresh Cached Statuses:**
-- Delete "Available Story Statuses" section from `jira-conf.md` and re-run to re-fetch
-- Or manually edit the status list in `jira-conf.md`
-
-## Notes
-
-- This task is batch operation - updates multiple stories efficiently
-- **Efficient Reading**: Only reads specific sections (metadata, Tasks/Subtasks, QA Gates) - NOT entire documents
-- Validates EACH story individually before updating (no blind batch updates)
-- QA gate validation only enforced when transitioning to "Done"
-- Task completion must be 100% before any transition (counts both tasks and subtasks)
-- **Subtasks in Descriptions**: Story subtasks are in Jira Subtask descriptions as checklists (NOT separate issues)
-- Local story files are updated to match Jira status for successful transitions
-- Failed stories are clearly reported with specific reasons
-- User can retry failed stories individually or fix issues and re-run batch
-- Each story's transition availability is checked (workflow-aware)
-- Partial failures are handled gracefully - successful updates are preserved
-
-## Related Commands
-
-- `*update-story-jira-status {story}` - Update individual story status
-- `*sync-epic-to-jira {epic-number}` - Sync epic stories to Jira first
-- `*validate-story-draft` - Validate story before approval
-- `*jira-setup` - Configure Jira integration