askrubberduck

Skills

20 in the Claude listing

• Duck breakTry to break a system's claimed behavior, then show what actually happened.
• Duck campaignCarve a grand vision into independent workstreams that ship without waiting on each other.
• Duck cutShrink a backlog the honest way — obsolete work out, duplicates merged, viable items unblocked.
• Duck decideWalk the owner through the decisions they have been ducking, one at a time.
• Duck dietPut agent context, memory, and token costs on a diet without starving the essential guidance.
• Duck dryStrip comments, docstrings, commit messages, and PR descriptions until only unobvious decisions, contracts, and traps survive.
• Duck frameSettle a system's target design before planning begins, because 'we'll figure out the architecture later' means never.
• Duck landMerge approved work, run a described release process when asked, update project records, and clean up the branch and worktree; landed means nothing left behind.
• Duck learnTurn session and delivery evidence into reusable lessons, so each mistake is only paid for once.
• Duck planFind the hole in the plan before building over it; assumptions and acceptance checks must survive challenge.
• Duck proofMake the goal, the path, and the finished work earn your trust through counterexamples and executed checks.
• Duck racePut two different model families on the same problem and let executed evidence pick the result.
• Duck reviewReview work from multiple angles or deliver an independent judgment.
• Duck roastRoast the whole solution until its weak claims show; a finding must earn its place, and a round must end.
• Duck runChallenge the goal, shape the plan, build it, and make it prove itself; local means local.
• Duck scanFind ready, blocked, and remaining work without changing anything; looking is free.
• Duck shapeMake every layer earn its place; cut the machinery the problem never asked for.
• Duck splitHold a branch, PR or document to the one thing it was opened for; nothing rides along, nothing falls off.
• Duck sweepClean out stale branches, worktrees, checkouts, scratch directories, and ignore rules; the pond stays clean.
• Duck whyName the cause of a failure before anyone writes a fix, because the symptom is not the defect.