vertical-slice-delivery

Original：🇺🇸 English
Translated

Required methodology for planning, ideating, and delivering features or tasks. Use when user asks to "plan", "break down", "continue", or "figure out steps".

1installs
Sourcejjenzz/agent-skills
Added on

NPX Install

npx skill4agent add jjenzz/agent-skills vertical-slice-delivery

Tags

Translated version includes tags in frontmatter
vertical-slice-deliveryproject-planningtask-breakdowngit-disciplinecode-review

SKILL.md Content

View Translation Comparison →

Vertical Slice Delivery

This skill defines the default delivery methodology for planning and shipping work as independently valuable, reviewable vertical slices.
txt
Skateboard → Scooter → Bicycle → Motorcycle → Car
Load and obey its 
AGENTS.md
that lives next to this 
SKILL.md
.

When to Apply

Use this skill whenever work is being:
  • planned
  • split into tasks or steps
  • delivered incrementally
  • resumed after interruption
Any deviation from vertical slice delivery MUST be explicit and justified.

Core Loop

Each slice = one commit + one review. No slice begins until the previous is approved.
  1. IMPLEMENT — one behavioral slice only
  2. COMMIT — with slice ID and conventional message 
    feat(scope): [S1] description
  3. STOP — mandatory review (do not proceed)
  4. WAIT — approved → next slice, blocked → fixup and re-review

Key Concepts

ConceptSummary
Behavioral SlicesDeployable behaviors, not technical tasks. "Can a user demo this alone?"
Role SeparationDelivery writes code; Review audits and approves. Self-approval prohibited.
Git DisciplineStatus before work, explicit paths, fixups for amendments
Code GuidelinesImprove touched code only, no speculative abstraction

Full Document

All rules with examples and details: 
AGENTS.md