Claude Skills by blakemartz

Author a decompose-ready sub-spec for one subsystem — collect operator pins, ground against code and primary sources, draft to the house template, land it through adversarial docs-review, then hand off to /decompose. Two hard human gates (draft nod before the PR, backlog approval inside /decompose). e.g. "/author-spec object storage".

Author or evolve the repo's styleguides — the conventions in STYLEGUIDES_DIR that decompose fits tasks to, implementers follow, and reviewers enforce. Detects the stack, observes existing conventions, pins contested choices with the human, drafts, and lands nothing until the human ratifies. Re-runnable as stacks are added. e.g. "/author-styleguides" or "/author-styleguides python".

Destructure a repo's specs into a dependency-ordered backlog of epics and tasks as GitHub Issues. Dry-run by default; pass --create only after a human approves the printed backlog. Optional scope arg, e.g. "/decompose backend api loop".

Drive one READY task end-to-end — implement in a worktree, independent adversarial review, bounded 3-iteration patch loop, then hand to a human for merge. Pass the issue number, e.g. "/deliver-task 42". A single-command composition of next-task + review-task + patch-task.

One orchestrator tick of the agentic delivery loop - reconcile the board, then take exactly ONE state-advancing action (patch a rejected PR, review an unreviewed PR, or start the next ready task) — or, with "--parallel N", up to N independent actions concurrently. With --auto-merge (opt-in, off by default) it first squash-merges any fully-approved, mergeable, green PR. Designed as the /loop target.

Bootstrap the delivery loop in the current repo — create/connect the GitHub repo if needed, create the label taxonomy, scaffold .claude/delivery.conf, seed the gate and styleguides stub, gitignore .worktrees/. Run once per repo. Idempotent.

Claim the next ready task off the GitHub Issues queue (or a specific one, e.g. "/next-task 42"), implement it in an isolated worktree to its acceptance criteria, pass the gate, and open a PR. The implementer role of the agentic delivery loop.

Respond to review findings or failing CI on an existing agent PR, e.g. "/patch-task 17" (PR number). Bounded to 3 iterations, then escalates to a human. The patcher role of the agentic delivery loop.

Adversarially review a PR against its linked task's acceptance criteria and the styleguides, e.g. "/review-task 17" (PR number). Executes every criterion in a clean checkout. The independent reviewer role of the agentic delivery loop.

Render the delivery board — ready / claimed / in-review / changes-requested / approved / blocked / needs-human — from GitHub Issues and PRs. Pass --reclaim to also reconcile labels and release stale agent claims.