A Claude Code plugin marketplace bringing proven software engineering practices into agentic development — starting with architecture decision records and use case specifications.
Status: early alpha. The plugin is in active use on real projects; expect the details to move.
Architecture decision records and use case specifications are expensive. On most teams they lose against the backlog, and the reasoning behind a system evaporates.
Agents change the cost side: the agent conducts the interview, drafts the document, and keeps it consistent; the human makes the decisions. ADLC packages this as Claude Code skills built on established formats — MADR for decision records, fully-dressed use cases after Cockburn's Writing Effective Use Cases — instead of inventing new ones. Everything produced is plain markdown that a team can read, review, and maintain without any AI in the loop.
The skills are event-driven, not phase-locked: they fire when something happens, at any point in the life-cycle, and re-fire on change — as a revision, never a regeneration.
| Stage | Component | Fires when… |
|---|---|---|
| specify | /adlc:use-case |
a user goal enters or changes — "let's spec a new feature" |
| decide | /adlc:adr |
a decision about how the system is built or structured is being made |
| build | your practices | — |
| verify | check-docs.py |
locally and in CI, over the produced documents |
The use-case skill interviews you and writes one specification per goal; if the spec exists, it proposes a revision diff. The ADR skill's gatekeeper keeps non-architectural decisions out and routes them where they belong; it also catches decisions surfacing inside other skills' work (e.g. an architecture analysis during feature development) — ADLC composes with such skills rather than replacing them. Skills trigger automatically when the conversation matches their description, and can always be invoked explicitly by name.
/plugin marketplace add wuersch/adlc # or a local path during development
/plugin install adlc@adlc-marketplace
To pin a project to a released version (e.g. for CI), add the marketplace at a tag:
/plugin marketplace add wuersch/adlc@v0.1.0
- Textbook first, customize later. Established formats, cited; no house dialects.
- The human decides; the agent drafts and interviews. Documents record your reasoning, not the model's guesses — open points are marked, never papered over.
- Plain artifacts. Everything produced is ordinary markdown with no tool lock-in.
- Respect existing conventions. In a repo that already has an ADR directory or spec layout, the skills detect and follow it; defaults apply only in fresh projects.
- Checks over exhortations. Rules that can be verified mechanically are enforced by a script, not by prose.