Create Shape Up Pitch

Overview

Generate a pitch following the Shape Up methodology (Ryan Singer / Basecamp). A pitch defines the problem, sets a fixed time budget (appetite), sketches a solution at the right level of abstraction, identifies rabbit holes to avoid, and declares explicit no-gos. This gives teams enough direction to build without over-specifying the solution.

Workflow

1. Read product context -- Scan .chalk/docs/product/ for the product profile, related PRDs, and JTBD docs. Check .chalk/docs/engineering/ for architecture docs that inform feasibility. Understand the existing system before shaping new work.

2. Parse the feature -- Extract from $ARGUMENTS the problem or feature to pitch. If $ARGUMENTS describes a solution rather than a problem, dig back to the underlying need and reframe.

3. Determine the next file number -- Read filenames in .chalk/docs/product/ to find the highest numbered file. The next number is highest + 1.

4. Write the Problem section -- Describe the problem from the user's perspective. Include: who has this problem, when they encounter it, and what the current workaround is. Ground it in specific scenarios, not abstract statements.

5. Set the Appetite -- Define the fixed time budget (typically 2 or 6 weeks in Shape Up). The appetite is a constraint, not an estimate. State what the team should be willing to spend and why that budget is appropriate for the value delivered.

6. Sketch the Solution -- Describe the solution at fat-marker sketch level: broad strokes, key affordances, critical flows. Do not specify UI details, exact copy, or implementation. Show enough that a team can start building but has room to make design decisions.