Use this skill when discussing feature breakdown, PR structure, implementation ordering, or how to decompose work. Guides thinking about vertical slices (end-to-end functionality) rather than horizontal layers (all of one layer first). Triggers on "how should we break this down?", "what order should we implement?", "how many PRs?", or decomposition discussions.
/plugin marketplace add jclfocused/claude-agents/plugin install linear-planning-workflow@laserfocused-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
examples.mdreferences.mdThis skill guides the decomposition of features into vertical slices - thin, end-to-end pieces of functionality that can be shipped independently.
Apply this skill when:
A vertical slice cuts through ALL layers of the application to deliver a thin piece of complete functionality.
┌─────────────────────────────────────────┐
│ HORIZONTAL LAYERS │
├─────────────────────────────────────────┤
│ UI Layer │ █ │ │ │ │
├────────────────┼───┼─────┼─────┼────────┤
│ API Layer │ █ │ │ │ │
├────────────────┼───┼─────┼─────┼────────┤
│ Service Layer │ █ │ │ │ │
├────────────────┼───┼─────┼─────┼────────┤
│ Data Layer │ █ │ │ │ │
└────────────────┴───┴─────┴─────┴────────┘
↑
Vertical Slice
(Complete feature)
Building all of one layer before moving to the next:
Problems: Nothing works until everything is done, late integration issues, hard to show progress.
Building thin, complete features:
Benefits: Each slice is shippable, continuous integration, visible progress.
What can the user DO? Each action is often a slice.
For each action, what's the minimal implementation?
Which slices enable other slices?
| Size | Indicators |
|---|---|
| Too Big | Multiple user actions, >2 days work, many acceptance criteria |
| Too Small | Just infrastructure, just types, <1 hour work |
| Just Right | One capability, 1-2 days, 3-5 acceptance criteria |
Use prefixes to show slice relationships:
SLICE 1: Basic product list display
SLICE 1.1: Add product image support
SLICE 2: Product search functionality
When creating Linear issues:
Each slice should be independently deployable, testable, and valuable.
Remember: Ship working software frequently. Slices make this possible.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.