agentsclimarketplace

052 design hamburger method

Skill jabrena/plinth/skills/052-design-hamburger-method

Use when a large feature, story, plan, or spec idea needs to be split into small vertical slices with the Hamburger Method. This should trigger for requests such as Split this oversized story; Find the smallest useful slice; Break this feature into vertical slices; Apply the Hamburger Method; Turn this broad plan into tracked slices. Part of Plinth ToolkitFrom its SKILL.md

Install
npx -y skills add jabrena/plinth --skill 052-design-hamburger-method

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.0 KB, as published. Nobody here has run it

Hamburger Method Design

Guide Java teams through the Hamburger Method for splitting oversized work into small, valuable, end-to-end vertical slices. This is an interactive SKILL.

What is covered in this Skill?

  • Recognizing oversized feature, story, plan, or spec work
  • Identifying 3-6 functional or workflow layers that participate in delivering value
  • Generating 4-5 implementation or quality options per layer
  • Challenging scope with the smallest useful version question
  • Filtering options that are too costly, redundant, irreversible, or unnecessary for early learning
  • Composing one first vertical slice and follow-up slices
  • Self-checking value, size, testability, deliverability, and issue-tracking suitability
  • Routing plan, OpenSpec, GitHub issue, and Jira follow-up through the existing planning skills

Constraints

Split oversized work into vertical slices that deliver observable value, not isolated horizontal technical tasks.

  • MUST read references/052-design-hamburger-method.md before applying the method
  • MUST identify 3-6 functional or workflow layers before selecting a slice
  • MUST generate 4-5 options per layer, ordered from simplest acceptable option to richer options
  • MUST challenge scope with the smallest-useful-version question before recommending a first slice
  • MUST filter costly, redundant, irreversible, or unnecessary options before composing the first slice
  • MUST keep recommended work as vertical slices that deliver observable value
  • MUST NOT present isolated technical layers as independently shippable stories

When to use this skill

  • Apply the Hamburger Method
  • Split this oversized story
  • Find the smallest useful slice
  • Break this feature into vertical slices
  • Turn this broad plan into tracked slices
  • This feature is too large

Workflow

  1. Recognize Oversized Work

Read references/052-design-hamburger-method.md, then restate the large feature, story, plan, or spec idea and why ordinary implementation task decomposition would be too broad, risky, or horizontal.

  1. Map Layers and Options

Identify 3-6 functional or workflow layers needed for observable value. For each layer, generate 4-5 implementation or quality options ordered from the simplest acceptable choice to richer choices.

  1. Challenge Scope

Ask: "If this had to ship tomorrow, what would be the smallest useful version?" Use the answer to remove options that are too costly, redundant, irreversible, or unnecessary for early learning.

  1. Compose the First Slice

Select one option from each relevant layer to create the smallest useful end-to-end vertical slice. Explain the user-visible value, validation signal, and why rejected layer options wait for later slices.

  1. Plan Follow-Up Slices

Propose follow-up vertical slices that incrementally improve quality, automation, robustness, reach, observability, operational behavior, or supported workflows without turning them into isolated technical layers.

  1. Self-Check and Route Follow-Up

Check every slice for value, size, testability, deliverability, and issue-tracking suitability. Route implementation planning through 041-planning-plan-mode, spec-level changes through 042-planning-openspec, GitHub issue work through 043-planning-github-issues, Jira work through 044-planning-jira, and Azure DevOps work through 045-planning-azure-devops.

Reference

For detailed guidance, examples, and constraints, see references/052-design-hamburger-method.md.

What ships with it: 1 file

10.0 KB alongside SKILL.md

Gives 0 of the 12 instructions most plan spec skills give

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 73 of 1360
  • Write the spec using the templatein 22 of 1360
  • Ask clarifying questions if neededin 19 of 1360, across 18 files
  • Wait for user confirmation before proceedingin 19 of 1360
  • Save plans to the plans directoryin 17 of 1360, across 13 files
  • Check for product marketing context firstin 16 of 1360, across 5 files
  • Read the plan file completelyin 16 of 1360
  • Order tasks by dependencyin 16 of 1360
  • Gather context from the conversationin 15 of 1360, across 9 files
  • Explore the codebase instead of askingin 15 of 1360, across 13 files
  • Wait for explicit user approvalin 14 of 1360, across 13 files
  • Quiz the user on the breakdownin 13 of 1360, across 7 files

Said here and by no other author read

  • Identify functional or workflow layers
  • Generate implementation options per layer
  • Challenge scope with the smallest useful version question
  • Filter costly or unnecessary options
  • Compose the first vertical slice
  • Propose follow-up vertical slices

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 613,297. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.