Creates TDD implementation plans where tests ARE the plan. Specifies test specs and structural context per phase — implementation emerges during execution, not planning. Verification is fully automated; no manual verification step. Use when planning features test-first, creating TDD plans from design artifacts, or when the user asks for a test-driven implementation plan. NOT for executing a plan test-first (the Red-Green-Refactor cycle during implementation) — that is practicing-tdd.
Breaks an epic into an ordered backlog of vertical, sprint-sized user stories. Use when splitting an epic into stories, planning a feature's story backlog, or when a story feels too large but isn't ready for task breakdown. Produces 4-8 demoable stories, each independently shippable and grounded in user-visible behavior. NOT for sub-story implementation slicing (see slicing-elephant-carpaccio) or for writing one story's full BDD spec (see writing-agile-stories).
Slices a single feature or story into ultra-thin vertical increments (minutes-to-hours each) using Alistair Cockburn's Elephant Carpaccio methodology. Use during implementation planning when one story or feature is too large to build in a session and you need demoable increments across layers. Produces an ordered backlog of 10-20 thin slices, each independently working, testable, and demoable. NOT for splitting an epic into sprint-sized stories (see decomposing-epics).
Write well-scoped, verifiable development tasks for non-user-facing work — refactors, test work, and dependency/tooling changes. Use to "write a dev task", create a "refactor task", a "tech-debt ticket", a "test task", or a "dependency upgrade task"; to capture "non-user-facing work" or a "technical task"; or to write a "definition of done for a refactor". Produces an implementation-focused task with a verifiable Definition of Done. For user-facing behavior, use writing-agile-stories instead.
Expert guidance for creating, writing, and refining Claude Code Skills. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices.
Examines a git-machete stack of dependent branches and drafts preemptive PR comments warning reviewers that code in an earlier PR is already refactored, renamed, moved, deleted, or fixed later in the stack. Output is DRAFT ONLY — the user pastes it manually; the skill never posts to GitHub. Use for stacked PRs, a git-machete stack, when reviewers comment on code that is "already fixed/refactored/handled later in the stack", to preempt reviewer comments on superseded code, to draft PR comments for a branch stack, or to find code in an earlier branch that a later branch supersedes.
Researches and documents existing codebase implementations. Use when exploring how code works, understanding architecture, answering 'how does X work?' questions, or gathering context before making changes. Produces structured research documents with code references.
Enforces test-first development with Red-Green-Refactor cycle. Use when implementing features, fixing bugs, writing tests, or when someone mentions TDD, test-driven, "test first", or "write a failing test".