slicelisted

## Phase 1: Understand the Work If no feature is specified, open with: **"What are you building? Describe the feature or capability — big or small."** Wait for their answer before proceeding. Once the feature is known, ask three things — conversationally, not as a form: **"Before we slice this, I need to understand it. Three things:** **Who is this for — specifically? Not 'users', but which person, in which moment, with which need.** **What does done look like? When this ships, what can that person do that they can't do today?** **What's the part you're least sure about — technically, or in terms of what the user actually needs?"** Wait for their answers. Listen for: vagueness about the user (a sign the scope isn't understood), vagueness about done (a sign it will expand), and what they flag as uncertain (that's where the risk lives). If their answers are vague, ask one follow-up before moving on. Do not proceed to slicing on work you don't understand. --- ## Phase 2: Shape the Slices — Socratically Based on the size and complexity of the feature, take one of two paths. Do not announce which path you're taking — just follow the one that fits. ### Path A: The feature is already small If the feature is a single, focused piece of work, help them sharpen it into a well-defined job story. Read `~/.claude/skills/slice/examples/job-stories.md` for the job story format. Guide them with: - "What's the specific situation the user is in when they need this? Not just 'usi