[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754ADTMW86HEB0YW3002QRC":3,"skill-same:01M754ADTMW86HEB0YW3002QRC":65},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":36,"updatedAt":37,"install":38,"resources":50},"01M754ADTMW86HEB0YW3002QRC","x-plan-story",null,"Multi-agent story planning: launches 7 specialized agents (Architect, QA, Security, PentestEngineer, TechLead, ProductOwner, PerformanceEngineer) in parallel to produce a consolidated task breakdown, individual task plans, planning report, and DoR validation. Schema-aware: v1 (legacy) runs the original 6-phase flow; v2 (task-first, EPIC-0038) adds Phases 4a-4c that emit task-TASK-NNN.md + plan-task-TASK-NNN.md per task and a task-implementation-map-STORY-*.md, wiring every task through x-plan-task in parallel.","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\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-plan-story\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-plan-story\ndescription: \"Multi-agent story planning: launches 7 specialized agents (Architect, QA, Security, PentestEngineer, TechLead, ProductOwner, PerformanceEngineer) in parallel to produce a consolidated task breakdown, individual task plans, planning report, and DoR validation. Schema-aware: v1 (legacy) runs the original 6-phase flow; v2 (task-first, EPIC-0038) adds Phases 4a-4c that emit task-TASK-NNN.md + plan-task-TASK-NNN.md per task and a task-implementation-map-STORY-*.md, wiring every task through x-plan-task in parallel.\"\nuser-invocable: true\nallowed-tools: Read, Write, Edit, Bash, Grep, Glob, Skill\nargument-hint: \"[STORY-ID] [--force] [--skip-dor] [--dry-run] [--no-commit]\"\ncontext-budget: medium\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## Triggers\n\n```\n\u002Fx-plan-story STORY-ID             — plan story with 7 parallel agents\n\u002Fx-plan-story STORY-ID --force     — regenerate even if artifacts are fresh\n\u002Fx-plan-story STORY-ID --skip-dor  — skip Phase 5 DoR validation\n\u002Fx-plan-story STORY-ID --dry-run   — write artifacts but skip subagent\u002Fcommit steps\n\u002Fx-plan-story STORY-ID --no-commit — skip commit step (for orchestrators batch-committing)\n```\n\n## Parameters\n\n| Parameter | Type | Default | Description |\n|-----------|------|---------|-------------|\n| `STORY-ID` | positional | (required) | `story-XXXX-YYYY` format |\n| `--force` | boolean | `false` | Regenerate all artifacts even if fresh |\n| `--skip-dor` | boolean | `false` | Skip Phase 5 DoR validation |\n| `--dry-run` | boolean | `false` | Artifacts written but Steps P1\u002FP2\u002FP4\u002FP5 become no-ops |\n| `--no-commit` | boolean | `false` | Skip commit step; used by orchestrators batching commits at parent level |\n\n**CRITICAL:** 6 phases (0-5) all mandatory (unless `--skip-dor` skips Phase 5). Never stop before Phase 5. Print `>>> Phase N\u002F5 completed. Proceeding to Phase N+1...` after each phase.\n\n## Output Contract\n\n**Schema dispatch:**\n\n| `planningSchemaVersion` | Phases run |\n|--------------------------|------------|\n| `\"1.0\"` (or absent) | Phases 0-5 (legacy flow: task breakdown + planning report + DoR) |\n| `\"2.0\"` | Phases 0-5 + 4a-4c (v2: task-TASK-NNN.md + plan-task-TASK-NNN.md per task + task-implementation-map-STORY-*.md) |\n\n**Artifacts produced:**\n\n| Artifact | Path |\n|----------|------|\n| Task breakdown | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Ftasks-story-XXXX-YYYY.md` |\n| Planning report | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Fplanning-report-story-XXXX-YYYY.md` |\n| DoR checklist | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Fdor-story-XXXX-YYYY.md` |\n| Task files (v2) | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Ftask-TASK-XXXX-YYYY-NNN.md` per task |\n| Task plans (v2) | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Fplan-task-TASK-XXXX-YYYY-NNN.md` per task |\n| Task map (v2) | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Ftask-implementation-map-STORY-XXXX-YYYY.md` |\n\n**Phase execution with telemetry:**\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-P1-Worktree-Detect`\n\n**Step P1 (Worktree Detect):** `Skill(skill: \"x-manage-worktrees\", args: \"detect-context\")` — advisory, fail-open. Skip when `--no-commit`.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-P1-Worktree-Detect ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-P2-Epic-Branch-Ensure`\n\n**Step P2 (Epic Branch Ensure):** `Skill(skill: \"x-internal-ensure-epic-branch\", args: \"--epic-id \u003CXXXX>\")` — idempotent. Abort on failure with `EPIC_BRANCH_ENSURE_FAILED`. Skip when `--no-commit` or `--dry-run`.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-P2-Epic-Branch-Ensure ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-1-Context-Gathering`\n\n**Phase 1 (Context Gathering):** Read story, epic, implementation map, and existing plan artifacts inline. Also read `.claude\u002Fskills\u002Fplanning-standards-kp\u002FSKILL.md` (RA9 contract: 9 sections, Packages format, Decision Rationale micro-template). See staleness check and context-combination matrix in references.\n\n> **RA9 guidance (EPIC-0056 \u002F planning-standards-kp):** When producing the consolidated plan, the Architect subagent MUST fill:\n> - **Section 2 (Packages Hexagonal):** Feature-level packages in each hexagonal layer from the story analysis.\n> - **Section 8 (Decision Rationale):** At least 1 feature-level decision using the 4-line micro-template.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-1-Context-Gathering ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-2-Parallel-Planning`\n\n**Phase 2 (Parallel Planning):** Dispatch 7 subagents in a **single message** (Rule 13 Pattern 2 — SUBAGENT-GENERAL) for true parallelism.\n\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story Architect`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story QA`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story Security`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story PentestEngineer`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story TechLead`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story PO`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story PerformanceEngineer`\n\nDispatch all 7 in ONE assistant message:\n\n    Agent(subagent_type: \"general-purpose\", model: \"opus\", description: \"Architect — story {STORY_ID}\", prompt: \"You are a Senior Architect. Read context files. Analyze story {STORY_ID}. Produce TASK_PROPOSAL entries (architecture, layers, dependencies). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"QA — story {STORY_ID}\", prompt: \"You are a QA Specialist. Read context files. Produce TASK_PROPOSAL entries (tests, coverage, acceptance criteria). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"Security — story {STORY_ID}\", prompt: \"You are a Security Specialist. Read knowledge\u002Fsecurity\u002Fapplication-security.md, knowledge\u002Fsecurity\u002Fsecurity-principles.md, and context files. Produce TASK_PROPOSAL entries (security, OWASP, threat model). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"PentestEngineer — story {STORY_ID}\", prompt: \"You are a Penetration Test Engineer. Read capabilities\u002Fquality\u002Fpentest\u002Fpentest-always-on.yaml and context files. Produce TASK_PROPOSAL entries (pentest scenarios, CVSS-rated vulnerabilities, exploitation paths). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"TechLead — story {STORY_ID}\", prompt: \"You are a Tech Lead. Read context files. Produce TASK_PROPOSAL entries (code quality, SOLID, complexity). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"PO — story {STORY_ID}\", prompt: \"You are a Product Owner. Read knowledge\u002Fcompliance.md and context files. Produce TASK_PROPOSAL entries (business value, acceptance, DoD, compliance). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"PerformanceEngineer — story {STORY_ID}\", prompt: \"You are a Performance Engineer. Read context files. Produce TASK_PROPOSAL entries (latency SLAs, throughput targets, load testing scenarios). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story Architect ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story QA ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story Security ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story PentestEngineer ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story TechLead ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story PO ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story PerformanceEngineer ok`\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-2-Parallel-Planning ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-3-Consolidation`\n\n**Phase 3 (Consolidation):** Merge all TASK_PROPOSAL entries using deterministic rules (majority-vote, duplicate elimination, dependency ordering). See consolidation algorithm in references.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-3-Consolidation ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-4-Artifact-Generation`\n\n**Phase 4 (Artifact Generation):** Write `tasks-story-*.md` and `planning-report-*.md`. v2 only: Phases 4a-4c emit per-task artifacts and task map (see references).\n\n**Phase 4b (v2 only — batch task-plan dispatch):** For each TASK-XXXX-YYYY-NNN, invoke `x-plan-task` in parallel (batch ≤ 4) with `--no-commit` so the caller aggregates into a single Step P4 commit:\n\n    Skill(skill: \"x-plan-task\",\n          args: \"--task-file ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Ftask-TASK-XXXX-YYYY-NNN.md --no-commit\")\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-4-Artifact-Generation ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-5-DoR-Validation`\n\n**Phase 5 (DoR Validation):** Run 12 checks; v2 adds per-task READY checks. Skipped with `--skip-dor`.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-5-DoR-Validation ok`\n\n### Step P4 — Batch Planning Commit (EPIC-0049 \u002F RULE-007)\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-P4-Batch-Commit`\n\nIf `--dry-run` is set, log `\"dry-run, skipping commit\"` and skip this step. If `--no-commit` is set, skip as well — the parent orchestrator (e.g., `x-orchestrate-epic`) aggregates commits at the wave level.\n\nOtherwise, issue ONE consolidated commit covering every planning artifact produced by this story (task breakdown, planning report, DoR checklist, plan-story, all task files, all plan-task files, task map, and the updated `execution-state.json`):\n\n    Skill(skill: \"x-commit-planning\",\n          args: \"--scope docs --epic-id \u003CXXXX> --paths ai\u002Fepics\u002Fepic-\u003CXXXX>\u002Fplans\u002F ai\u002Fepics\u002Fepic-\u003CXXXX>\u002Fexecution-state.json --subject \\\"docs(story-\u003CXXXX>-\u003CYYYY>): add planning artifacts\\\"\")\n\nIdempotency: re-executing with identical inputs returns `commitSha=null` (silent no-op). On `COMMIT_FAILED` (exit 4), abort with the same code.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-P4-Batch-Commit ok`\n\n### Step P5 — Push Epic Branch to Origin (optional, EPIC-0049)\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-P5-Push`\n\nIf `--dry-run` or `--no-commit` is set, log `\"dry-run, skipping push\"` and skip this step.\n\nOtherwise, delegate the push to `x-push-branch` so the canonical `epic\u002F\u003CXXXX>` branch is synchronized with origin:\n\n    Skill(skill: \"x-push-branch\", args: \"--branch epic\u002F\u003CXXXX>\")\n\nOn push failure (remote rejection, no connectivity), log a WARNING and continue — the local commit is preserved; the operator can re-run Step P5 or `git push` manually. Do NOT abort.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-P5-Push ok`\n\n## Error Envelope\n\n| Code | Condition |\n|------|-----------|\n| `STORY_NOT_FOUND` | Story file absent at `ai\u002Fepics\u002Fepic-XXXX\u002Fstory-XXXX-YYYY.md` |\n| `EPIC_BRANCH_ENSURE_FAILED` | Step P2 `x-internal-ensure-epic-branch` non-zero |\n| `CONSOLIDATION_FAILED` | No TASK_PROPOSAL entries returned by any subagent |\n| `WRITE_FAILED` | Unable to write output artifact to `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002F` |\n| `DOR_NOT_MET` | DoR validation returns \u003C 12\u002F12 checks passed |\n\n## Full Protocol\n\n> Complete per-phase detail (Phase 0 input resolution, staleness check, context-combination table, TASK_PROPOSAL format, consolidation algorithm with deterministic merge rules, Phase 3 conflict resolution, Phase 4 artifact templates, v2 Phases 4a–4c task-file-first execution, x-plan-task delegation per task, Phase 5 12-check DoR validation, commit conventions) and planning-guide reference in [`references\u002Ffull-protocol.md`](references\u002Ffull-protocol.md). Existing [`references\u002Fplanning-guide.md`](references\u002Fplanning-guide.md) preserved per story-0054-0003 audit.\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## Triggers\n\n```\n\u002Fx-plan-story STORY-ID             — plan story with 7 parallel agents\n\u002Fx-plan-story STORY-ID --force     — regenerate even if artifacts are fresh\n\u002Fx-plan-story STORY-ID --skip-dor  — skip Phase 5 DoR validation\n\u002Fx-plan-story STORY-ID --dry-run   — write artifacts but skip subagent\u002Fcommit steps\n\u002Fx-plan-story STORY-ID --no-commit — skip commit step (for orchestrators batch-committing)\n```\n\n## Parameters\n\n| Parameter | Type | Default | Description |\n|-----------|------|---------|-------------|\n| `STORY-ID` | positional | (required) | `story-XXXX-YYYY` format |\n| `--force` | boolean | `false` | Regenerate all artifacts even if fresh |\n| `--skip-dor` | boolean | `false` | Skip Phase 5 DoR validation |\n| `--dry-run` | boolean | `false` | Artifacts written but Steps P1\u002FP2\u002FP4\u002FP5 become no-ops |\n| `--no-commit` | boolean | `false` | Skip commit step; used by orchestrators batching commits at parent level |\n\n**CRITICAL:** 6 phases (0-5) all mandatory (unless `--skip-dor` skips Phase 5). Never stop before Phase 5. Print `>>> Phase N\u002F5 completed. Proceeding to Phase N+1...` after each phase.\n\n## Output Contract\n\n**Schema dispatch:**\n\n| `planningSchemaVersion` | Phases run |\n|--------------------------|------------|\n| `\"1.0\"` (or absent) | Phases 0-5 (legacy flow: task breakdown + planning report + DoR) |\n| `\"2.0\"` | Phases 0-5 + 4a-4c (v2: task-TASK-NNN.md + plan-task-TASK-NNN.md per task + task-implementation-map-STORY-*.md) |\n\n**Artifacts produced:**\n\n| Artifact | Path |\n|----------|------|\n| Task breakdown | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Ftasks-story-XXXX-YYYY.md` |\n| Planning report | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Fplanning-report-story-XXXX-YYYY.md` |\n| DoR checklist | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Fdor-story-XXXX-YYYY.md` |\n| Task files (v2) | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Ftask-TASK-XXXX-YYYY-NNN.md` per task |\n| Task plans (v2) | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Fplan-task-TASK-XXXX-YYYY-NNN.md` per task |\n| Task map (v2) | `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Ftask-implementation-map-STORY-XXXX-YYYY.md` |\n\n**Phase execution with telemetry:**\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-P1-Worktree-Detect`\n\n**Step P1 (Worktree Detect):** `Skill(skill: \"x-manage-worktrees\", args: \"detect-context\")` — advisory, fail-open. Skip when `--no-commit`.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-P1-Worktree-Detect ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-P2-Epic-Branch-Ensure`\n\n**Step P2 (Epic Branch Ensure):** `Skill(skill: \"x-internal-ensure-epic-branch\", args: \"--epic-id \u003CXXXX>\")` — idempotent. Abort on failure with `EPIC_BRANCH_ENSURE_FAILED`. Skip when `--no-commit` or `--dry-run`.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-P2-Epic-Branch-Ensure ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-1-Context-Gathering`\n\n**Phase 1 (Context Gathering):** Read story, epic, implementation map, and existing plan artifacts inline. Also read `.claude\u002Fskills\u002Fplanning-standards-kp\u002FSKILL.md` (RA9 contract: 9 sections, Packages format, Decision Rationale micro-template). See staleness check and context-combination matrix in references.\n\n> **RA9 guidance (EPIC-0056 \u002F planning-standards-kp):** When producing the consolidated plan, the Architect subagent MUST fill:\n> - **Section 2 (Packages Hexagonal):** Feature-level packages in each hexagonal layer from the story analysis.\n> - **Section 8 (Decision Rationale):** At least 1 feature-level decision using the 4-line micro-template.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-1-Context-Gathering ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-2-Parallel-Planning`\n\n**Phase 2 (Parallel Planning):** Dispatch 7 subagents in a **single message** (Rule 13 Pattern 2 — SUBAGENT-GENERAL) for true parallelism.\n\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story Architect`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story QA`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story Security`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story PentestEngineer`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story TechLead`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story PO`\n\u003C!-- TELEMETRY: subagent.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-start x-plan-story PerformanceEngineer`\n\nDispatch all 7 in ONE assistant message:\n\n    Agent(subagent_type: \"general-purpose\", model: \"opus\", description: \"Architect — story {STORY_ID}\", prompt: \"You are a Senior Architect. Read context files. Analyze story {STORY_ID}. Produce TASK_PROPOSAL entries (architecture, layers, dependencies). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"QA — story {STORY_ID}\", prompt: \"You are a QA Specialist. Read context files. Produce TASK_PROPOSAL entries (tests, coverage, acceptance criteria). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"Security — story {STORY_ID}\", prompt: \"You are a Security Specialist. Read knowledge\u002Fsecurity\u002Fapplication-security.md, knowledge\u002Fsecurity\u002Fsecurity-principles.md, and context files. Produce TASK_PROPOSAL entries (security, OWASP, threat model). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"PentestEngineer — story {STORY_ID}\", prompt: \"You are a Penetration Test Engineer. Read capabilities\u002Fquality\u002Fpentest\u002Fpentest-always-on.yaml and context files. Produce TASK_PROPOSAL entries (pentest scenarios, CVSS-rated vulnerabilities, exploitation paths). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"TechLead — story {STORY_ID}\", prompt: \"You are a Tech Lead. Read context files. Produce TASK_PROPOSAL entries (code quality, SOLID, complexity). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"PO — story {STORY_ID}\", prompt: \"You are a Product Owner. Read knowledge\u002Fcompliance.md and context files. Produce TASK_PROPOSAL entries (business value, acceptance, DoD, compliance). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n    Agent(subagent_type: \"general-purpose\", model: \"sonnet\", description: \"PerformanceEngineer — story {STORY_ID}\", prompt: \"You are a Performance Engineer. Read context files. Produce TASK_PROPOSAL entries (latency SLAs, throughput targets, load testing scenarios). Follow TASK_PROPOSAL format in references\u002Ffull-protocol.md.\")\n\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story Architect ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story QA ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story Security ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story PentestEngineer ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story TechLead ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story PO ok`\n\u003C!-- TELEMETRY: subagent.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh subagent-end x-plan-story PerformanceEngineer ok`\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-2-Parallel-Planning ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-3-Consolidation`\n\n**Phase 3 (Consolidation):** Merge all TASK_PROPOSAL entries using deterministic rules (majority-vote, duplicate elimination, dependency ordering). See consolidation algorithm in references.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-3-Consolidation ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-4-Artifact-Generation`\n\n**Phase 4 (Artifact Generation):** Write `tasks-story-*.md` and `planning-report-*.md`. v2 only: Phases 4a-4c emit per-task artifacts and task map (see references).\n\n**Phase 4b (v2 only — batch task-plan dispatch):** For each TASK-XXXX-YYYY-NNN, invoke `x-plan-task` in parallel (batch ≤ 4) with `--no-commit` so the caller aggregates into a single Step P4 commit:\n\n    Skill(skill: \"x-plan-task\",\n          args: \"--task-file ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Ftask-TASK-XXXX-YYYY-NNN.md --no-commit\")\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-4-Artifact-Generation ok`\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-5-DoR-Validation`\n\n**Phase 5 (DoR Validation):** Run 12 checks; v2 adds per-task READY checks. Skipped with `--skip-dor`.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-5-DoR-Validation ok`\n\n### Step P4 — Batch Planning Commit (EPIC-0049 \u002F RULE-007)\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-P4-Batch-Commit`\n\nIf `--dry-run` is set, log `\"dry-run, skipping commit\"` and skip this step. If `--no-commit` is set, skip as well — the parent orchestrator (e.g., `x-orchestrate-epic`) aggregates commits at the wave level.\n\nOtherwise, issue ONE consolidated commit covering every planning artifact produced by this story (task breakdown, planning report, DoR checklist, plan-story, all task files, all plan-task files, task map, and the updated `execution-state.json`):\n\n    Skill(skill: \"x-commit-planning\",\n          args: \"--scope docs --epic-id \u003CXXXX> --paths ai\u002Fepics\u002Fepic-\u003CXXXX>\u002Fplans\u002F ai\u002Fepics\u002Fepic-\u003CXXXX>\u002Fexecution-state.json --subject \\\"docs(story-\u003CXXXX>-\u003CYYYY>): add planning artifacts\\\"\")\n\nIdempotency: re-executing with identical inputs returns `commitSha=null` (silent no-op). On `COMMIT_FAILED` (exit 4), abort with the same code.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-P4-Batch-Commit ok`\n\n### Step P5 — Push Epic Branch to Origin (optional, EPIC-0049)\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-story Phase-P5-Push`\n\nIf `--dry-run` or `--no-commit` is set, log `\"dry-run, skipping push\"` and skip this step.\n\nOtherwise, delegate the push to `x-push-branch` so the canonical `epic\u002F\u003CXXXX>` branch is synchronized with origin:\n\n    Skill(skill: \"x-push-branch\", args: \"--branch epic\u002F\u003CXXXX>\")\n\nOn push failure (remote rejection, no connectivity), log a WARNING and continue — the local commit is preserved; the operator can re-run Step P5 or `git push` manually. Do NOT abort.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-story Phase-P5-Push ok`\n\n## Error Envelope\n\n| Code | Condition |\n|------|-----------|\n| `STORY_NOT_FOUND` | Story file absent at `ai\u002Fepics\u002Fepic-XXXX\u002Fstory-XXXX-YYYY.md` |\n| `EPIC_BRANCH_ENSURE_FAILED` | Step P2 `x-internal-ensure-epic-branch` non-zero |\n| `CONSOLIDATION_FAILED` | No TASK_PROPOSAL entries returned by any subagent |\n| `WRITE_FAILED` | Unable to write output artifact to `ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002F` |\n| `DOR_NOT_MET` | DoR validation returns \u003C 12\u002F12 checks passed |\n\n## Full Protocol\n\n> Complete per-phase detail (Phase 0 input resolution, staleness check, context-combination table, TASK_PROPOSAL format, consolidation algorithm with deterministic merge rules, Phase 3 conflict resolution, Phase 4 artifact templates, v2 Phases 4a–4c task-file-first execution, x-plan-task delegation per task, Phase 5 12-check DoR validation, commit conventions) and planning-guide reference in [`references\u002Ffull-protocol.md`](references\u002Ffull-protocol.md). Existing [`references\u002Fplanning-guide.md`](references\u002Fplanning-guide.md) preserved per story-0054-0003 audit.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":25,"context-budget":26,"user-invocable":27,"requires-capabilities":28},"Read, Write, Edit, Bash, Grep, Glob, Skill","[STORY-ID] [--force] [--skip-dor] [--dry-run] [--no-commit]","medium",true,[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-plan-story",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":39,"prompt":49,"zipAvailable":27},[40,43,46],{"tool":41,"command":42},"npx","npx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-plan-story",{"tool":44,"command":45},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-plan-story",{"tool":47,"command":48},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-plan-story","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-plan-story\u002FSKILL.md",[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"README.md","REFERENCE","参考文档",5094,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-plan-story\u002FREADME.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Ffull-protocol.md",6233,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-plan-story\u002Freferences\u002Ffull-protocol.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fplanning-guide.md",9083,"https:\u002F\u002Fgithub.com\u002Freview-bench\u002Federcnj_ia-dev-environment\u002Fblob\u002Fmain\u002Fsrc\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-plan-story\u002Freferences\u002Fplanning-guide.md",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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",[],[]]