메뉴
Manage Architecture Decision Records using the project's ADR CLI tool. Use when the user wants to create, list, view, lint, or index ADRs, or when working with docs/architecture/ files. Triggers on "create an ADR", "new ADR", "list ADRs", "lint ADRs", "what ADRs exist", "ADR domains".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Score way matching (embedding and BM25), analyze vocabulary, and validate frontmatter. Use when testing how well a way matches prompts, checking cosine similarity or BM25 scores, inspecting the embedding engine status, or validating way files.
Check how much context window remains in this session. Use when you want to know token budget, context usage, or how much room is left before compaction. Also use proactively when working on long tasks to gauge remaining capacity.
Cite governance controls and justifications when making recommendations about code quality, security, commits, or documentation. Use when justifying why a practice matters, when a user asks "why do we do this?", when reviewing code against standards, or when recommending practices that align with NIST, OWASP, ISO, SOC 2, CIS, or IEEE controls.
Ship current work through the branch → commit → push → PR → merge → cleanup flow. Picks up wherever you are in the cycle. Use when the user says "ship it", "land this", "merge this", or invokes /ship.
Review what changed in Claude Code upstream and compare against this project's commits and ADRs. Surfaces opportunities, gaps, and ADR status drift. Discovery conversation, not compliance dashboard.
Strategy selector for structured reasoning. Lists available thinking frameworks and invokes the right one. Use when facing complex decisions, trade-offs, or when stuck.
| name | adr |
| description | Manage Architecture Decision Records using the project's ADR CLI tool. Use when the user wants to create, list, view, lint, or index ADRs, or when working with docs/architecture/ files. Triggers on "create an ADR", "new ADR", "list ADRs", "lint ADRs", "what ADRs exist", "ADR domains". |
| allowed-tools | Bash, Read, Grep, Glob |
Operate ADRs through the docs/scripts/adr CLI tool. Never create ADR files manually.
# Discover
docs/scripts/adr domains # Show domain number series and ranges
docs/scripts/adr list --group # List all ADRs grouped by domain
docs/scripts/adr list --domain system # Filter to one domain
docs/scripts/adr list --status Accepted # Filter by status
docs/scripts/adr view <number> # View an ADR (accepts 14, 014, ADR-014)
# Create
docs/scripts/adr new <domain> "Title" # Create from template in correct subdirectory
# Maintain
docs/scripts/adr lint # Check all ADRs for issues
docs/scripts/adr lint --check # Exit 1 on errors (CI mode)
docs/scripts/adr index -y # Regenerate INDEX.md
# Config
docs/scripts/adr config # Show current adr.yaml configuration
docs/scripts/adr domains to see available domains and number rangesdocs/scripts/adr new <domain> "Decision Title" — assigns next number, uses YAML frontmatter templatedocs/scripts/adr lint before committingdocs/scripts/adr index -y after adding or changing ADRsEach project defines its domain structure in docs/architecture/adr.yaml:
Always run docs/scripts/adr domains to discover the project's actual configuration rather than assuming domains.
The tool generates ADRs with YAML frontmatter:
---
status: Draft
date: 2026-02-17
deciders:
- aaronsb
- claude
related: []
---
# ADR-NNN: Decision Title
## Context
## Decision
## Consequences
### Positive
### Negative
### Neutral
## Alternatives Considered
ADR-*.md files by handdomains first when working in an unfamiliar project — domain names and ranges varystatus: field, not inline textdocs/scripts/adr index -y