shape-up

# Shape Up - Shaping Workflow

## Core Philosophy

**Fixed time, variable scope.**

Shape Up inverts traditional estimation:
- You don't estimate how long something takes, then ask for that time
- You decide how much time something is worth, then shape to fit

**Shaped work has three properties:**
1. **Rough** - Visibly unfinished, leaves room for creativity
2. **Solved** - Main elements connected, clear direction
3. **Bounded** - Explicit appetite and no-gos

**The shaper's job:** Define work at the right abstraction level - neither too vague (leaves team lost) nor too detailed (constrains team creativity).

**See:** `skills/shape-up/references/methodology.md` for the full philosophy.

---

## Entry Point

When this skill is invoked, start with:

```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 SHAPE UP
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

What are you working on?

  1. Shape new work
     → Walk through the 4-step process
     → Output: Pitch ready for betting

  2. Review an existing pitch
     → Challenge boundaries, rabbit holes, no-gos
     → Output: Feedback and improvements

  3. Quick pitch (I know what I want)
     → Skip the coaching, just format
     → Output: Pitch document

  4. Not sure where to start
     → Tell me about the raw idea
     → I'll help figure out if it's ready to shape

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
```

**Parse intent from context:**
- If user mentions "pitch" or "shape" a specific feature → Flow 1 (Shape New)
- If user pastes or describes an existing pitch → Flow 2 (Review)
- If user uses `--pitch` flag → Flow 3 (Quick Pitch)
- If user describes a vague idea or problem → Flow 4 (Explore First)

**Command-line shortcuts:**
- `/shape` → Show entry point
- `/shape "feature idea"` → Start Flow 1 with context
- `/shape --review` → Start Flow 2
- `/spec --pitch` → Start Flow 3 (quick pitch format only)
- `/shape --established` → Flow 1 with established product m