barrydobson-skills

Plugin barrydobson-skills from marketplace barrydobson in barrydobson/skills. Commands read from the repo's manifest — today.

Skills (20)

• be-ambitious

  Makes a task or prompt more ambitious using Felix Rieseberg's types of ambition, Altitude (aim at the outcome, the goal beyond the goal), Depth (work like the best expert in the field, from the raw data, checked by an outside judge) and Range (bring in other fields and do what their experts do). Wri

• blast-radius

  Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.

• correct

  Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /cor

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• file-pr

  File a concise pull request with a problem-first body, evidence and merge risk. Use when the user asks to file, open, raise or create a PR, or to write a PR title or body.

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

• handoff

  Compact the current conversation into a handoff document for another agent to pick up.

• leaving-pr-comments

  Use whenever leaving comments on GitHub.

• personal-brand

  Applies Barry Dobson's personal colours (the Voltaic palette, dark and light) and fonts (Clash Display, Clash Grotesk, Geist, JetBrains Mono) when creating a document, web page, slide deck, dashboard, chart, diagram or other visual output for Barry personally. Use when the user asks for "my brand",

• retro

  Conduct a retrospective on a coding session.

• reviewing-plugins

  Reviews Claude Code skills, plugins and plugin marketplaces against current Anthropic guidance, then reports ranked, concrete recommendations and offers to apply them. Covers SKILL.md frontmatter and descriptions, invocation control, context cost, progressive disclosure, plugin.json, agents, hooks,

• setup-matt-pocock-skills

  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

• technical-docs

  Write reader-facing prose in the style of the Google Developer Documentation Style Guide. Name a document to write and it dispatches the technical-writer agent.

• to-spec

  Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

• to-tickets

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

• triage

  Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

• unslop

  Cut AI tells from any writing.

• wizard

  Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can pe

• work-hc

  How /tote-issue-tracker:work delegates when the session runs inside herdr-core ($HC_TERMINAL_ID set) - each ticket's implementer and reviewer run as hc terminals the human can watch and steer. Use when /work reaches implementation or review inside Herdr. Not for /work outside Herdr, which implements

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Subagents (2)

• codebase-analyzer

  Analyzes codebase implementation details — traces data flow, explains how components work, and documents logic with precise file:line references. The more detailed the request prompt, the better the output.

• technical-writer

  Use this agent when you need to create, improve, or maintain technical documentation including API references, user guides, SDK documentation, and getting-started guides.

Similar plugins