agentleFS
Sign inStart free
roronoazoroshao369roronoazoroshao369/vibe-coding-os/skills/core/issue-slicing/SKILL.md

issue-slicing

Skill1 starsChanged 5 months agoMITView on GitHub

Break a PRD or plan into small vertical issues that independent agents can grab safely. Use after a PRD, spec, or plan exists and the work is too large for one simple patch. Approved PRD/spec, constraints, dependencies, acceptance criteria, risk areas, and issue tracker conventions. Issue list with scope, owner-ready instructions, dependencies, validation, and done criteria. Creating vague tasks, layer-only slices, hidden dependencies, or issues too large for focused review. Each issue has a clear outcome; dependencies are explicit; tests/checks…

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Use after a PRD, spec, or plan exists and the work is too large for one simple patch.

    line 20
  2. Distinctive:

    Keep each issue independently reviewable and testable.

    line 29
  3. Distinctive:

    Avoid splitting only by technical layer unless necessary.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Skill: Issue Slicing

Purpose

Break a PRD or plan into small vertical issues that independent agents can grab safely.

When to use

Use after a PRD, spec, or plan exists and the work is too large for one simple patch.

Inputs

Approved PRD/spec, constraints, dependencies, acceptance criteria, risk areas, and issue tracker conventions.

Workflow

  1. Identify user-visible vertical slices.
  2. Keep each issue independently reviewable and testable.
  3. Name dependencies and sequencing.
  4. Include acceptance criteria and verification commands.
  5. Avoid splitting only by technical layer unless necessary.

Outputs

Issue list with scope, owner-ready instructions, dependencies, validation, and done criteria.

Failure modes

Creating vague tasks, layer-only slices, hidden dependencies, or issues too large for focused review.

Verification checklist

Each issue has a clear outcome; dependencies are explicit; tests/checks are named; no issue requires unstated context.

Ghi chú tiếng Việt

Issue slicing giúp nhiều agent/person làm việc độc lập. File liên quan: templates/issue-slicing-template.md, commands/vibe-to-issues.md, skills/core/plan-driven-execution/SKILL.md.

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