메뉴
Records architectural decisions with context, alternatives, and consequences using the ADR format. Use when making or reviewing significant design choices that affect multiple modules or packages.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Pipeline for delegating one large mechanical change to a worker under a hard green-or-report gate — specify, dispatch mechanical-refactor-worker, independently re-verify the green claim, hand the working-tree diff to pr-review-reviewer, then commit. Route-only: it does no editing and forms no verdict. Use when delegating a big decision-free change on your own working tree.
Procedure for running multiple independent backlog items in parallel via worktree-isolated subagents with zero merge conflicts — partition file ownership before spawning, isolate each implementer in its own worktree, sequence overlapping work behind occupants, one coherent self-verified PR per agent, and serial orchestrator merge. Use when executing 2 or more independent items concurrently.
Thin router for the doc-vs-code architecture conformance audit (GATE-CONFORMANCE). Routes to the mechanical conformance scan plus the architecture-refresh agent loop (architecture-conformance-auditor / architecture-auditor + fixers), which own the audit behavior natively. Use before a release, after cross-package work, or when GATE-CONFORMANCE runs.
Router for the mandatory post-implementation sequence — SPEC sync, build/test, README, commit/PR, publish, content/ docs, docs deploy. Each step's detail lives in its owning skill/rule; this file only fixes the order and the gates. Execute automatically after implementation work; do not wait for the user to request it.
Orchestrator for the spec document gate pipeline. Reads current status from frontmatter, determines the next gate, invokes backlog-writer or backlog-gate-guard, and updates frontmatter status on PASS. Does nothing else.
Mandatory verification loop after any SPEC.md or contract document change. Compares spec against implementation code, fixes code to match spec, repeats until zero discrepancies, then runs regression tests. Spec is always the source of truth — never modify the spec within this workflow.
| name | architecture-decision-records |
| description | Records architectural decisions with context, alternatives, and consequences using the ADR format. Use when making or reviewing significant design choices that affect multiple modules or packages. |
AGENTS.md > "Development Patterns"AGENTS.md > "Build Requirements"Write one ADR per decision when a design choice affects multiple packages or modules, or has 2+ viable
alternatives with real trade-offs. Accepted ADRs are immutable — supersede with a new ADR, never
edit. Section presence + Status values are mechanically enforced by
scripts/harness/check-adr-completeness.mjs; this skill owns the template.
.design/decisions/ADR-NNN-short-title.md (e.g., ADR-001-runtime-event-prefix-system.md)proposed, accepted, superseded, deprecated, rejected# ADR-NNN: Short Title
## Status
accepted | superseded by ADR-NNN | rejected
## Context
What is the problem or question? Why does it need a decision now?
## Alternatives Considered
1. **Option A**: description — pros / cons
2. **Option B**: description — pros / cons
## Decision
Which option was chosen and why.
## Consequences
- What becomes easier or possible.
- What becomes harder or impossible.
- What follow-up work is needed.
## References
- Related ADRs, specs, or rule anchors.