scott-skills
claudeScott's end-to-end workflow for Claude Code: set an effort's destination, principles, and high-level design once with /wayfinder, then let agents build it on their own — a plan of pieces on your tracker, only the risks that could sink it proved first, every ready piece built in parallel and verified on two axes, every decision citing its grounds and cross-read each round so bad calls are corrected before they compound — or spec a feature yourself and run it through /specify, /spec-review, /tickets and /ship with /next, or grow a feature a slice at a time with /iterate, decisions made just in time against an effort log in the repo and the next effort's idea parked as a ticket by /seed, client feedback turned into an effort by /triage — every review gate on the finding-pipeline contract, every spawned agent on a policy-resolved model tier, every test run scoped to the change by the repo's TESTING.md — plus standalone skills for grilling, design, domain modeling, prototyping, research, TDD, wizards, verification skills that drive each app the way a user does, writing for agents, Herdr and Rex hand-offs and side panes, cold-reading the docs agents have worn, /tend to keep the repo's CONVENTIONS, TESTING, PRINCIPLES, CONTEXT and ADR docs on purpose as each change lands, a /snag → /autopsy loop that traces friction in past sessions back to the skill text that caused it and replays it as an eval, /rsi, which grades recent sessions from every local coding agent and files the failures these skills caused as snags for that loop, /evals to A/B any skill edit against the text before it, and /maintain-iterate, which tunes the /iterate loop from its own runs.
40 skills · hooks