[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M751N10RGDPEGY6CEKNJCG2C":3,"skill-same:01M751N10RGDPEGY6CEKNJCG2C":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":49},"01M751N10RGDPEGY6CEKNJCG2C","x-create-jira-stories",null,"Create Jira Stories from existing local story markdown files. Read all story files in an epic directory, map fields to Jira, create issues with parent epic link, create dependency links between stories, and sync Jira keys back to local files.","review-bench\u002Federcnj_ia-dev-environment","review-bench","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F286778065?v=4","01M7517F9NTEPDZDAXJBR30FWT","ReviewBench","01M7517FAC9F4P7TGWCNJ8VYVW",0,"MIT","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fcore\u002Fjira\u002Fx-create-jira-stories\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-create-jira-stories\ndescription: \"Create Jira Stories from existing local story markdown files. Read all story files in an epic directory, map fields to Jira, create issues with parent epic link, create dependency links between stories, and sync Jira keys back to local files.\"\nuser-invocable: true\nallowed-tools: Read, Write, Edit, Bash, Grep, Glob, AskUserQuestion\nargument-hint: \"[EPIC_DIR_PATH or EPIC_ID]\"\nrequires-capabilities: []\n---\n\n## Global Output Policy\n\n- **Language**: English ONLY.\n- **Tone**: Technical, Direct, and Concise.\n- **Efficiency**: Remove all conversational fillers and greetings to save tokens.\n\n# Skill: Create Jira Stories\n\n## Purpose\n\nCreate Jira Story issues from existing local `story-XXXX-YYYY.md` files. Parse all story files in an epic directory, map fields to Jira attributes, create issues with parent epic link, create dependency links between stories, update the implementation map with Jira keys, and sync keys back to local files.\n\n## Triggers\n\n- `\u002Fx-create-jira-stories \u003Cepic_dir_path>` — create Jira stories from the specified directory\n- `\u002Fx-create-jira-stories \u003Cepic_id>` — create stories using epic ID (e.g., `0012`)\n- User says \"create stories in Jira\", \"sync stories to Jira\", or \"push stories to Jira\"\n- After running `\u002Fx-story-create` or `\u002Fx-epic-decompose` without Jira integration\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `EPIC_DIR_PATH` | Path or ID | No | — | Epic directory path or epic ID (prompted if omitted) |\n\n## Prerequisites\n\nRead the field mapping reference before creating issues:\n- `.claude\u002Fskills\u002Fx-create-jira-epic\u002Freferences\u002Fjira-field-mapping.md`\n\n## Workflow\n\n### Step 1 — Input and Discovery\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-stories Phase-1-Read-Markdowns`\n\n1. Accept the epic directory path or epic ID as argument. If not provided, ask:\n   ```\n   question: \"Informe o caminho do diretorio do epico ou o ID (ex: ai\u002Fepics\u002Fepic-XXXX ou XXXX)\"\n   header: \"Epic Directory\"\n   ```\n2. If only an ID was given (e.g., `0012`), construct the path: `ai\u002Fepics\u002Fepic-{ID}\u002F`\n3. Verify the directory exists. If not:\n   ```\n   ERROR: Directory {path} not found. Ensure the epic was created first.\n   ```\n4. Glob for `story-XXXX-*.md` files in the directory\n5. If no story files found:\n   ```\n   ERROR: No story files found in {path}. Run \u002Fx-story-create first.\n   ```\n\n### Step 2 — Parse All Stories\n\nFor each story file, extract:\n- **Title**: From `# Historia: \u003Ctitulo>` (line 1)\n- **Local ID**: From `**ID:**` field (e.g., `story-0012-0001`)\n- **Existing Jira Key**: From `**Chave Jira:**` field\n- **Description**: Section 3 text (user story paragraph + technical context)\n- **Value Delivery**: Section 3.5 (Entrega de Valor) — Valor Principal, Metrica de Sucesso, Impacto\n- **Dependencies**: Section 1 (Blocked By column)\n\n### Step 3 — Filter and Confirm\n\n1. Classify stories:\n   - **Already in Jira**: Stories with a real Jira key (not `\u003CCHAVE-JIRA>` or `—`)\n   - **To create**: Stories without a Jira key\n\n2. If all stories already have Jira keys:\n   ```\n   All {N} stories already have Jira keys. Nothing to create.\n   ```\n   Exit.\n\n3. Report and confirm:\n   ```\n   question: \"Confirma a criacao das historias no Jira?\"\n   header: \"Criar Stories no Jira\"\n   description: |\n     Historias a criar: {count_to_create}\n     Historias ja no Jira (pular): {count_existing}\n\n     Stories a criar:\n     - {story-ID}: {title}\n     - {story-ID}: {title}\n     ...\n   options:\n     - label: \"Sim, criar todas\"\n       description: \"Criar {count_to_create} stories no Jira\"\n     - label: \"Nao, cancelar\"\n       description: \"Nao criar nada no Jira\"\n   ```\n   If \"Nao\": exit.\n\n### Step 4 — Epic Link Discovery\n\n1. Read `epic-XXXX.md` from the same directory\n2. Extract the epic's `**Chave Jira:**` value\n3. If the epic has no Jira key (or has `\u003CCHAVE-JIRA>` \u002F `—`):\n   ```\n   question: \"O epico nao tem chave Jira. O que deseja fazer?\"\n   header: \"Epic Link\"\n   options:\n     - label: \"Criar stories sem vinculo ao epico\"\n       description: \"Stories serao criadas sem parent link\"\n     - label: \"Informar chave do epico manualmente\"\n       description: \"Informe a chave do epico no Jira (ex: PROJ-123)\"\n     - label: \"Cancelar — criar epico primeiro\"\n       description: \"Execute \u002Fx-create-jira-epic antes\"\n   ```\n   - If \"Criar sem vinculo\": proceed without `parent` field\n   - If \"Informar chave\": ask for the key and use it as `parent`\n   - If \"Cancelar\": exit\n\n### Step 5 — Project Selection\n\n1. Call `mcp__atlassian__getAccessibleAtlassianResources` to discover available Atlassian sites\n2. Use the first available site's `id` as `cloudId`. If no sites returned:\n   ```\n   ERROR: No accessible Atlassian sites found. Check your Atlassian credentials.\n   ```\n   Abort.\n\n3. Call `mcp__atlassian__getVisibleJiraProjects` with the discovered `cloudId`\n4. Present the project list to the user:\n   ```\n   question: \"Selecione o projeto Jira para criar as stories:\"\n   header: \"Projeto Jira\"\n   options:\n     - label: \"{PROJECT_KEY} — {PROJECT_NAME}\"\n       description: \"Project key: {PROJECT_KEY}\"\n     (one option per project)\n   ```\n5. Capture the selected `projectKey`\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-stories Phase-1-Read-Markdowns ok`\n\n### Step 6 — Create Stories in Jira\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-stories Phase-2-MCP-Loop`\n\nProcess stories in dependency order (stories with no dependencies first, then those that depend\non already-created stories). This ensures parent epic links and dependency links can be created.\n\nInitialize a mapping: `storyIdToJiraKey = {}`\n\nFor each story (in dependency order):\n\n#### 6.1 — Build Description\n\nConcatenate for Jira:\n```markdown\n{Section 3 — User story paragraph and technical context}\n\n---\n\n## Entrega de Valor\n\n- **Valor Principal:** {value from Section 3.5}\n- **Metrica de Sucesso:** {metric from Section 3.5}\n- **Impacto no Negocio:** {impact from Section 3.5}\n```\n\n#### 6.2 — Create Issue\n\nWrap each per-story MCP call with mcp-start \u002F mcp-end markers (story-0040-0008\n§3.2) so every `tool.call` event carries `tool=mcp__atlassian__createJiraIssue`\nand a measured `durationMs` — yielding N tool.call events for N stories and\nenabling per-skill aggregation of \"tempo gasto no Jira\" vs \"tempo local\":\n\n\u003C!-- TELEMETRY: tool.call mcp-start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-start x-create-jira-stories createJiraIssue`\n\nCall `mcp__atlassian__createJiraIssue`:\n- `cloudId`: discovered cloudId\n- `projectKey`: selected project key\n- `issueTypeName`: \"Story\"\n- `summary`: story title\n- `description`: constructed description (above)\n- `contentFormat`: \"markdown\"\n- `parent` (optional): epic Jira key (if available from Step 4)\n- `additional_fields`:\n  ```json\n  {\n    \"labels\": [\n      { \"name\": \"generated-by-ia-dev-env\" },\n      { \"name\": \"story-XXXX-YYYY\" }\n    ]\n  }\n  ```\n\n\u003C!-- TELEMETRY: tool.call mcp-end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-end x-create-jira-stories createJiraIssue ok`\n\n(On MCP failure in 6.5, pass status `failed` instead of `ok` to the mcp-end\nmarker so the telemetry record reflects the real outcome.)\n\n#### 6.3 — Capture and Store\n\nCapture the returned Jira key. Store mapping: `storyIdToJiraKey[storyId] = jiraKey`.\n\n#### 6.4 — Update Local File\n\nReplace `**Chave Jira:** \u003CCHAVE-JIRA>` or `**Chave Jira:** —` with `**Chave Jira:** {jiraKey}`.\n\n#### 6.5 — On Failure\n\nLog warning, set `\u003CCHAVE-JIRA>` to `—`, continue with next story.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-stories Phase-2-MCP-Loop ok`\n\n### Step 7 — Dependency Linking (Second Pass)\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-stories Phase-3-Dependency-Links`\n\nAfter ALL stories are created and have Jira keys, perform a second pass to create\ndependency links:\n\nFor each story's \"Blocked By\" list:\n1. Look up the blocker's Jira key in `storyIdToJiraKey` (or from the story file if pre-existing)\n2. If both the current story and the blocker have Jira keys:\n   - Wrap the MCP call with mcp-start \u002F mcp-end markers so every dependency\n     link emits its own `tool.call` event with\n     `tool=mcp__atlassian__createIssueLink`:\n\n     \u003C!-- TELEMETRY: tool.call mcp-start -->\n     Bash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-start x-create-jira-stories createIssueLink`\n\n   - Call `mcp__atlassian__createIssueLink`:\n     - `cloudId`: discovered cloudId\n     - `type`: \"Blocks\"\n     - `inwardIssue`: blocker's Jira key (the issue that blocks)\n     - `outwardIssue`: current story's Jira key (the issue that is blocked)\n\n     \u003C!-- TELEMETRY: tool.call mcp-end -->\n     Bash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-end x-create-jira-stories createIssueLink ok`\n\n3. If linking fails: log warning, continue (non-blocking, best-effort). Pass\n   status `failed` to the mcp-end marker on such failures.\n\n### Step 8 — Update Implementation Map\n\nIf `IMPLEMENTATION-MAP.md` exists in the epic directory:\n1. Read the file\n2. For each created story, find its row in the Section 1 dependency matrix\n3. Update the `Chave Jira` column with the actual Jira key\n4. Write the updated file\n\n### Step 9 — Report\n\nOutput summary:\n```\n## Resultado da Criacao no Jira\n\n| Story | Titulo | Chave Jira | Status |\n|-------|--------|------------|--------|\n| story-XXXX-0001 | {title} | PROJ-101 | Criada |\n| story-XXXX-0002 | {title} | PROJ-102 | Criada |\n| story-XXXX-0003 | {title} | — | Falha: {error} |\n\n**Resumo:**\n- Stories criadas: {success_count}\u002F{total_count}\n- Links de dependencia criados: {link_count}\n- Falhas: {failure_count}\n- Implementation Map atualizado: {yes\u002Fno}\n```\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-stories Phase-3-Dependency-Links ok`\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| MCP tool not available | Abort with clear message about MCP configuration |\n| No Atlassian sites found | Abort with credential check message |\n| Epic directory not found | Abort with message: \"Directory {path} not found\" |\n| No story files found | Abort with message: \"No story files found — run \u002Fx-story-create first\" |\n| Individual story creation fails | Log warning, continue with remaining stories |\n| Dependency link creation fails | Log warning, continue (best-effort) |\n| File write fails | Log warning, mention Jira key was created but file not updated |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-story-create | reads | Reads story files generated by this skill |\n| x-epic-decompose | called-by | Orchestrator may invoke this after story generation |\n| x-create-jira-epic | calls | Creates the parent epic before stories |\n| x-epic-map | reads | Implementation Map updated with Jira keys |\n\n## ID Synchronization Strategy\n\nBidirectional lookup is enabled by:\n- **Local to Jira**: The local ID (`story-XXXX-YYYY`) is stored as a Jira label\n- **Jira to Local**: The Jira key is stored in the `**Chave Jira:**` field\n- **JQL Lookup**: `labels = \"story-XXXX-YYYY\" AND labels = \"generated-by-ia-dev-env\"`\n","## Global Output Policy\n\n- **Language**: English ONLY.\n- **Tone**: Technical, Direct, and Concise.\n- **Efficiency**: Remove all conversational fillers and greetings to save tokens.\n\n# Skill: Create Jira Stories\n\n## Purpose\n\nCreate Jira Story issues from existing local `story-XXXX-YYYY.md` files. Parse all story files in an epic directory, map fields to Jira attributes, create issues with parent epic link, create dependency links between stories, update the implementation map with Jira keys, and sync keys back to local files.\n\n## Triggers\n\n- `\u002Fx-create-jira-stories \u003Cepic_dir_path>` — create Jira stories from the specified directory\n- `\u002Fx-create-jira-stories \u003Cepic_id>` — create stories using epic ID (e.g., `0012`)\n- User says \"create stories in Jira\", \"sync stories to Jira\", or \"push stories to Jira\"\n- After running `\u002Fx-story-create` or `\u002Fx-epic-decompose` without Jira integration\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|-----------|------|----------|---------|-------------|\n| `EPIC_DIR_PATH` | Path or ID | No | — | Epic directory path or epic ID (prompted if omitted) |\n\n## Prerequisites\n\nRead the field mapping reference before creating issues:\n- `.claude\u002Fskills\u002Fx-create-jira-epic\u002Freferences\u002Fjira-field-mapping.md`\n\n## Workflow\n\n### Step 1 — Input and Discovery\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-stories Phase-1-Read-Markdowns`\n\n1. Accept the epic directory path or epic ID as argument. If not provided, ask:\n   ```\n   question: \"Informe o caminho do diretorio do epico ou o ID (ex: ai\u002Fepics\u002Fepic-XXXX ou XXXX)\"\n   header: \"Epic Directory\"\n   ```\n2. If only an ID was given (e.g., `0012`), construct the path: `ai\u002Fepics\u002Fepic-{ID}\u002F`\n3. Verify the directory exists. If not:\n   ```\n   ERROR: Directory {path} not found. Ensure the epic was created first.\n   ```\n4. Glob for `story-XXXX-*.md` files in the directory\n5. If no story files found:\n   ```\n   ERROR: No story files found in {path}. Run \u002Fx-story-create first.\n   ```\n\n### Step 2 — Parse All Stories\n\nFor each story file, extract:\n- **Title**: From `# Historia: \u003Ctitulo>` (line 1)\n- **Local ID**: From `**ID:**` field (e.g., `story-0012-0001`)\n- **Existing Jira Key**: From `**Chave Jira:**` field\n- **Description**: Section 3 text (user story paragraph + technical context)\n- **Value Delivery**: Section 3.5 (Entrega de Valor) — Valor Principal, Metrica de Sucesso, Impacto\n- **Dependencies**: Section 1 (Blocked By column)\n\n### Step 3 — Filter and Confirm\n\n1. Classify stories:\n   - **Already in Jira**: Stories with a real Jira key (not `\u003CCHAVE-JIRA>` or `—`)\n   - **To create**: Stories without a Jira key\n\n2. If all stories already have Jira keys:\n   ```\n   All {N} stories already have Jira keys. Nothing to create.\n   ```\n   Exit.\n\n3. Report and confirm:\n   ```\n   question: \"Confirma a criacao das historias no Jira?\"\n   header: \"Criar Stories no Jira\"\n   description: |\n     Historias a criar: {count_to_create}\n     Historias ja no Jira (pular): {count_existing}\n\n     Stories a criar:\n     - {story-ID}: {title}\n     - {story-ID}: {title}\n     ...\n   options:\n     - label: \"Sim, criar todas\"\n       description: \"Criar {count_to_create} stories no Jira\"\n     - label: \"Nao, cancelar\"\n       description: \"Nao criar nada no Jira\"\n   ```\n   If \"Nao\": exit.\n\n### Step 4 — Epic Link Discovery\n\n1. Read `epic-XXXX.md` from the same directory\n2. Extract the epic's `**Chave Jira:**` value\n3. If the epic has no Jira key (or has `\u003CCHAVE-JIRA>` \u002F `—`):\n   ```\n   question: \"O epico nao tem chave Jira. O que deseja fazer?\"\n   header: \"Epic Link\"\n   options:\n     - label: \"Criar stories sem vinculo ao epico\"\n       description: \"Stories serao criadas sem parent link\"\n     - label: \"Informar chave do epico manualmente\"\n       description: \"Informe a chave do epico no Jira (ex: PROJ-123)\"\n     - label: \"Cancelar — criar epico primeiro\"\n       description: \"Execute \u002Fx-create-jira-epic antes\"\n   ```\n   - If \"Criar sem vinculo\": proceed without `parent` field\n   - If \"Informar chave\": ask for the key and use it as `parent`\n   - If \"Cancelar\": exit\n\n### Step 5 — Project Selection\n\n1. Call `mcp__atlassian__getAccessibleAtlassianResources` to discover available Atlassian sites\n2. Use the first available site's `id` as `cloudId`. If no sites returned:\n   ```\n   ERROR: No accessible Atlassian sites found. Check your Atlassian credentials.\n   ```\n   Abort.\n\n3. Call `mcp__atlassian__getVisibleJiraProjects` with the discovered `cloudId`\n4. Present the project list to the user:\n   ```\n   question: \"Selecione o projeto Jira para criar as stories:\"\n   header: \"Projeto Jira\"\n   options:\n     - label: \"{PROJECT_KEY} — {PROJECT_NAME}\"\n       description: \"Project key: {PROJECT_KEY}\"\n     (one option per project)\n   ```\n5. Capture the selected `projectKey`\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-stories Phase-1-Read-Markdowns ok`\n\n### Step 6 — Create Stories in Jira\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-stories Phase-2-MCP-Loop`\n\nProcess stories in dependency order (stories with no dependencies first, then those that depend\non already-created stories). This ensures parent epic links and dependency links can be created.\n\nInitialize a mapping: `storyIdToJiraKey = {}`\n\nFor each story (in dependency order):\n\n#### 6.1 — Build Description\n\nConcatenate for Jira:\n```markdown\n{Section 3 — User story paragraph and technical context}\n\n---\n\n## Entrega de Valor\n\n- **Valor Principal:** {value from Section 3.5}\n- **Metrica de Sucesso:** {metric from Section 3.5}\n- **Impacto no Negocio:** {impact from Section 3.5}\n```\n\n#### 6.2 — Create Issue\n\nWrap each per-story MCP call with mcp-start \u002F mcp-end markers (story-0040-0008\n§3.2) so every `tool.call` event carries `tool=mcp__atlassian__createJiraIssue`\nand a measured `durationMs` — yielding N tool.call events for N stories and\nenabling per-skill aggregation of \"tempo gasto no Jira\" vs \"tempo local\":\n\n\u003C!-- TELEMETRY: tool.call mcp-start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-start x-create-jira-stories createJiraIssue`\n\nCall `mcp__atlassian__createJiraIssue`:\n- `cloudId`: discovered cloudId\n- `projectKey`: selected project key\n- `issueTypeName`: \"Story\"\n- `summary`: story title\n- `description`: constructed description (above)\n- `contentFormat`: \"markdown\"\n- `parent` (optional): epic Jira key (if available from Step 4)\n- `additional_fields`:\n  ```json\n  {\n    \"labels\": [\n      { \"name\": \"generated-by-ia-dev-env\" },\n      { \"name\": \"story-XXXX-YYYY\" }\n    ]\n  }\n  ```\n\n\u003C!-- TELEMETRY: tool.call mcp-end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-end x-create-jira-stories createJiraIssue ok`\n\n(On MCP failure in 6.5, pass status `failed` instead of `ok` to the mcp-end\nmarker so the telemetry record reflects the real outcome.)\n\n#### 6.3 — Capture and Store\n\nCapture the returned Jira key. Store mapping: `storyIdToJiraKey[storyId] = jiraKey`.\n\n#### 6.4 — Update Local File\n\nReplace `**Chave Jira:** \u003CCHAVE-JIRA>` or `**Chave Jira:** —` with `**Chave Jira:** {jiraKey}`.\n\n#### 6.5 — On Failure\n\nLog warning, set `\u003CCHAVE-JIRA>` to `—`, continue with next story.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-stories Phase-2-MCP-Loop ok`\n\n### Step 7 — Dependency Linking (Second Pass)\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-create-jira-stories Phase-3-Dependency-Links`\n\nAfter ALL stories are created and have Jira keys, perform a second pass to create\ndependency links:\n\nFor each story's \"Blocked By\" list:\n1. Look up the blocker's Jira key in `storyIdToJiraKey` (or from the story file if pre-existing)\n2. If both the current story and the blocker have Jira keys:\n   - Wrap the MCP call with mcp-start \u002F mcp-end markers so every dependency\n     link emits its own `tool.call` event with\n     `tool=mcp__atlassian__createIssueLink`:\n\n     \u003C!-- TELEMETRY: tool.call mcp-start -->\n     Bash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-start x-create-jira-stories createIssueLink`\n\n   - Call `mcp__atlassian__createIssueLink`:\n     - `cloudId`: discovered cloudId\n     - `type`: \"Blocks\"\n     - `inwardIssue`: blocker's Jira key (the issue that blocks)\n     - `outwardIssue`: current story's Jira key (the issue that is blocked)\n\n     \u003C!-- TELEMETRY: tool.call mcp-end -->\n     Bash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh mcp-end x-create-jira-stories createIssueLink ok`\n\n3. If linking fails: log warning, continue (non-blocking, best-effort). Pass\n   status `failed` to the mcp-end marker on such failures.\n\n### Step 8 — Update Implementation Map\n\nIf `IMPLEMENTATION-MAP.md` exists in the epic directory:\n1. Read the file\n2. For each created story, find its row in the Section 1 dependency matrix\n3. Update the `Chave Jira` column with the actual Jira key\n4. Write the updated file\n\n### Step 9 — Report\n\nOutput summary:\n```\n## Resultado da Criacao no Jira\n\n| Story | Titulo | Chave Jira | Status |\n|-------|--------|------------|--------|\n| story-XXXX-0001 | {title} | PROJ-101 | Criada |\n| story-XXXX-0002 | {title} | PROJ-102 | Criada |\n| story-XXXX-0003 | {title} | — | Falha: {error} |\n\n**Resumo:**\n- Stories criadas: {success_count}\u002F{total_count}\n- Links de dependencia criados: {link_count}\n- Falhas: {failure_count}\n- Implementation Map atualizado: {yes\u002Fno}\n```\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-create-jira-stories Phase-3-Dependency-Links ok`\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| MCP tool not available | Abort with clear message about MCP configuration |\n| No Atlassian sites found | Abort with credential check message |\n| Epic directory not found | Abort with message: \"Directory {path} not found\" |\n| No story files found | Abort with message: \"No story files found — run \u002Fx-story-create first\" |\n| Individual story creation fails | Log warning, continue with remaining stories |\n| Dependency link creation fails | Log warning, continue (best-effort) |\n| File write fails | Log warning, mention Jira key was created but file not updated |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-story-create | reads | Reads story files generated by this skill |\n| x-epic-decompose | called-by | Orchestrator may invoke this after story generation |\n| x-create-jira-epic | calls | Creates the parent epic before stories |\n| x-epic-map | reads | Implementation Map updated with Jira keys |\n\n## ID Synchronization Strategy\n\nBidirectional lookup is enabled by:\n- **Local to Jira**: The local ID (`story-XXXX-YYYY`) is stored as a Jira label\n- **Jira to Local**: The Jira key is stored in the `**Chave Jira:**` field\n- **JQL Lookup**: `labels = \"story-XXXX-YYYY\" AND labels = \"generated-by-ia-dev-env\"`\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25,"user-invocable":26,"requires-capabilities":27},"Read, Write, Edit, Bash, Grep, Glob, AskUserQuestion","[EPIC_DIR_PATH or EPIC_ID]",true,[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fcore\u002Fjira\u002Fx-create-jira-stories",1,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment","https:\u002F\u002Fgithub.com\u002Freview-bench","https:\u002F\u002Freview-bench.ai","An open benchmark for AI code review.","2026-10-27 06:56:37",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":26},[39,42,45],{"tool":40,"command":41},"npx","npx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-create-jira-stories",{"tool":43,"command":44},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-create-jira-stories",{"tool":46,"command":47},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-create-jira-stories","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fcore\u002Fjira\u002Fx-create-jira-stories\u002FSKILL.md",[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"README.md","REFERENCE","参考文档",2093,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Fmain\u002Fresources\u002Ftargets\u002Fclaude\u002Fskills\u002Fcore\u002Fjira\u002Fx-create-jira-stories\u002FREADME.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M757M8J48TQ1Y3X25GSJBXAS","x-parallel-eval","Detects and classifies file-collision risks between work units (tasks, stories, or epic phases) before parallel execution. Reads ## File Footprint blocks produced by x-task-plan \u002F x-story-plan, applies the parallelism-heuristics knowledge pack (hard \u002F regen \u002F soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fx-parallel-eval\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M757M57XMR9546S69466HDWT","parallelism-heuristics","Canonical catalog of file-collision heuristics for parallel task, story, and epic execution. Defines the File Footprint block format, the three Conflict Categories (hard \u002F regen \u002F soft), a hotspot list of high-contention paths, and the degrade-with-warning policy. Consumed by x-task-plan, x-story-plan, x-epic-map, x-parallel-eval, and x-dev-*-implement.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fparallelism-heuristics\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M757M11SZ8P1VCQABT08QVYA","x-watch-pr-ci","Polls a PR's CI checks and Copilot review status, blocking until checks complete or timeout. Returns one of 8 stable exit codes (SUCCESS=0, CI_PENDING_PROCEED=10, CI_FAILED=20, TIMEOUT=30, PR_ALREADY_MERGED=40, NO_CI_CONFIGURED=50, PR_CLOSED=60, PR_NOT_FOUND=70). Writes a versioned state-file for session resume.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-watch-pr-ci\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M757KW53K8KFPGADFB4PH949","x-validate-docs","Documentation freshness gate: validates 6 dimensions (readme, api-specs, grpc-proto, adr, skill-docs, system-architecture) against code changes in a PR. Stack-aware — only validates targets declared\u002Fauto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-validate-docs\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M757KQZHSA10MKC0CR571D60","x-update-system-architecture","Incrementally updates docs\u002Farchitecture\u002Fsystem.md after an epic completes. Appends new entries to the Decision Log (§11) using x-internal-write-report --append (dedup by ## ID: marker) and surgically inserts component\u002Fintegration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-update-system-architecture\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M757KKBT5Q1SVF8DMJBVF46M","x-update-architecture","Incrementally updates the service architecture document with changes from architecture plans. Adds new components, integrations, flows, and ADR references without rewriting existing content. Use after implementation to keep architecture documentation current.","https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring\u002Fplatform-claude-code\u002F.claude\u002Fskills\u002Fx-update-architecture\u002FSKILL.md",[],[]]