audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
Architecture decision records: durable decisions with their date, context, and consequences — supersede, never rewrite.
> /plugin marketplace add azrtydxb/procoder > /plugin install procoder@procoder
How it fires
How this command gets triggered: by you, by Claude, or both.
/adrContext preview
What this command does when you run it.
Architecture decision records: durable decisions with their date, context, and consequences — supersede, never rewrite.
description: "Architecture decision records: durable decisions with their date, context, and consequences — supersede, never rewrite."
The user invoked /procoder:adr with arguments: $ARGUMENTS
The launcher is: "${CLAUDE_PLUGIN_ROOT}/hooks/launcher.sh"
An ADR captures a cross-cutting decision at the moment it is made, so the constraint that forced it survives the people and chats that knew it. Records are immutable: a changed mind writes a NEW record and marks the old one superseded.
write it and fill Context (what forced this), Decision (what we chose and why over the alternatives), and Consequences (what gets easier and what gets harder). Then bring the status to accepted with the user's agreement — deciding is theirs.
and supersede references pointing nowhere. Fix what it names.
Record an ADR whenever a decision would surprise a newcomer or took real debate: a dependency chosen, a boundary drawn, a ceiling accepted. With arguments, run the matching subcommand; without, run `list` and report.
Senior-developer discipline for AI coding agents. A commit gate that counts unchecked as failing, quality controllers that refuse to call unfinished work done, and a lessons loop that closes each escaped bug's class. One Go binary, no runtime deps, works with 20+ agents.
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
Run the formatting gate over the changed files, as a commit or CI would.
CI/CD hygiene and run health: pinned actions, timeouts, concurrency, tests — plus the latest runs via gh.
Copilot's auto-review escapes: find them since the last look, sanitise them, and turn each one into a lesson.
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the…