agentleFS
Sign inStart free
int2t05int2t05/engineering-skills/skills/04-develop/breakdown/SKILL.md

breakdown

Skill3 starsChanged 28 days agoMITView on GitHub

Turn agreed requirements into executable dependency-aware tasks. Triggers on "break into tickets", "拆解任务".

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ship.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read scope, design, current implementation and acceptance criteria.

    line 16
  2. Distinctive:

    Create tasks around observable outcomes or necessary structural steps.

    line 18
  3. Distinctive:

    Use available planning facilities or an inline plan.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Breakdown

When to use

  • Turn agreed requirements into executable dependency-aware tasks.

Not for: spec for defining scope; multi-agent-orchestration for execution.

Steps

  1. Read scope, design, current implementation and acceptance criteria.
  2. Create tasks around observable outcomes or necessary structural steps.
  3. Specify inputs, deliverables, dependencies, risks and concrete checks; identify critical path and safe parallelism.
  4. Use available planning facilities or an inline plan; create PLAN only when persistent coordination is useful and the path is agreed.

Output: Suggested paths, subject to human audit: docs/PLAN.md; optionally docs/vX.Y/plan.md for separate release planning.

Verify

  • Tasks cover acceptance without speculative additions; dependencies are acyclic and checks are concrete.

References

  • engineering-principles.md — shared decision boundaries, scope and verification.
  • human-audit.md — document consent, readability and human review.
  • references/ticket-format.md — local-ticket and issue templates, the staleness rule, and ticket-type routing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free