decomposelisted

# /decompose -- Work Item Decomposition **Fast-path companion to Pillar 4 (Increase Speed).** Breaks one epic or feature into work items sized at roughly a day of effort or less, without running a full `/speed` throughput analysis. The book's guidance: standardize decomposition into small, countable units so work can be forecasted, not estimated. ## When to invoke - Planning a single feature or epic before it enters a sprint/backlog - An item has sat "in progress" for multiple days with no sub-tasks -- break it down now - Before estimating a feature -- decompose first, then let counted throughput do the forecasting (see `/speed`) ## What it checks 1. **Current shape** -- is the feature/epic currently one large ticket, or already split? How big is each piece today (days-open as a proxy if points aren't tracked)? 2. **Natural seams** -- where does the work split along independently shippable, independently testable lines (e.g., by layer, by user-facing slice, by data migration vs. behavior change)? 3. **Sequencing** -- which sub-items unblock others, and which can ship in parallel? 4. **Cuttable scope** -- is there a "least amount of work to accomplish the outcome" version, with clearly-optional pieces flagged separately (ties to Speed's "waste" check)? ## Inputs - **The feature/epic itself** -- the ticket description, a design doc, or the user's plain-language description of what needs to happen - **Existing size signal, if any** -- similar past items' actual days-to-cl