Adr
Enterprise engineering workflow for Claude Code — not just prompts. AI agents that plan, build, audit, and ship with security gates, privacy checks, and approval-controlled commits. Safely adopt it into new or existing repositories.
npx -y skills add byerlikaya/claude-starter-kit --skill adrAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 20 stars20 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Architecture Decision Record: context-decision-consequences, for decisions that are expensive to reverse. Written under docs/adr/. Trigger phrases: "adr", "architecture decision", "decision record", "why this approach"
SKILL.md
1.1 KB, as published. Nobody here has run it
Architecture Decision Record (ADR)
When
On an architecture/technology choice that is expensive to reverse, long-lived, or contested (database selection, auth strategy, critical pattern). Small/reversible decisions do not require an ADR.
Format (docs/adr/NNNN-short-title.md, ~1 page)
# NNNN. <Decision title>
Status: proposed | accepted | rejected | superseded (by NNNN)
## Context
Which problem/constraint requires this decision?
## Decision
What was decided (clear, one sentence + rationale)?
## Consequences
Pros / cons / accepted trade-offs.
## Alternatives considered
Why were they not chosen?
Principles
- Invariant: a new decision marks the old ADR as
superseded; an ADR is never deleted (decision history is preserved). - Numbered and dated; keep it short.
DoD
- Decision + rationale + rejected alternatives recorded; status current.