37signals-way

Applies 37signals product development principles to shape, bet, and ship lean software.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/HafidJoss/Lummy --skill 37signals-way-hafidjoss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 37signals-way
Source: https://github.com/HafidJoss/Lummy/tree/main/agent/skills/37signals-way
Command: npx skills add https://github.com/HafidJoss/Lummy --skill 37signals-way-hafidjoss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams overbuild features, drown in backlogs and meetings, and miss deadlines because scope expands to fill unlimited timelines. This Skill provides the 37signals framework from Getting Real, Rework, and Shape Up to cut scope, fix time constraints, and ship with small autonomous teams. ## Core Features & Use Cases - Shaping and Pitching: Turn raw ideas into bounded pitches with appetite, breadboards, fat marker sketches, rabbit holes, and no-gos. - Betting and Cycles: Replace backlogs and roadmaps with six-week cycles, a betting table, circuit breakers, and two-week cool-downs. - Small Team Execution: Run three-person teams with hill charts, async communication, and scope cutting instead of standups and status meetings. - Use Case: A product team with an 800-item backlog and slipping sprints uses this Skill to abolish the backlog, shape three pitches, bet on one six-week cycle, and track progress with hill charts instead of daily standups. ## Quick Start Ask the assistant to apply the 37signals method to shape a feature idea into a pitch with appetite, rabbit holes, and no-gos for a six-week cycle.

Frequently Asked Questions about 37signals-way

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I shape a product pitch using Shape Up?

A shaped pitch has five elements: problem, appetite, solution, rabbit holes, and no-gos. Set the appetite first as a time budget, sketch the solution with breadboards or fat marker sketches, then explicitly list risks and exclusions before bringing it to the betting table.

What is the difference between appetite and estimation?

Appetite asks how much time a problem is worth, which is a strategic decision made before a solution exists. Estimation asks how long work will take, which produces guesses that grow under pressure. Appetite constrains the solution instead of letting the solution dictate the timeline.

How do hill charts replace standup meetings?

Hill charts place each named scope on a hill where uphill means figuring things out and downhill means executing known work. Teams update dot positions twice a week asynchronously, making stuck scopes visible without daily status meetings or misleading percentage-complete reports.

When should the circuit breaker stop a project?

Invoke the circuit breaker when a six-week cycle ends with significant unfinished work, the core approach proved wrong, or the team is grinding without momentum. The project pauses and must be re-shaped and re-bet rather than receiving an automatic extension.

When is the 37signals approach not a good fit?

The method fits small teams building opinionated products with fixed-time cycles. It is harder to apply when work requires large coordinated teams, regulatory deadlines with fixed scope, or exploratory research where the problem itself is not yet understood.