AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Breakdown

skill-dtiger1889-ops-claude-harness-toolbox-breakdown · by dtiger1889-ops

Convergent, action-first problem decomposition (the terse twin of /fanout). Use ONLY when the user types /breakdown or says "break this down" / "break it down" / "decompose this". Takes ONE tangled or ambiguous problem and returns the single smallest next ACTION plus a collapsed full plan. Terse, no hand-holding, no capability narration. Do NOT use for open-ended ideation with many valid answers…

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-dtiger1889-ops-claude-harness-toolbox-breakdown

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-dtiger1889-ops-claude-harness-toolbox-breakdown)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Breakdown? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

breakdown -- convergent, action-first decomposition

The convergent complement to /fanout. /fanout opens a problem up (many valid answers); /breakdown closes one down (one tangle -> one next step). Single-shot, no sub-agents, ~1x cost. Grounded in the maintainer's session-transcript crawl: the loudest friction was "stop explaining, just do it," so this skill is ACTION-FIRST and minimal-prose by design. If your output reads like a gentle walk-through, it is wrong -- cut it.

Step 1 -- get the tangle

Accept the problem from an @-mention, a path, or pasted text. If it is genuinely vague, ask for one or two sentences -- once. Read any referenced file to EOF before decomposing. If the tangle is (or names) a project artifact, ALSO read that project's CHECKPOINT.md to EOF first (receipt/preview is not a read) -- the "real goal" and the "blocking decision" depend on live project state (deadlines, sequencing gates, what's already decided), and a decomposition blind to it points at the wrong next action. Skip only if genuinely project-free.

Step 2 -- output exactly these five blocks, tersely, in order

No preamble. No "I have access to...". Do not restate the question back at length.

  1. Real goal (one sentence). What "done" actually means. If the stated goal differs

from the real one, say so in one line.

  1. Smallest next action (one concrete, physical step doable in one sitting -- e.g.

"open X and write the three field names," not "design the schema"). Then OFFER to just do it now. Do not explain at length first.

  1. The one blocking decision -- the single fork that unlocks the most, or

"none -- just start."

  1. Full plan (collapsed) -- the complete checklist under a one-line summary, explicitly

de-emphasized: "ignore until step 2 is done."

  1. First trap -- the single most likely failure mode and its earliest signal.

Rules

  • One thread on the critical path. Do not list parallel workstreams.
  • Plain language, no invented codes (translate any filing tags to people-words).
  • Do NOT start the work until the user picks. /breakdown plans; it does not execute.
  • Persist nothing by default. If worth keeping, offer to write it into the project's

CHECKPOINT "Next step" line.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.