CtrlK
BlogDocsLog inGet started
Tessl Logo

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 Toolkit

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-structured and actionable, with a clear sequenced workflow, concrete quantified guidance, and proper use of a one-level reference file. Its main weakness is mild redundancy between the overview list, the when-to-use section, and the workflow/frontmatter.

Suggestions

Remove or merge the 'What is covered in this Skill?' list into the Workflow section, since it restates the same steps.

Trim the 'When to use this skill' section to avoid duplicating the trigger phrases already in the frontmatter description.

DimensionReasoningScore

Conciseness

The body avoids concept over-explanation and delegates detail to a reference file, but the 'What is covered in this Skill?' list restates the workflow and 'When to use' duplicates the frontmatter triggers, so it could be tightened.

2 / 3

Actionability

Provides concrete, quantified guidance ('Identify 3-6 functional or workflow layers', 'generate 4-5 implementation or quality options ordered from the simplest acceptable choice to richer choices') plus explicit MUST/MUST NOT constraints, which is fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

A clear 6-step sequenced workflow culminates in an explicit self-check checklist (value, size, testability, deliverability, issue-tracking suitability); no error-recovery loop is required for a low-risk planning skill per the scoring notes.

3 / 3

Progressive Disclosure

The body is an overview that points to a single, clearly signaled, one-level-deep reference (references/052-design-hamburger-method.md, which exists) with well-organized sections, matching the clear-navigation anchor.

3 / 3

Total

11

/

12

Passed

Description

92%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states concrete actions, surfaces natural trigger phrases, and explicitly covers both what and when. Its only weakness is that several triggers are generic story-splitting language that may overlap with sibling planning skills.

Suggestions

Tie the generic triggers more tightly to the Hamburger Method (e.g., 'Split this oversized story with the Hamburger Method') to reduce overlap with sibling planning skills 041-045.

Drop or scope 'Part of Plinth Toolkit' so it does not dilute the distinctiveness signal for routing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions such as 'split into small vertical slices', 'Find the smallest useful slice', and 'Break this feature into vertical slices', matching the comprehensive-actions anchor rather than the partial score-2 anchor.

3 / 3

Completeness

Explicitly states what the skill does ('split into small vertical slices with the Hamburger Method') and when to use it ('Use when a large feature, story, plan, or spec idea needs to be split' plus a trigger list), satisfying both what and when.

3 / 3

Trigger Term Quality

Includes natural user phrasings verbatim ('Split this oversized story', 'Apply the Hamburger Method', 'Turn this broad plan into tracked slices'), giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

The named 'Hamburger Method' gives a niche, but generic triggers like 'Split this oversized story' and 'Find the smallest useful slice' overlap with the toolkit's other planning skills, so it could still trigger the wrong skill.

2 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/plinth
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.