decomposelisted

# Decompose Break a feature request into a chain of ordered GitHub issues that `/ship-loop` (or the scheduled issue-worker) can implement autonomously. ## When to Use - "Build a reservation system" → 5-8 ordered issues - "Add dark mode to the hospitality app" → 3-4 ordered issues - "Create an admin dashboard" → 6-10 ordered issues ## Workflow ### Step 1: Understand the Feature Read the user's feature description. If invoked with arguments, use those. Otherwise ask: - What should the feature do? - Which app/service does it affect? - Any constraints or preferences? ### Step 2: Analyze the Codebase Before decomposing, understand what exists: ```bash # Check relevant areas ls apps/ services/ packages/ # Read CLAUDE.md for architecture context # Read relevant service/app CLAUDE.md files # Check existing patterns in the target area ``` Key questions: - Which existing files/components need modification? - What new files need creation? - Are there existing patterns to follow (routes, components, schemas)? - What dependencies exist between the pieces? ### Step 3: Decompose into Issues Break the feature into **3-10 issues**, each representing a single agent-workable unit. Each issue should be: - **Self-contained**: Can be implemented without other issues being done first (unless explicitly dependent) - **Testable**: Has clear acceptance criteria - **Agent-sized**: 15-60 minutes of work, touching 1-5 files - **Ordered**: Later issues build on earlier ones #### Issue Sizi