adr
Architecture decision records: durable decisions with their date, context, and consequences — supersede, never rewrite.
Scope-boxed sprints over the backlog: one active sprint, explicit carry-over, a close that refuses to hide unfinished work.
> /plugin marketplace add azrtydxb/procoder > /plugin install procoder@procoder
How it fires
How this command gets triggered: by you, by Claude, or both.
/sprintContext preview
What this command does when you run it.
Scope-boxed sprints over the backlog: one active sprint, explicit carry-over, a close that refuses to hide unfinished work.
description: "Scope-boxed sprints over the backlog: one active sprint, explicit carry-over, a close that refuses to hide unfinished work."
The user invoked /procoder:sprint with arguments: $ARGUMENTS
The launcher is: "${CLAUDE_PLUGIN_ROOT}/hooks/launcher.sh"
A sprint is a commitment, not a calendar: a goal plus the stories pulled into it, opened and closed explicitly. One sprint is active at a time — that is the WIP limit, and the point.
otherwise prints the sprint file for you to write. State a real goal: what this sprint delivers, not a date range.
active sprint. Done, missing, or already-committed stories are refused individually; the rest still pull.
done/total and carried counts. Run it before claiming progress.
story to the backlog, with the reason recorded in the story file. Lean makes unfinished work visible; carrying without a reason is refused.
neither done nor carried. Finish it (`backlog close story <id>`) or carry it with a reason, then close; the sprint file gets a Result section with committed/done/carried counts and a Retro scaffold.
one adaptation worth keeping. The retro is the price of the next sprint: `sprint open` refuses while the last one's Retro is empty (`[sprint] retro = "off"` opts a repo out).
With arguments, run the matching subcommand and act on its output. Without arguments, run `status` and report where the sprint stands.
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.
Architecture decision records: durable decisions with their date, context, and consequences — supersede, never rewrite.
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.