メニュー
Detect violations of architectural decisions in the codebase. Checks module dependency direction rules, identifies boundary violations, and reports drift between documented decisions and actual code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Validate that a pull request follows principled conventions: references a plan or proposal, has correct labels, includes required sections in the description, and links to relevant documents. Use in CI or before merging to enforce PR quality.
Generate a structured pull request description from a DDD plan task. Reads the plan, task manifest, and implementation branch to produce a PR body with references to the originating proposal, plan, ADRs, and related tasks. Use when opening a PR for plan-driven work.
Process open GitHub issues through the principled pipeline. Lists untriaged issues, normalizes their metadata, ingests them into the documentation pipeline, and reports a summary. Operates as the batch entry point — delegates to /ingest-issue for each individual issue.
Implementation orchestration strategy for the Principled framework. Consult when working with DDD plan execution, git worktrees for task isolation, task manifests, or the decompose-spawn-validate-merge lifecycle. Covers worktree management, sub-agent patterns, task state machines, and manifest schema.
Top-level orchestrator for DDD plan execution. Decomposes a plan into tasks, iterates through phases respecting dependencies, spawns worktree-isolated agents, validates implementations, and merges results. Runs inline to coordinate multiple sub-agent spawns. Use for automated end-to-end plan execution.
Audit ADR coverage across modules. Identifies modules with no architectural governance, orphaned ADRs referencing removed modules, and stale architecture docs. Classifies findings by severity.
| name | arch-drift |
| description | Detect violations of architectural decisions in the codebase. Checks module dependency direction rules, identifies boundary violations, and reports drift between documented decisions and actual code. |
| allowed-tools | Read, Bash(git *), Bash(ls *), Bash(bash plugins/*) |
| user-invocable | true |
Detect whether the codebase conforms to documented architectural decisions. Checks dependency direction rules, identifies module boundary violations, and reports drift with references to governing ADRs.
/arch-drift [--module <path>] [--strict]
| Argument | Required | Description |
|---|---|---|
--module <path> | No | Scope analysis to a single module. Checks all modules if omitted. |
--strict | No | Exit non-zero on any error-severity violation. For CI use. |
Scan modules. Discover all modules:
bash ../arch-map/scripts/scan-modules.sh [--module <path>]
Read accepted ADRs. For each ADR in docs/decisions/ with status accepted:
Check dependency direction. For each module, run the boundary checker:
bash scripts/check-boundaries.sh --module <path> --type <type>
This scans source files for import statements and checks them against the dependency direction rules:
| Module Type | Can Depend On | Cannot Depend On |
|---|---|---|
app | lib, core | other app |
lib | core | app, lib* |
core | (none internal) | app, lib |
*Cross-lib dependencies are allowed if explicitly declared in the module's CLAUDE.md ## Dependencies section.
Classify findings. Each violation is classified by severity:
core importing from app)Reference governing ADRs. For each violation, identify which ADR established the rule being violated and include the reference in the report.
Report results. Output a structured report:
Architecture drift analysis:
Modules checked: 8
Violations found: 3
Errors: 1
Warnings: 2
ERROR: packages/core/src/utils.ts:15
Imports from packages/api (app) — core cannot depend on app
Governing ADR: ADR-014 (Heuristic Architecture Governance)
WARNING: packages/auth-lib/src/client.ts:42
Imports from packages/shared-lib (lib) — lib-to-lib not declared
Declare in CLAUDE.md ## Dependencies to allow
Strict mode. If --strict is specified and any error-severity violations exist, report failure. This enables CI integration.
scripts/check-boundaries.sh --- Scan source files for import violations against dependency direction rules