Agent skill
shape-up
Use when asked to "shape up", "run a shaping session", "set an appetite", "scope a project without estimates", "betting table", or "ship in fixed cycles". Helps teams escape estimate-driven development and Scrum fatigue. The Shape Up method (created by Ryan Singer at Basecamp/37signals) uses fixed time boxes, variable scope, and collaborative shaping to ship meaningful work predictably.
Install this agent skill to your Project
npx add-skill https://github.com/wdavidturner/product-skills/tree/main/skills/shape-up
SKILL.md
Shape Up
What It Is
Shape Up is a product development methodology built on one core insight: you cannot estimate your way to shipping—you must shape your way there.
Traditional approaches ask "How long will this take?" and then try to hit that estimate. Shape Up flips this: decide upfront how much time you're willing to spend (the appetite), then shape a version of the solution that fits within that constraint.
The methodology emerged from 17 years of building Basecamp, where the founding team faced an unusual constraint: their only engineer (DHH) worked just 10 hours per week. This forced extreme clarity about what to build and ruthless scoping to ensure every hour counted. As the company grew, they formalized these practices into Shape Up to maintain startup speed at scale.
The key shift: Move from "What's the estimate for this?" to "What version of this can we confidently ship in the time we're willing to spend?"
When to Use It
Use Shape Up when you need to:
- Stop projects from dragging — work that should take weeks is taking months
- Escape the estimate trap — you're tired of estimates that are always wrong
- Give teams real autonomy — not just ticket execution
- Reduce meeting overhead — Scrum rituals are consuming your time
- Ship meaningful chunks — not just incremental tickets that don't add up to anything
- Align product and engineering — there's a wall between them today
- Maintain startup speed — as you scale past 30-50 people
When Not to Use It
Don't use Shape Up when:
- You're 3 people or fewer — just talk to each other, formalization isn't needed yet
- There's no real complexity — simple tasks don't need shaping
- You can't get engineering into shaping — without technical input, shaping fails
- Leadership isn't bought in — you need exec support to protect build time
- You're doing pure maintenance — bug fixes don't need the full process
Patterns
Detailed examples showing how to apply Shape Up correctly. Each pattern shows a common mistake and the correct approach.
Critical (get these wrong and you've wasted your time)
| Pattern | What It Teaches |
|---|---|
| estimates-vs-appetite | Don't ask "how long?" — decide how much time you're willing to spend |
| unshaped-work | A Figma file or PRD is not shaped work — you need collaborative clarity |
| shaping-without-engineering | Shaping without a senior engineer is a recipe for blowups |
| ten-pound-bag | You can't put 10 pounds of scope in a 5 pound time box |
| fuzzy-problem | "Build a calendar" is not a problem — narrow it down first |
High Impact
| Pattern | What It Teaches |
|---|---|
| too-abstract-shaping | Fat marker sketches must communicate the idea, not just be blurry wireframes |
| scope-hammering | Cut scope before you start, not when you're out of time |
| tickets-not-projects | Give teams whole projects, not shredded tickets |
| hill-chart-theater | Hill charts show real progress, not status theater |
| missing-kickoff | Builders must translate shaped work into 9 or fewer implementation scopes |
| cool-down-skipping | Teams need breathing room between cycles to reset |
Medium Impact
| Pattern | What It Teaches |
|---|---|
| betting-table-dysfunction | Betting is a real commitment, not a backlog shuffle |
| junior-detail-dial | Adjust shaping detail based on who's building |
| circuit-breaker-fear | If it's not working, stop building and return to shaping |
Deep Dives
Read only when you need extra detail.
references/shape-up-playbook.md: Expanded framework detail, checklists, and examples.
Resources
Books:
- Shape Up by Ryan Singer — the original free book (basecamp.com/shapeup)
- Demand-Side Sales 101 by Bob Moesta — for the framing/problem discovery phase
- Competing Against Luck by Clayton Christensen — Jobs-to-be-Done theory
Courses:
- Shaping in Real Life — Ryan Singer's course on practical shaping
Other:
- Ryan Singer's website: ryansinger.co
- 37signals blog for ongoing insights
Credit: Shape Up was created by Ryan Singer during his 17 years at Basecamp/37signals. This skill is based on his book and podcast conversations.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
wdavidturner/product-skills
radical-candor
Use when asked to "radical candor", "give feedback that cares", "have a difficult conversation", "challenge directly", "manage performance issues", or "give praise that lands". Helps deliver direct feedback while showing you care. The Radical Candor framework (created by Kim Scott) teaches how to challenge directly while caring personally.
wdavidturner/product-skills
hooked-model
Use when asked to "build habit-forming products", "Hooked model", "trigger action reward investment", "create sticky behavior loops", or "design habit loops". Helps design products that form unprompted user habits. The Hooked Model (created by Nir Eyal) explains how products create habits through Trigger, Action, Variable Reward, and Investment.
wdavidturner/product-skills
strategic-narrative
Use when asked to "strategic narrative", "Andy Raskin", "tell our company story", "write a pitch deck", "explain why customers should care", or "movement narrative". Helps craft compelling narratives that define movements rather than just selling products. The Strategic Narrative framework (created by Andy Raskin) transforms pitches from feature lists into stories about change.
wdavidturner/product-skills
design-sprint
Use when asked to "run a design sprint", "5-day sprint", "prototype in a week", "test ideas before building", or "Jake Knapp sprint". Helps teams go from problem to tested prototype in five days. The Design Sprint framework (created by Jake Knapp at Google Ventures) compresses months of work into one focused week.
wdavidturner/product-skills
hierarchy-of-marketplaces
Use when asked about "marketplace strategy", "chicken and egg problem", "liquidity", "two-sided market", "tipping a marketplace", "GMV growth", or "Sarah Tavel marketplaces". Helps founders and product leaders build defensible marketplace businesses by sequencing supply and demand. The Hierarchy of Marketplaces framework (created by Sarah Tavel / Benchmark) provides a progression from focused launch to market dominance.
wdavidturner/product-skills
okrs
Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and create a cadence of progress. The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at Google) creates alignment, focus, and learning cycles. Christina Wodtke's Radical Focus approach emphasizes simplicity and avoiding common pitfalls.
Didn't find tool you were looking for?