[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754A8676FAKBCA2STWZCA0X":3,"skill-same:01M754A8676FAKBCA2STWZCA0X":57},{"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},"01M754A8676FAKBCA2STWZCA0X","x-plan-architecture",null,"Generates a comprehensive architecture plan with component diagrams, sequence diagrams, deployment topology, mini-ADRs, NFRs, and resilience\u002Fobservability strategies. Use before implementation to document design decisions.","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-architecture\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-plan-architecture\ndescription: \"Generates a comprehensive architecture plan with component diagrams, sequence diagrams, deployment topology, mini-ADRs, NFRs, and resilience\u002Fobservability strategies. Use before implementation to document design decisions.\"\nuser-invocable: true\nallowed-tools: Read, Write, Edit, Bash, Grep, Glob\nargument-hint: \"[STORY-ID or feature-name]\"\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# Skill: Architecture Plan Generator\n\n## Purpose\n\nGenerates a comprehensive architecture plan for {{PROJECT_NAME}} with component diagrams, sequence diagrams, deployment topology, mini-ADRs, NFRs, and resilience\u002Fobservability strategies. Use before implementation to document design decisions.\n\n## Triggers\n\n- `\u002Fx-plan-architecture STORY-ID` — generate architecture plan from story\n- `\u002Fx-plan-architecture \"Feature Name\"` — generate from feature description\n- `\u002Fx-plan-architecture ai\u002Fepics\u002Fepic-XXXX\u002Fstory-XXXX-YYYY.md` — generate from story file path\n\n## Parameters\n\n| Parameter | Type | Default | Values | Description |\n|-----------|------|---------|--------|-------------|\n| `argument` | String | required | story ID, feature name, or file path | Source for architecture plan generation |\n\n### Decision Tree\n\nEvaluate the change scope to determine the plan level:\n\n| Condition | Plan Level |\n|-----------|-----------|\n| New service \u002F new integration \u002F contract change \u002F infra change | **Full** |\n| New feature, no contract or infra change | **Simplified** |\n| Bug fix \u002F refactor \u002F docs-only | **Skip** |\n\n#### Full Architecture Plan\n\nApply when **any** of these conditions is true:\n\n- New service or module being created\n- New external integration (database, message broker, third-party API)\n- Change to a public contract (REST API, gRPC proto, GraphQL schema, event schema)\n- Infrastructure topology change (new container, new deployment target, new network policy)\n\n#### Simplified Architecture Plan\n\nApply when:\n\n- New feature in an existing service **without** contract or infrastructure changes\n- Only affected sections are generated (skip unrelated diagrams)\n\n#### Skip Architecture Plan\n\nApply when:\n\n- Bug fix with no architectural impact\n- Internal refactoring (no public API or contract change)\n- Documentation-only change\n\n## Workflow\n\n```\n1. PRE-CHECK  -> Verify idempotency (RULE-002)\n2. TEMPLATE   -> Load template or use inline fallback (RULE-007)\n3. READ       -> Read story\u002Ffeature requirements\n4. EVALUATE   -> Determine plan level (Full\u002FSimplified\u002FSkip)\n5. CONTEXT    -> Read knowledge packs\n6. REVIEW     -> Review existing architecture\n7. GENERATE   -> Generate architecture plan document\n8. VALIDATE   -> Verify section completeness\n```\n\n### Step 1 — Idempotency Pre-Check (RULE-002 — Idempotency)\n\nBefore generating an architecture plan, check whether one already exists and is still fresh.\n\n#### Pre-Check Algorithm\n\n```\n1. Resolve the expected output path:\n   ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Farchitecture-story-XXXX-YYYY.md\n\n2. IF the file does NOT exist:\n   - Log: \"Generating architecture plan for {story}\"\n   - Proceed to generation\n\n3. IF the file EXISTS:\n   a. Compare modification times:\n      - story_mtime = mtime of the story file\n      - plan_mtime  = mtime of the architecture plan file\n   b. IF story_mtime \u003C= plan_mtime:\n      - Log: \"Reusing existing architecture plan from {date}\"\n      - STOP — do NOT regenerate\n   c. IF story_mtime > plan_mtime:\n      - Log: \"Regenerating stale architecture plan for {story}\"\n      - Proceed to generation\n```\n\n#### Staleness Decision Table\n\n| Condition | Action | Log Message |\n|-----------|--------|-------------|\n| Plan does not exist | Generate new | `Generating architecture plan for {story}` |\n| Plan exists, story not modified | Reuse existing | `Reusing existing architecture plan from {date}` |\n| Plan exists, story modified after plan | Regenerate | `Regenerating stale architecture plan for {story}` |\n\n### Step 2 — Template Loading (RULE-007 — Template Reference)\n\n```\n1. Check if `.claude\u002Ftemplates\u002F_TEMPLATE-ARCHITECTURE-PLAN.md` exists\n2. IF template exists:\n   - Read the template\n   - Use its 13 sections as the required output structure\n   - Log: \"Using architecture plan template v1.0.0\"\n3. IF template does NOT exist (RULE-012 fallback):\n   - Log WARNING: \"Template not found, using inline format\"\n   - Fall back to the inline Output Structure defined below\n   - Execution continues normally — no interruption\n```\n\n**Template Fallback:** When the template file is missing, the skill degrades gracefully to the inline Output Structure. No interruption occurs. A WARNING is logged.\n\n### Step 3 — Read Story\u002FFeature Requirements\n\nRead the story file or feature description provided as argument. Extract: scope, acceptance criteria, integrations, NFRs, constraints.\n\n### Step 4 — Evaluate Decision Tree\n\nDetermine if this requires a Full Plan, Simplified Plan, or Skip:\n- If Skip: report \"Architecture plan not needed for this change\" and stop\n- If Full or Simplified: proceed to knowledge pack reading\n\n### Step 5 — Read Knowledge Packs\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-architecture Phase-1-KP-Read`\n\nRead knowledge packs **in order** before generating the architecture plan. For Simplified Plan, read only Architecture KP + KPs relevant to affected sections.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-architecture Phase-1-KP-Read ok`\n\n### Step 6 — Review Existing Architecture\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-architecture Phase-2-Component-Diagram`\n\n- Check for existing architecture documents in `steering\u002F`\n- Review current codebase structure to understand the baseline\n- Identify what is new vs. what is changing\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-architecture Phase-2-Component-Diagram ok`\n\n### Step 7 — Generate Architecture Plan\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-architecture Phase-3-Sequence-Diagrams`\n\nLaunch a **single** `general-purpose` subagent with explicit `model: \"opus\"` (Rule 23 RULE-002 — deep architectural reasoning justifies Opus). Generate ALL mandatory sections.\n\n    Agent(\n      subagent_type: \"general-purpose\",\n      model: \"opus\",\n      description: \"Architect generates mandatory sections for architecture plan\",\n      prompt: \"Generate all mandatory sections of the architecture plan per the template loaded above\"\n    )\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-architecture Phase-3-Sequence-Diagrams ok`\n\n### Step 8 — Validate Sections Post-Generation\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-architecture Phase-4-ADR-Mini`\n\n```\n1. Parse the generated document for H2 headings (## Section Name)\n2. Count sections found vs. sections expected\n3. For each conditional section:\n   - IF capability is enabled AND section is missing -> WARNING\n   - IF capability is disabled AND section is absent -> OK (conditional skip)\n4. For each mandatory section:\n   - IF section is missing -> WARNING with instruction to complete\n5. Log checklist:\n   - All present: \"Architecture plan: 13\u002F13 sections present\"\n   - Some missing: \"Architecture plan: X\u002FY applicable sections present, Z conditional skipped\"\n```\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-architecture Phase-4-ADR-Mini ok`\n\n## Mandatory Sections (13)\n\n| # | Section | Mandatory | Conditional |\n|---|---------|-----------|-------------|\n| 1 | Header | Yes | -- |\n| 2 | Executive Summary | Yes | -- |\n| 3 | Component Diagram | Yes | -- |\n| 4 | Sequence Diagrams | Yes | -- |\n| 5 | Deployment Diagram | Yes | orchestrator != none |\n| 6 | External Connections | Yes | -- |\n| 7 | Architecture Decisions | Yes | -- |\n| 8 | Technology Stack | Yes | -- |\n| 9 | Non-Functional Requirements | Yes | -- |\n| 10 | Data Model | Yes | database != none |\n| 11 | Observability Strategy | Yes | -- |\n| 12 | Resilience Strategy | Yes | -- |\n| 13 | Impact Analysis | Yes | -- |\n\n### Conditional Section Rules\n\n- **Deployment Diagram**: Include when `orchestrator != none`. When not applicable, write `N\u002FA - capability not enabled`.\n- **Data Model**: Include when `database != none`. When not applicable, write `N\u002FA - capability not enabled`.\n- **Event Schema**: Include when `eventDriven: true`. When not applicable, write `N\u002FA - capability not enabled`.\n\n## Output Structure\n\n| # | Section | Type | Format | Description |\n|---|---------|------|--------|-------------|\n| 1 | `# Architecture Plan — {title}` | M | Markdown H1 | Title with story ID or feature name |\n| 2 | `## Executive Summary` | M | Paragraph | One-paragraph overview of the architecture |\n| 3 | `## Component Diagram` | M | Mermaid `graph TD` | Components, layers, and dependency arrows |\n| 4 | `## Sequence Diagrams` | M | Mermaid `sequenceDiagram` | Main flows (happy path + primary error path) |\n| 5 | `## Deployment Diagram` | M | Mermaid `graph TD` | Infrastructure nodes, networking, load balancers |\n| 6 | `## External Connections` | M | Markdown table | System, Protocol, Purpose, SLO columns |\n| 7 | `## Architecture Decisions` | M | Mini-ADR format | Key decisions with Context\u002FDecision\u002FRationale |\n| 8 | `## Technology Stack` | M | Markdown table | Component, Technology, Version, Rationale columns |\n| 9 | `## Non-Functional Requirements` | M | Markdown table | Metric, Target, Measurement columns |\n| 10 | `## Data Model` | O | Mermaid `erDiagram` or table | Entities and relationships (if applicable) |\n| 11 | `## Observability Strategy` | M | Markdown section | Key metrics, trace spans, log patterns, alerts |\n| 12 | `## Resilience Strategy` | M | Markdown section | Circuit breakers, retries, fallbacks, degradation |\n| 13 | `## Impact Analysis` | M | Markdown section | Affected services, migration plan, rollback strategy |\n\n**Minimum mandatory sections:** 12 (all M sections).\n\n### Output Path\n\n```\nai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Farch-story-XXXX-YYYY.md\n```\n\nWhere `XXXX` is the epic ID and `YYYY` is the story sequence number extracted from the story ID.\n\n### Origin Marker (EPIC-0059 — mandatory)\n\nEvery generated architecture plan MUST start with a YAML frontmatter block:\n\n```yaml\n---\ngenerated-by: x-plan-architecture@\u003C40-char-git-sha>\ngenerated-at: \u003CISO-8601-UTC>\nstory-id: \u003Cstory-id>\n---\n```\n\nCapture the SHA and timestamp at write time:\n- SHA: `git rev-parse HEAD 2>\u002Fdev\u002Fnull || echo \"unknown\"`\n- Timestamp: `date -u +%Y-%m-%dT%H:%M:%SZ`\n\nThis frontmatter is required by `audit-execution-integrity.sh` Phase-1 validation (EPIC-0059, Rule 24).\nArtifacts without this block fail the CI audit with `EIE_EVIDENCE_MISSING`.\n\n## Mini-ADR Format\n\nEach architectural decision is documented inline using this simplified format:\n\n```markdown\n### ADR-NNN: {Decision Title}\n\n**Status:** Proposed | Accepted | Deprecated | Superseded\n\n**Context:**\n{What is the issue or force motivating this decision? 2-3 sentences.}\n\n**Decision:**\n{What is the change being proposed or adopted? 1-2 sentences.}\n\n**Rationale:**\n{Why was this option chosen over alternatives? List key trade-offs.}\n\n**Consequences:**\n- Positive: {benefits}\n- Negative: {trade-offs or risks}\n\n**Story Reference:** {STORY-ID}\n```\n\n**Rules:**\n- Number ADRs sequentially within the document (ADR-001, ADR-002, ...)\n- Each ADR must have a Story Reference linking back to the originating story\n- Status must be one of: Proposed, Accepted, Deprecated, Superseded\n- Context and Decision are mandatory; Consequences may be brief for simple decisions\n\n## Subagent Prompt\n\nLaunch a **single** `general-purpose` subagent with explicit `model: \"opus\"` (Rule 23 RULE-002 — deep architectural reasoning justifies Opus):\n\n    Agent(\n      subagent_type: \"general-purpose\",\n      model: \"opus\",\n      description: \"Senior Architect generates architecture plan for project\",\n      prompt: \"\u003Csee the blockquote below>\"\n    )\n\n> You are a **Senior Architect** generating a comprehensive architecture plan for {{PROJECT_NAME}}.\n>\n> **Step 1 — Read the template (RULE-007):**\n> - Read template at `.claude\u002Ftemplates\u002F_TEMPLATE-ARCHITECTURE-PLAN.md` for required output format\n> - If the template file does not exist, use the inline Output Structure defined in this skill as fallback (RULE-012)\n> - Log which format source is being used\n>\n> **Step 2 — Read the story\u002Ffeature requirements:**\n> - Read the story file or feature description provided as argument\n> - Extract: scope, acceptance criteria, integrations, NFRs, constraints\n>\n> **Step 3 — Evaluate the decision tree:**\n> - Determine if this requires a Full Plan, Simplified Plan, or Skip\n> - If Skip: report \"Architecture plan not needed for this change\" and stop\n>\n> **Step 4 — Read knowledge packs (in order):**\n> - `knowledge\u002Farchitecture\u002Farchitecture-principles.md` — layer structure, dependency direction\n> - `knowledge\u002Farchitecture\u002Farchitecture-patterns.md` — design patterns\n> - `knowledge\u002Fprotocols.md` — protocol conventions for the project's interfaces\n> - `knowledge\u002Fsecurity\u002Freferences\u002F` — OWASP, headers, secrets\n> - `knowledge\u002Fobservability\u002Freferences\u002F` — tracing, metrics, logging\n> - `knowledge\u002Finfrastructure.md` — Docker, K8s, 12-factor\n> - `knowledge\u002Fresilience\u002Freferences\u002F` — circuit breaker, retry, fallback\n> - `knowledge\u002Fcompliance.md` — only if compliance frameworks are active\n>\n> For Simplified Plan: read only Architecture KP + KPs relevant to affected sections.\n>\n> **Step 5 — Review existing architecture:**\n> - Check for existing architecture documents in `steering\u002F`\n> - Review current codebase structure to understand the baseline\n> - Identify what is new vs. what is changing\n>\n> **Step 6 — Generate the architecture plan** with ALL mandatory sections:\n>\n> 1. **Executive Summary** — one paragraph overview\n> 2. **Component Diagram** — Mermaid `graph TD` showing layers and dependencies\n> 3. **Sequence Diagrams** — Mermaid `sequenceDiagram` for main flows\n> 4. **Deployment Diagram** — Mermaid `graph TD` with infrastructure nodes\n> 5. **External Connections** — table: System | Protocol | Purpose | SLO\n> 6. **Architecture Decisions** — mini-ADRs (Context\u002FDecision\u002FRationale per decision)\n> 7. **Technology Stack** — table: Component | Technology | Version | Rationale\n> 8. **Non-Functional Requirements** — table: Metric | Target | Measurement\n> 9. **Data Model** — erDiagram or table (if applicable, skip if no data changes)\n> 10. **Observability Strategy** — key metrics, trace spans, structured log fields, alerts\n> 11. **Resilience Strategy** — circuit breakers, retry policies, fallback chains, graceful degradation\n> 12. **Impact Analysis** — affected services, migration steps, rollback strategy, risk assessment\n>\n> **Step 7 — Emit origin marker and save the document (EPIC-0059 — mandatory):**\n>\n> Before writing the artifact, prepend the YAML frontmatter block at the very top:\n>\n> ```yaml\n> ---\n> generated-by: x-plan-architecture@$(git rev-parse HEAD 2>\u002Fdev\u002Fnull || echo \"unknown\")\n> generated-at: $(date -u +%Y-%m-%dT%H:%M:%SZ)\n> story-id: ${STORY_ID}\n> ---\n> ```\n>\n> Then write the full document content after the closing `---`. The frontmatter is required by\n> `audit-execution-integrity.sh` Phase-1 validation (EPIC-0059, Rule 24). Output path:\n> ```\n> ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Farch-story-XXXX-YYYY.md\n> ```\n>\n> **Step 8 — Validate sections post-generation:**\n> - Parse the generated document for all 13 expected sections\n> - For conditional sections (Deployment Diagram, Data Model, Event Schema):\n>   check project capabilities and mark as \"N\u002FA - capability not enabled\" if not applicable\n> - Log section checklist: \"Architecture plan: X\u002FY sections present\"\n> - If any mandatory section is missing, log a WARNING with instruction to complete\n>\n> **Conventions:**\n> - All diagrams MUST use Mermaid syntax\n> - All text MUST be in English\n> - Mini-ADRs follow the inline format (Context\u002FDecision\u002FRationale\u002FConsequences\u002FStory Reference)\n> - Tables use GitHub-flavored Markdown\n> - NFR targets must be measurable (e.g., \"p99 latency \u003C 200ms\", not \"fast\")\n\n## Knowledge Pack References\n\n| # | Knowledge Pack | Path | Purpose |\n|---|----------------|------|---------|\n| 1 | Architecture | `knowledge\u002Farchitecture\u002Farchitecture-principles.md` | Layer structure, dependency direction, package conventions |\n| 2 | Architecture Patterns | `knowledge\u002Farchitecture\u002Farchitecture-patterns.md` | Design patterns, CQRS, event sourcing, saga |\n| 3 | Protocols | `knowledge\u002Fprotocols.md` | REST, gRPC, GraphQL, WebSocket, event-driven conventions |\n| 4 | Security | `knowledge\u002Fsecurity\u002Freferences\u002F` | OWASP Top 10, security headers, secrets management |\n| 5 | Observability | `knowledge\u002Fobservability\u002Freferences\u002F` | Tracing, metrics, logging, health checks |\n| 6 | Infrastructure | `knowledge\u002Finfrastructure.md` | Docker, Kubernetes, 12-factor app |\n| 7 | Resilience | `knowledge\u002Fresilience\u002Freferences\u002F` | Circuit breaker, retry, fallback, bulkhead |\n| 8 | Compliance | `knowledge\u002Fcompliance.md` | GDPR, HIPAA, LGPD (if compliance is active) |\n\n**Minimum KPs for Full Plan:** 7 (all except Compliance, which is conditional).\n**Minimum KPs for Simplified Plan:** 1 (Architecture only; add others as relevant).\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Story file not found | Abort with \"Story file not found: {path}\" |\n| Template not found | Log WARNING, fall back to inline Output Structure (RULE-012) |\n| Knowledge pack not found | Log WARNING, continue with available KPs |\n| Subagent fails | Abort with error details, suggest manual generation |\n| Post-validation finds missing mandatory section | Log WARNING with instruction to complete the section |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-implement-story | Called by | Invoked during Phase 1 for architecture planning; pre-check ensures idempotency |\n| x-model-threats | Complements | Architecture plan feeds threat model generation |\n| x-implement-task | Consumed by | Implementation phase reads architecture plan alongside implementation plan |\n| x-update-architecture | Followed by | After implementation, architecture document is updated incrementally |\n\n## Detailed References\n\nFor in-depth guidance on architecture patterns, consult:\n- `knowledge\u002Farchitecture.md` — full architecture reference\n- `knowledge\u002Fprotocols.md` — protocol conventions\n- `knowledge\u002Fsecurity\u002Findex.md` — security standards\n- `knowledge\u002Fobservability\u002Findex.md` — observability patterns\n- `knowledge\u002Fresilience\u002Findex.md` — resilience patterns\n- `knowledge\u002Finfrastructure.md` — infrastructure patterns\n\n## Planning Status Propagation (Rule 22 \u002F EPIC-0046)\n\n> V2-gated: only runs when `SchemaVersionResolver.resolve(ai\u002Fepics\u002Fepic-XXXX\u002Fexecution-state.json) == V2`. v1 epics: skip silently (Rule 19).\n\nAfter writing `arch-story-XXXX-YYYY.md`, this skill checks the associated story's lifecycle status. The architecture plan does NOT itself drive the `Pendente → Planejada` transition — that is owned by `x-plan-story` (Rule 22 single-writer invariant). If the story is still `Pendente` when the architecture plan is generated standalone (i.e. `x-plan-architecture` invoked directly without `x-plan-story`), transition it to `Planejada` here (idempotent if already `Planejada`).\n\n**Steps (end of architecture-plan generation, BEFORE the final commit):**\n\n1. Detect v2 via SchemaVersionResolver on the epic's `execution-state.json`. If v1: skip.\n2. Read the story's current status via the CLI:\n   ```bash\n   CURRENT=$(java -cp $CLAUDE_PROJECT_DIR\u002Fjava\u002Ftarget\u002Fclasses \\\n       dev.iadev.adapter.inbound.cli.StatusFieldParserCli \\\n       read ai\u002Fepics\u002Fepic-XXXX\u002Fstory-XXXX-YYYY.md)\n   ```\n3. If `CURRENT == \"Pendente\"`, write `Planejada`:\n   ```bash\n   java -cp $CLAUDE_PROJECT_DIR\u002Fjava\u002Ftarget\u002Fclasses \\\n       dev.iadev.adapter.inbound.cli.StatusFieldParserCli \\\n       write ai\u002Fepics\u002Fepic-XXXX\u002Fstory-XXXX-YYYY.md Planejada\n   ```\n   If `CURRENT == \"Planejada\"`: idempotent no-op.\n4. Stage both files and commit via `x-commit-changes`:\n   ```bash\n   git add ai\u002Fepics\u002Fepic-XXXX\u002Fstory-XXXX-YYYY.md ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Farch-story-XXXX-YYYY.md\n   ```\n   Then:\n\n       Skill(skill: \"x-commit-changes\", args: \"docs(story-XXXX-YYYY): add architecture plan + update status to Planejada\")\n\n**Fail-loud:** non-zero exit from CLI → abort skill (RULE-046-08).\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: Architecture Plan Generator\n\n## Purpose\n\nGenerates a comprehensive architecture plan for {{PROJECT_NAME}} with component diagrams, sequence diagrams, deployment topology, mini-ADRs, NFRs, and resilience\u002Fobservability strategies. Use before implementation to document design decisions.\n\n## Triggers\n\n- `\u002Fx-plan-architecture STORY-ID` — generate architecture plan from story\n- `\u002Fx-plan-architecture \"Feature Name\"` — generate from feature description\n- `\u002Fx-plan-architecture ai\u002Fepics\u002Fepic-XXXX\u002Fstory-XXXX-YYYY.md` — generate from story file path\n\n## Parameters\n\n| Parameter | Type | Default | Values | Description |\n|-----------|------|---------|--------|-------------|\n| `argument` | String | required | story ID, feature name, or file path | Source for architecture plan generation |\n\n### Decision Tree\n\nEvaluate the change scope to determine the plan level:\n\n| Condition | Plan Level |\n|-----------|-----------|\n| New service \u002F new integration \u002F contract change \u002F infra change | **Full** |\n| New feature, no contract or infra change | **Simplified** |\n| Bug fix \u002F refactor \u002F docs-only | **Skip** |\n\n#### Full Architecture Plan\n\nApply when **any** of these conditions is true:\n\n- New service or module being created\n- New external integration (database, message broker, third-party API)\n- Change to a public contract (REST API, gRPC proto, GraphQL schema, event schema)\n- Infrastructure topology change (new container, new deployment target, new network policy)\n\n#### Simplified Architecture Plan\n\nApply when:\n\n- New feature in an existing service **without** contract or infrastructure changes\n- Only affected sections are generated (skip unrelated diagrams)\n\n#### Skip Architecture Plan\n\nApply when:\n\n- Bug fix with no architectural impact\n- Internal refactoring (no public API or contract change)\n- Documentation-only change\n\n## Workflow\n\n```\n1. PRE-CHECK  -> Verify idempotency (RULE-002)\n2. TEMPLATE   -> Load template or use inline fallback (RULE-007)\n3. READ       -> Read story\u002Ffeature requirements\n4. EVALUATE   -> Determine plan level (Full\u002FSimplified\u002FSkip)\n5. CONTEXT    -> Read knowledge packs\n6. REVIEW     -> Review existing architecture\n7. GENERATE   -> Generate architecture plan document\n8. VALIDATE   -> Verify section completeness\n```\n\n### Step 1 — Idempotency Pre-Check (RULE-002 — Idempotency)\n\nBefore generating an architecture plan, check whether one already exists and is still fresh.\n\n#### Pre-Check Algorithm\n\n```\n1. Resolve the expected output path:\n   ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Farchitecture-story-XXXX-YYYY.md\n\n2. IF the file does NOT exist:\n   - Log: \"Generating architecture plan for {story}\"\n   - Proceed to generation\n\n3. IF the file EXISTS:\n   a. Compare modification times:\n      - story_mtime = mtime of the story file\n      - plan_mtime  = mtime of the architecture plan file\n   b. IF story_mtime \u003C= plan_mtime:\n      - Log: \"Reusing existing architecture plan from {date}\"\n      - STOP — do NOT regenerate\n   c. IF story_mtime > plan_mtime:\n      - Log: \"Regenerating stale architecture plan for {story}\"\n      - Proceed to generation\n```\n\n#### Staleness Decision Table\n\n| Condition | Action | Log Message |\n|-----------|--------|-------------|\n| Plan does not exist | Generate new | `Generating architecture plan for {story}` |\n| Plan exists, story not modified | Reuse existing | `Reusing existing architecture plan from {date}` |\n| Plan exists, story modified after plan | Regenerate | `Regenerating stale architecture plan for {story}` |\n\n### Step 2 — Template Loading (RULE-007 — Template Reference)\n\n```\n1. Check if `.claude\u002Ftemplates\u002F_TEMPLATE-ARCHITECTURE-PLAN.md` exists\n2. IF template exists:\n   - Read the template\n   - Use its 13 sections as the required output structure\n   - Log: \"Using architecture plan template v1.0.0\"\n3. IF template does NOT exist (RULE-012 fallback):\n   - Log WARNING: \"Template not found, using inline format\"\n   - Fall back to the inline Output Structure defined below\n   - Execution continues normally — no interruption\n```\n\n**Template Fallback:** When the template file is missing, the skill degrades gracefully to the inline Output Structure. No interruption occurs. A WARNING is logged.\n\n### Step 3 — Read Story\u002FFeature Requirements\n\nRead the story file or feature description provided as argument. Extract: scope, acceptance criteria, integrations, NFRs, constraints.\n\n### Step 4 — Evaluate Decision Tree\n\nDetermine if this requires a Full Plan, Simplified Plan, or Skip:\n- If Skip: report \"Architecture plan not needed for this change\" and stop\n- If Full or Simplified: proceed to knowledge pack reading\n\n### Step 5 — Read Knowledge Packs\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-architecture Phase-1-KP-Read`\n\nRead knowledge packs **in order** before generating the architecture plan. For Simplified Plan, read only Architecture KP + KPs relevant to affected sections.\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-architecture Phase-1-KP-Read ok`\n\n### Step 6 — Review Existing Architecture\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-architecture Phase-2-Component-Diagram`\n\n- Check for existing architecture documents in `steering\u002F`\n- Review current codebase structure to understand the baseline\n- Identify what is new vs. what is changing\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-architecture Phase-2-Component-Diagram ok`\n\n### Step 7 — Generate Architecture Plan\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-architecture Phase-3-Sequence-Diagrams`\n\nLaunch a **single** `general-purpose` subagent with explicit `model: \"opus\"` (Rule 23 RULE-002 — deep architectural reasoning justifies Opus). Generate ALL mandatory sections.\n\n    Agent(\n      subagent_type: \"general-purpose\",\n      model: \"opus\",\n      description: \"Architect generates mandatory sections for architecture plan\",\n      prompt: \"Generate all mandatory sections of the architecture plan per the template loaded above\"\n    )\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-architecture Phase-3-Sequence-Diagrams ok`\n\n### Step 8 — Validate Sections Post-Generation\n\n\u003C!-- TELEMETRY: phase.start -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh start x-plan-architecture Phase-4-ADR-Mini`\n\n```\n1. Parse the generated document for H2 headings (## Section Name)\n2. Count sections found vs. sections expected\n3. For each conditional section:\n   - IF capability is enabled AND section is missing -> WARNING\n   - IF capability is disabled AND section is absent -> OK (conditional skip)\n4. For each mandatory section:\n   - IF section is missing -> WARNING with instruction to complete\n5. Log checklist:\n   - All present: \"Architecture plan: 13\u002F13 sections present\"\n   - Some missing: \"Architecture plan: X\u002FY applicable sections present, Z conditional skipped\"\n```\n\n\u003C!-- TELEMETRY: phase.end -->\nBash command: `$CLAUDE_PROJECT_DIR\u002F.claude\u002Fhooks\u002Ftelemetry-phase.sh end x-plan-architecture Phase-4-ADR-Mini ok`\n\n## Mandatory Sections (13)\n\n| # | Section | Mandatory | Conditional |\n|---|---------|-----------|-------------|\n| 1 | Header | Yes | -- |\n| 2 | Executive Summary | Yes | -- |\n| 3 | Component Diagram | Yes | -- |\n| 4 | Sequence Diagrams | Yes | -- |\n| 5 | Deployment Diagram | Yes | orchestrator != none |\n| 6 | External Connections | Yes | -- |\n| 7 | Architecture Decisions | Yes | -- |\n| 8 | Technology Stack | Yes | -- |\n| 9 | Non-Functional Requirements | Yes | -- |\n| 10 | Data Model | Yes | database != none |\n| 11 | Observability Strategy | Yes | -- |\n| 12 | Resilience Strategy | Yes | -- |\n| 13 | Impact Analysis | Yes | -- |\n\n### Conditional Section Rules\n\n- **Deployment Diagram**: Include when `orchestrator != none`. When not applicable, write `N\u002FA - capability not enabled`.\n- **Data Model**: Include when `database != none`. When not applicable, write `N\u002FA - capability not enabled`.\n- **Event Schema**: Include when `eventDriven: true`. When not applicable, write `N\u002FA - capability not enabled`.\n\n## Output Structure\n\n| # | Section | Type | Format | Description |\n|---|---------|------|--------|-------------|\n| 1 | `# Architecture Plan — {title}` | M | Markdown H1 | Title with story ID or feature name |\n| 2 | `## Executive Summary` | M | Paragraph | One-paragraph overview of the architecture |\n| 3 | `## Component Diagram` | M | Mermaid `graph TD` | Components, layers, and dependency arrows |\n| 4 | `## Sequence Diagrams` | M | Mermaid `sequenceDiagram` | Main flows (happy path + primary error path) |\n| 5 | `## Deployment Diagram` | M | Mermaid `graph TD` | Infrastructure nodes, networking, load balancers |\n| 6 | `## External Connections` | M | Markdown table | System, Protocol, Purpose, SLO columns |\n| 7 | `## Architecture Decisions` | M | Mini-ADR format | Key decisions with Context\u002FDecision\u002FRationale |\n| 8 | `## Technology Stack` | M | Markdown table | Component, Technology, Version, Rationale columns |\n| 9 | `## Non-Functional Requirements` | M | Markdown table | Metric, Target, Measurement columns |\n| 10 | `## Data Model` | O | Mermaid `erDiagram` or table | Entities and relationships (if applicable) |\n| 11 | `## Observability Strategy` | M | Markdown section | Key metrics, trace spans, log patterns, alerts |\n| 12 | `## Resilience Strategy` | M | Markdown section | Circuit breakers, retries, fallbacks, degradation |\n| 13 | `## Impact Analysis` | M | Markdown section | Affected services, migration plan, rollback strategy |\n\n**Minimum mandatory sections:** 12 (all M sections).\n\n### Output Path\n\n```\nai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Farch-story-XXXX-YYYY.md\n```\n\nWhere `XXXX` is the epic ID and `YYYY` is the story sequence number extracted from the story ID.\n\n### Origin Marker (EPIC-0059 — mandatory)\n\nEvery generated architecture plan MUST start with a YAML frontmatter block:\n\n```yaml\n---\ngenerated-by: x-plan-architecture@\u003C40-char-git-sha>\ngenerated-at: \u003CISO-8601-UTC>\nstory-id: \u003Cstory-id>\n---\n```\n\nCapture the SHA and timestamp at write time:\n- SHA: `git rev-parse HEAD 2>\u002Fdev\u002Fnull || echo \"unknown\"`\n- Timestamp: `date -u +%Y-%m-%dT%H:%M:%SZ`\n\nThis frontmatter is required by `audit-execution-integrity.sh` Phase-1 validation (EPIC-0059, Rule 24).\nArtifacts without this block fail the CI audit with `EIE_EVIDENCE_MISSING`.\n\n## Mini-ADR Format\n\nEach architectural decision is documented inline using this simplified format:\n\n```markdown\n### ADR-NNN: {Decision Title}\n\n**Status:** Proposed | Accepted | Deprecated | Superseded\n\n**Context:**\n{What is the issue or force motivating this decision? 2-3 sentences.}\n\n**Decision:**\n{What is the change being proposed or adopted? 1-2 sentences.}\n\n**Rationale:**\n{Why was this option chosen over alternatives? List key trade-offs.}\n\n**Consequences:**\n- Positive: {benefits}\n- Negative: {trade-offs or risks}\n\n**Story Reference:** {STORY-ID}\n```\n\n**Rules:**\n- Number ADRs sequentially within the document (ADR-001, ADR-002, ...)\n- Each ADR must have a Story Reference linking back to the originating story\n- Status must be one of: Proposed, Accepted, Deprecated, Superseded\n- Context and Decision are mandatory; Consequences may be brief for simple decisions\n\n## Subagent Prompt\n\nLaunch a **single** `general-purpose` subagent with explicit `model: \"opus\"` (Rule 23 RULE-002 — deep architectural reasoning justifies Opus):\n\n    Agent(\n      subagent_type: \"general-purpose\",\n      model: \"opus\",\n      description: \"Senior Architect generates architecture plan for project\",\n      prompt: \"\u003Csee the blockquote below>\"\n    )\n\n> You are a **Senior Architect** generating a comprehensive architecture plan for {{PROJECT_NAME}}.\n>\n> **Step 1 — Read the template (RULE-007):**\n> - Read template at `.claude\u002Ftemplates\u002F_TEMPLATE-ARCHITECTURE-PLAN.md` for required output format\n> - If the template file does not exist, use the inline Output Structure defined in this skill as fallback (RULE-012)\n> - Log which format source is being used\n>\n> **Step 2 — Read the story\u002Ffeature requirements:**\n> - Read the story file or feature description provided as argument\n> - Extract: scope, acceptance criteria, integrations, NFRs, constraints\n>\n> **Step 3 — Evaluate the decision tree:**\n> - Determine if this requires a Full Plan, Simplified Plan, or Skip\n> - If Skip: report \"Architecture plan not needed for this change\" and stop\n>\n> **Step 4 — Read knowledge packs (in order):**\n> - `knowledge\u002Farchitecture\u002Farchitecture-principles.md` — layer structure, dependency direction\n> - `knowledge\u002Farchitecture\u002Farchitecture-patterns.md` — design patterns\n> - `knowledge\u002Fprotocols.md` — protocol conventions for the project's interfaces\n> - `knowledge\u002Fsecurity\u002Freferences\u002F` — OWASP, headers, secrets\n> - `knowledge\u002Fobservability\u002Freferences\u002F` — tracing, metrics, logging\n> - `knowledge\u002Finfrastructure.md` — Docker, K8s, 12-factor\n> - `knowledge\u002Fresilience\u002Freferences\u002F` — circuit breaker, retry, fallback\n> - `knowledge\u002Fcompliance.md` — only if compliance frameworks are active\n>\n> For Simplified Plan: read only Architecture KP + KPs relevant to affected sections.\n>\n> **Step 5 — Review existing architecture:**\n> - Check for existing architecture documents in `steering\u002F`\n> - Review current codebase structure to understand the baseline\n> - Identify what is new vs. what is changing\n>\n> **Step 6 — Generate the architecture plan** with ALL mandatory sections:\n>\n> 1. **Executive Summary** — one paragraph overview\n> 2. **Component Diagram** — Mermaid `graph TD` showing layers and dependencies\n> 3. **Sequence Diagrams** — Mermaid `sequenceDiagram` for main flows\n> 4. **Deployment Diagram** — Mermaid `graph TD` with infrastructure nodes\n> 5. **External Connections** — table: System | Protocol | Purpose | SLO\n> 6. **Architecture Decisions** — mini-ADRs (Context\u002FDecision\u002FRationale per decision)\n> 7. **Technology Stack** — table: Component | Technology | Version | Rationale\n> 8. **Non-Functional Requirements** — table: Metric | Target | Measurement\n> 9. **Data Model** — erDiagram or table (if applicable, skip if no data changes)\n> 10. **Observability Strategy** — key metrics, trace spans, structured log fields, alerts\n> 11. **Resilience Strategy** — circuit breakers, retry policies, fallback chains, graceful degradation\n> 12. **Impact Analysis** — affected services, migration steps, rollback strategy, risk assessment\n>\n> **Step 7 — Emit origin marker and save the document (EPIC-0059 — mandatory):**\n>\n> Before writing the artifact, prepend the YAML frontmatter block at the very top:\n>\n> ```yaml\n> ---\n> generated-by: x-plan-architecture@$(git rev-parse HEAD 2>\u002Fdev\u002Fnull || echo \"unknown\")\n> generated-at: $(date -u +%Y-%m-%dT%H:%M:%SZ)\n> story-id: ${STORY_ID}\n> ---\n> ```\n>\n> Then write the full document content after the closing `---`. The frontmatter is required by\n> `audit-execution-integrity.sh` Phase-1 validation (EPIC-0059, Rule 24). Output path:\n> ```\n> ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Farch-story-XXXX-YYYY.md\n> ```\n>\n> **Step 8 — Validate sections post-generation:**\n> - Parse the generated document for all 13 expected sections\n> - For conditional sections (Deployment Diagram, Data Model, Event Schema):\n>   check project capabilities and mark as \"N\u002FA - capability not enabled\" if not applicable\n> - Log section checklist: \"Architecture plan: X\u002FY sections present\"\n> - If any mandatory section is missing, log a WARNING with instruction to complete\n>\n> **Conventions:**\n> - All diagrams MUST use Mermaid syntax\n> - All text MUST be in English\n> - Mini-ADRs follow the inline format (Context\u002FDecision\u002FRationale\u002FConsequences\u002FStory Reference)\n> - Tables use GitHub-flavored Markdown\n> - NFR targets must be measurable (e.g., \"p99 latency \u003C 200ms\", not \"fast\")\n\n## Knowledge Pack References\n\n| # | Knowledge Pack | Path | Purpose |\n|---|----------------|------|---------|\n| 1 | Architecture | `knowledge\u002Farchitecture\u002Farchitecture-principles.md` | Layer structure, dependency direction, package conventions |\n| 2 | Architecture Patterns | `knowledge\u002Farchitecture\u002Farchitecture-patterns.md` | Design patterns, CQRS, event sourcing, saga |\n| 3 | Protocols | `knowledge\u002Fprotocols.md` | REST, gRPC, GraphQL, WebSocket, event-driven conventions |\n| 4 | Security | `knowledge\u002Fsecurity\u002Freferences\u002F` | OWASP Top 10, security headers, secrets management |\n| 5 | Observability | `knowledge\u002Fobservability\u002Freferences\u002F` | Tracing, metrics, logging, health checks |\n| 6 | Infrastructure | `knowledge\u002Finfrastructure.md` | Docker, Kubernetes, 12-factor app |\n| 7 | Resilience | `knowledge\u002Fresilience\u002Freferences\u002F` | Circuit breaker, retry, fallback, bulkhead |\n| 8 | Compliance | `knowledge\u002Fcompliance.md` | GDPR, HIPAA, LGPD (if compliance is active) |\n\n**Minimum KPs for Full Plan:** 7 (all except Compliance, which is conditional).\n**Minimum KPs for Simplified Plan:** 1 (Architecture only; add others as relevant).\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| Story file not found | Abort with \"Story file not found: {path}\" |\n| Template not found | Log WARNING, fall back to inline Output Structure (RULE-012) |\n| Knowledge pack not found | Log WARNING, continue with available KPs |\n| Subagent fails | Abort with error details, suggest manual generation |\n| Post-validation finds missing mandatory section | Log WARNING with instruction to complete the section |\n\n## Integration Notes\n\n| Skill | Relationship | Context |\n|-------|-------------|---------|\n| x-implement-story | Called by | Invoked during Phase 1 for architecture planning; pre-check ensures idempotency |\n| x-model-threats | Complements | Architecture plan feeds threat model generation |\n| x-implement-task | Consumed by | Implementation phase reads architecture plan alongside implementation plan |\n| x-update-architecture | Followed by | After implementation, architecture document is updated incrementally |\n\n## Detailed References\n\nFor in-depth guidance on architecture patterns, consult:\n- `knowledge\u002Farchitecture.md` — full architecture reference\n- `knowledge\u002Fprotocols.md` — protocol conventions\n- `knowledge\u002Fsecurity\u002Findex.md` — security standards\n- `knowledge\u002Fobservability\u002Findex.md` — observability patterns\n- `knowledge\u002Fresilience\u002Findex.md` — resilience patterns\n- `knowledge\u002Finfrastructure.md` — infrastructure patterns\n\n## Planning Status Propagation (Rule 22 \u002F EPIC-0046)\n\n> V2-gated: only runs when `SchemaVersionResolver.resolve(ai\u002Fepics\u002Fepic-XXXX\u002Fexecution-state.json) == V2`. v1 epics: skip silently (Rule 19).\n\nAfter writing `arch-story-XXXX-YYYY.md`, this skill checks the associated story's lifecycle status. The architecture plan does NOT itself drive the `Pendente → Planejada` transition — that is owned by `x-plan-story` (Rule 22 single-writer invariant). If the story is still `Pendente` when the architecture plan is generated standalone (i.e. `x-plan-architecture` invoked directly without `x-plan-story`), transition it to `Planejada` here (idempotent if already `Planejada`).\n\n**Steps (end of architecture-plan generation, BEFORE the final commit):**\n\n1. Detect v2 via SchemaVersionResolver on the epic's `execution-state.json`. If v1: skip.\n2. Read the story's current status via the CLI:\n   ```bash\n   CURRENT=$(java -cp $CLAUDE_PROJECT_DIR\u002Fjava\u002Ftarget\u002Fclasses \\\n       dev.iadev.adapter.inbound.cli.StatusFieldParserCli \\\n       read ai\u002Fepics\u002Fepic-XXXX\u002Fstory-XXXX-YYYY.md)\n   ```\n3. If `CURRENT == \"Pendente\"`, write `Planejada`:\n   ```bash\n   java -cp $CLAUDE_PROJECT_DIR\u002Fjava\u002Ftarget\u002Fclasses \\\n       dev.iadev.adapter.inbound.cli.StatusFieldParserCli \\\n       write ai\u002Fepics\u002Fepic-XXXX\u002Fstory-XXXX-YYYY.md Planejada\n   ```\n   If `CURRENT == \"Planejada\"`: idempotent no-op.\n4. Stage both files and commit via `x-commit-changes`:\n   ```bash\n   git add ai\u002Fepics\u002Fepic-XXXX\u002Fstory-XXXX-YYYY.md ai\u002Fepics\u002Fepic-XXXX\u002Fplans\u002Farch-story-XXXX-YYYY.md\n   ```\n   Then:\n\n       Skill(skill: \"x-commit-changes\", args: \"docs(story-XXXX-YYYY): add architecture plan + update status to Planejada\")\n\n**Fail-loud:** non-zero exit from CLI → abort skill (RULE-046-08).\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","[STORY-ID or feature-name]","medium",true,[],"main","952a630c6f38d193a349d86fa18db1de8843e837","src\u002Ftest\u002Fresources\u002Fgolden\u002Fjava-spring-event-driven\u002F.claude\u002Fskills\u002Fx-plan-architecture",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-architecture",{"tool":44,"command":45},"bunx","bunx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-plan-architecture",{"tool":47,"command":48},"pnpm","pnpm dlx skills add review-bench\u002Federcnj_ia-dev-environment --skill x-plan-architecture","安装技能，技能地址：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-architecture\u002FSKILL.md",[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"README.md","REFERENCE","参考文档",1943,"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-architecture\u002FREADME.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[]]