x-plan-arch-capability
Generate C4 Container + Component diagrams for a capability in Mermaid or PlantUML.
- License 许可
- MIT
- 最近更新
- 2026-10-27
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- x-plan-arch-capability
- model
- opus
- description
- Generate C4 Container + Component diagrams for a capability in Mermaid or PlantUML.
- allowed-tools
- Read, Write, Bash
- argument-hint
- --capability-id <ID> [--output-format mermaid|plantuml]
- context-budget
- light
- user-invocable
- true
- requires-capabilities
- []
03 SKILL.md 正文
Output Policy
- Language: Portuguese (pt-BR) for content. English for technical terms and code identifiers.
- Tone: Technical, Direct, and Concise.
Skill: x-plan-arch-capability
Purpose
Generate C4 architecture diagrams (Context, Container, Component levels) for a Capability artifact. Diagrams are written in Mermaid (default) or PlantUML. Placeholder diagrams are generated when structural information is sparse.
When to Use
- After
x-create-capabilitycreates the capability artifact - When planning architectural boundaries for a specific capability area
- Before feature decomposition — establishes technical context
CLI Command
ia-dev-env x-plan-arch-capability --capability-id capability-0001
ia-dev-env x-plan-arch-capability --capability-id capability-0001 --output-format plantuml
Triggers
/x-plan-arch-capability --capability-id <ID>/x-plan-arch-capability --capability-id <ID> --output-format plantuml
Arguments
| Flag | Required | Description |
|---|---|---|
--capability-id |
yes | Capability identifier (e.g. capability-0001) |
--output-format |
no | mermaid (default) or plantuml |
Output
Produces C4 diagram blocks printed to stdout:
CONTEXT— System context diagramCONTAINER— Container diagramCOMPONENT— Component diagram
Each entry is marked OK or [placeholder].
Exit Codes
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | Validation error |
| 2 | Execution error |
Examples
ia-dev-env x-plan-arch-capability --capability-id capability-0001
ia-dev-env x-plan-arch-capability --capability-id capability-auth --output-format plantuml
Related Skills
| Skill | Relationship |
|---|---|
x-plan-arch-product |
Product-level C4 — run before this |
x-plan-arch-feature |
Feature-level C4 — run after this |
x-create-capability |
Creates the capability artifact consumed here |
References
04 同仓库更多 Skills
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 / x-story-plan, applies the parallelism-heuristics knowledge pack (hard / regen / soft categories + hotspot overrides), and emits a collision matrix + serialization recommendation in Markdown (default) or JSON.
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 / regen / 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.
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.
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/auto-detected from ProjectConfig.documentation.targets. Returns exit non-zero on staleness; produces structured report.
x-update-system-architecture
Incrementally updates docs/architecture/system.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/integration changes into sections 1-10 via Edit. Idempotent: re-running with the same epic produces a byte-identical system.md.
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.