planning

Plans implementation work as vertical slices with TDD increments and small reviewable pull requests.

Updated May 18, 2024
One-click install
npx skills add https://github.com/joshhornby/dotfiles --skill planning-joshhornby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/joshhornby/dotfiles/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/joshhornby/dotfiles --skill planning-joshhornby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large features and epics often get implemented as monolithic changes or layer-by-layer plans that delay feedback, hide broken integration, and produce oversized pull requests. This Skill turns selected stories into implementation plans built from small, known-good vertical slices, each independently deployable and reviewable. ## Core Features & Use Cases - Vertical Slice Planning: Defines slices by actor, trigger, observable outcome, and production path, with explicit size heuristics and anti-patterns to avoid layer-cake plans. - TDD and Quality Gates: Enforces RED-GREEN-REFACTOR increments per behavior-changing slice, a pre-PR mutation-testing or alternate-evidence gate, and commit approval checkpoints. - Delivery Topology: Defaults each slice to one trunk-based PR, with explicit support for cross-slice or intra-slice stacked PRs and mechanism-reduction programs. - Use Case: Given a selected user story for a gift-tracking feature, produce a plans/gift-tracking.md plan with ordered slices, acceptance criteria, and per-slice PR boundaries, then implement each slice with tests first. ## Quick Start Ask the assistant to plan the selected story as vertical slices with acceptance criteria and one small pull request per slice.

Frequently Asked Questions about planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a large feature into small pull requests?

Plan the feature as vertical slices, where each slice delivers one observable behavior through the real production path and fits in a single trunk-based PR. Name the actor, trigger, outcome, and path for each slice, and default to the thinnest walking skeleton first.

What is a vertical slice in software planning?

A vertical slice is the smallest end-to-end behavior a real actor can observe, touching the real entry point, domain logic, persistence, and output. It leaves all tests passing, is independently deployable, and can be described in one sentence.

When should I use stacked pull requests instead of independent PRs?

Use a stack when later slices have hard dependencies or deliberate flow lineage and will be in flight before lower PRs merge, or when one slice needs focused review layers. Otherwise default each slice to an independent trunk-based PR.

Does this planning approach require test-driven development?

Yes, every behavior-changing slice uses RED-GREEN-REFACTOR increments with a failing test written first. Pure refactors and reduction slices instead start from passing preservation evidence, and mutation testing runs once at PR readiness.

When is horizontal work like database or infrastructure setup allowed?

Horizontal work may be its own slice only when it names the vertical slice it unlocks, leaves the codebase deployable, has observable verification, and is smaller than doing it inside the vertical slice. It must not introduce speculative abstractions.