Game Changing Features
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
Applies Steve Blank's Customer Development methodology from The Four Steps to the Epiphany.
$ npx skills add getagentseal/founder-playbook --skill four-steps -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getagentseal/founder-playbook four-steps --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/four-steps .claude/skills/four-steps && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "four-steps" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/four-steps into .claude/skills/four-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "four-steps", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/getagentseal/founder-playbook/tree/main/skills/four-stepsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add getagentseal/founder-playbook --skill four-steps -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getagentseal/founder-playbook four-steps --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/four-steps .agents/skills/four-steps && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "four-steps" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/four-steps into .agents/skills/four-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "four-steps", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getagentseal/founder-playbook --skill four-steps -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getagentseal/founder-playbook four-steps --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/four-steps .cursor/skills/four-steps && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "four-steps" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/four-steps into .cursor/skills/four-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "four-steps", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/getagentseal/founder-playbook.git --path skills/four-steps--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add getagentseal/founder-playbook --skill four-steps -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getagentseal/founder-playbook four-steps --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/four-steps .gemini/skills/four-steps && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "four-steps" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/four-steps into .gemini/skills/four-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "four-steps", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install getagentseal/founder-playbook four-stepsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add getagentseal/founder-playbook --skill four-steps -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/four-steps .github/skills/four-steps && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "four-steps" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/four-steps into .github/skills/four-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "four-steps", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getagentseal/founder-playbook --skill four-steps -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getagentseal/founder-playbook four-steps --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/four-steps .opencode/skills/four-steps && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "four-steps" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/four-steps into .opencode/skills/four-steps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "four-steps", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
four-stepsApplies Steve Blank's Customer Development methodology from The Four Steps to the Epiphany.
Four Steps is an agent skill from getagentseal/founder-playbook. Applies Steve Blank's Customer Development methodology from The Four Steps to the Epiphany. Use when a startup is searching for customers and a business model before scaling. Covers Customer Discovery, Customer Validation, Customer Creation, and Company Building. Triggers include 'we built it but no one's buying', 'should we hire salespeople yet', 'how do we find our first customers', 'we're burning cash and sales aren't scaling', 'are we in a new or existing market', 'when do we scale'. NOT for companies that…
Its SKILL.md is about 7.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `cases.md`, `examples.md` and `frameworks.md`).
It sits in Product & Project Management, covering Product strategy. The repository describes itself as: 15 proven business books distilled into AI-native skills. Works with Claude Code, ChatGPT, Gemini, Cursor. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e811e63. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Four Steps loads about 7.5k tokens when it runs. Until then it costs about 184 tokens; SKILL.md has 3,359 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from getagentseal/founder-playbook at commit e811e63, republished under its MIT licence (© getagentseal). 3,359 words, ~7,488 tokens.
.claude/skills/four-steps/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Note: This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.
"Startups that survive the first few tough years do not follow the traditional product-centric launch model. Through trial and error, hiring and firing, successful startups all invent a parallel process to product development. I call this process 'Customer Development.'" - Steve Blank
Are you searching for customers and a business model (not executing a known one)?
├─ YES → This skill is for you
└─ NO → You have paying customers and a repeatable sales process?
├─ YES, but stuck before mainstream → Use Crossing the Chasm
├─ YES, scaling fine → You're past this. Use Company Building concepts only
└─ NO, still pre-product → Start here at Customer Discovery
Have you validated that people will pay for your product?
├─ NO → Start at Customer Discovery (Step 1)
└─ YES → Can you describe a repeatable sales process?
├─ NO → You're in Customer Validation (Step 2)
└─ YES → Have you matched your launch to your Market Type?
├─ NO → You're in Customer Creation (Step 3)
└─ YES → Company Building (Step 4)9 out of 10 new product introductions fail. Not because the products don't work - because the companies never found customers.
The Product Development model (Concept → Build → Test → Launch) was designed for manufacturing in the early 1900s and adopted by consumer packaged goods in the 1950s. It works when you're launching a new product into an existing market with known customers. Most startups have neither.
PRODUCT DEVELOPMENT (what everyone does):
Concept/Seed ──→ Product Dev ──→ Alpha/Beta ──→ Launch
↑
"Where are the
customers?"
CUSTOMER DEVELOPMENT (what winners do - in parallel):
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ Customer │←──→│ Customer │←──→│ Customer │───→│ Company │
│ Discovery│ │Validation│ │ Creation │ │ Building │
└──────────┘ └──────────┘ └──────────┘ └──────────┘
↻ ↻ ↻
iterate iterate iterateCustomer Development is a companion to Product Development, not a replacement. Each step is an iterative circle - going backwards is natural and valuable, not failure.
"It's OK to screw it up if you plan to learn from it." - the heart of the methodology.
| # | Flaw | Consequence |
|---|---|---|
| 1 | Where are the customers? | Greatest risk is customer/market development, not product development |
| 2 | Focus on first customer ship date | FCS means Engineering is done, not that you understand customers |
| 3 | Execution instead of learning | Sales/marketing hired for what they know, not what they can learn |
| 4 | No meaningful sales/marketing milestones | "Hire, fire, repeat" substitutes for real progress metrics |
| 5 | Product dev used to measure sales | Clock to tell temperature - measures the wrong thing |
| 6 | Product dev used to measure marketing | All plans made in "a vacuum of real customer feedback" |
| 7 | Premature scaling | Fully staffing sales/marketing before knowing if anyone will buy |
| 8 | Death spiral | Premature scaling → burn rate → missed numbers → fire VP Sales → fire VP Marketing → fire CEO |
| 9 | Not all startups are alike | Four Market Types need radically different strategies |
| 10 | Unrealistic expectations | "Build it and the customers will come" is not a strategy, it's a prayer |
"In a startup, no facts exist inside the building, only opinions."
Everything depends on Market Type. It changes how you find customers, how you launch, how you spend, and how long it takes to become profitable.
| Market Type | Definition | Competitors | Time to Profit | Key Risk |
|---|---|---|---|---|
| Existing | Higher performance than what's currently offered | Known incumbents define the market | 12-18 months | Cost of entry (Lanchester rules) |
| New | Enables something customers couldn't do before | Non-consumption / other startups | 3-7 years | Market may never materialize |
| Resegmented (Low-cost) | "Good enough" at substantially lower price | Incumbents who abandon low margins | 18-36 months | Must be profitable at low price |
| Resegmented (Niche) | Radical enough to change the rules for a subset | Incumbents who defend profitable core | 18-36 months | Segmentation must be spot-on |
"Market Type changes everything a company does."
Are there existing companies selling comparable products?
├─ NO → NEW MARKET
│ (No competitors, but also no existing customers)
└─ YES → Are you competing on the same basis (features, performance)?
├─ YES → EXISTING MARKET
│ (You must be better on known dimensions)
└─ NO → Are you targeting a subset of customers?
├─ YES, at lower price → RESEGMENTED (LOW-COST)
└─ YES, for a specific need → RESEGMENTED (NICHE)Same team, same CEO (Donna Dubinsky), same product category, three years apart:
Identical products and team. Wrong Market Type strategy = death.
"The goal of Customer Discovery is finding out who the customers for your product are and whether the problem you believe you are solving is important to them."
"The initial product specification comes from the founders' vision, not the sum of a set of focus groups."
Not all early customers are equal. You need earlyvangelists - visionary customers who:
| # | Characteristic | Why It Matters |
|---|---|---|
| 1 | Has a problem | Not latent - they know it exists |
| 2 | Understands the problem | Can articulate it and its cost |
| 3 | Actively searching for a solution | Has a timetable |
| 4 | Has cobbled together an interim solution | Proves the pain is real enough to act on |
| 5 | Has or can acquire budget | Can actually buy |
The customer pain hierarchy:
"What problem?" → Latent need. Useless for 2 years.
"Yes, terrible. I hand out water." → Active, but only papering symptoms.
"Losing $500K/yr. Need X by Y." → Visualized solution. Getting warm.
"Wrote a req to IT, they cobbled → HAS A HOMEMADE SOLUTION. YES.
something but it keeps crashing."
"Budgeted $500K for a vendor." → HAS BUDGET. ULTIMATE CUSTOMER.| Phase | Activity | Key Question |
|---|---|---|
| 0 | Get Buy-In | Does the team agree to this process? |
| 1 | State Your Hypotheses | What do we believe about customer, problem, product, pricing, channel, market, competition? |
| 2 | Test the Problem | Do customers recognize and care about this problem? |
| 3 | Test the Product | Does our product concept solve their problem? Will they pay? |
| 4 | Verify | Iterate or proceed to Customer Validation? |
Six hypotheses to articulate before leaving the building:
"If, and only if, you are successful in this step do you proceed to Customer Validation."
Passing means: founders' vision matches a real, painful, paid-for problem. Failing means: iterate within Discovery or exit.
"Customer Validation is where the rubber meets the road."
Build a repeatable sales roadmap - "the playbook of the proven and repeatable sales process that has been field-tested by successfully selling the product to early customers."
"Building a roadmap to sales success, rather than building a sales organization, is the heart of Customer Validation."
A pipeline is the funnel (leads → suspects → prospects → closes → orders). Mature companies need it.
A roadmap answers: Who influences? Who recommends? Who decides? Who has budget? Who sabotages? How many calls per sale? Average cycle? What selling strategy? Key customer problems? Profile of the optimal earlyvangelist?
"It is impossible to build a sales pipeline without first having developed a sales roadmap."
Founders/CEO must be in front of customers through at least the first iteration. Delegating to VP of Sales is often fatal.
Three conditions to pass:
"If you can't find enough paying customers in the Customer Validation step, the model returns you to Customer Discovery to rediscover what customers want and will pay for."
This is the pivot - predating the term's popularization. Failure here is not failure; it's learning. Most startups cycle through Steps 1-2 at least twice.
"Customer Creation builds on the success of the company's initial sales. Its goal is to create end-user demand and drive that demand into the company's sales channel."
"No serious spending in marketing until the company has a proven and repeatable sales roadmap."
Cash protection: this step is placed after Validation to move heavy marketing spending after the point where a startup has its first customers.
Most startups execute the same launch playbook regardless of Market Type. This is the #1 Customer Creation mistake.
| Building Block | Existing Market | New Market | Resegmented Market |
|---|---|---|---|
| Year 1 Goal | Market share | Market adoption | Market share + segment education |
| Positioning | Differentiation (faster, cheaper, better) | Vision and passion ("what could be") | Segmentation (unique valued spot) |
| Launch Type | Onslaught (full frontal) | Early Adopter (targeted, low-cost) | Niche (focused onslaught) |
| Demand Creation | Drive demand into channel | Educate about the market | Educate + drive demand |
Military operations research applied to market entry:
| Leader's Market Share | Implication | Cost of Entry |
|---|---|---|
| ≥74% (monopoly) | Do NOT attack head-on | 3× their budget - unaffordable |
| ≥41% (clear leader) | Very difficult | Resegment or create new market |
| 26-41% (unstable) | Some opportunity | 1.7× weakest player's budget |
| <26% (fragmented) | Market ripe for entry | Affordable entry possible |
"Your goal is to become No. 1 in something important to your customer."
Golder & Tellis (1993), 500 brands in 50 categories:
"The issue is not being first to market, but understanding the type of market your company is going to enter."
Onslaught (Existing Market): Full-frontal assault. Maximum exposure. Heavy upfront spending. Only correct for capturing share in an existing market.
Early Adopter (New Market): Targeted, low-cost. Goal is mind share, not market share. Education campaign targeting earlyvangelists. Create a "tipping point." New markets take 3-7 years to become profitable.
Niche (Resegmented Market): All demand-creation dollars focused on one identifiable segment. If the segment is speculative, treat as new market instead.
Three types to educate before launch:
| Phase | Activity |
|---|---|
| 1 | Get Ready to Launch - choose Market Type, set year-1 goals |
| 2 | Position Company and Product - audits, match positioning to Market Type |
| 3 | Launch - select launch type, audiences, messengers, craft sticky messages, measure |
| 4 | Create Demand - match demand strategy to year-1 objectives, measure, iterate |
"Company Building is where the company transitions from its informal, learning and discovery-oriented Customer Development team into formal departments with VPs of Sales, Marketing and Business Development."
Both are wrong. The answer is a mission-centric organization - the third alternative between startup chaos and corporate rigidity.
| Stage | Organizational Form | Activities |
|---|---|---|
| 1 (Discovery/Validation) | Customer + Product Development teams | Learning and discovery |
| 2 (Company Building) | Mission-centric organization | Cross the chasm |
| 3 (Large company) | Process-centric organization | Repeatable/scalable execution |
| Phase | Activity |
|---|---|
| 1 | Reach mainstream customers - match growth curve to Market Type |
| 2 | Review management, build mission-centric organization |
| 3 | Transition Customer Development team into functional departments |
| 4 | Build fast-response departments (OODA loops) |
Five components:
Blank rejects the "kick the founder out" reflex:
"The long-term success of a startup requires founder continuity long past the point when conventional wisdom says the founders should be replaced."
Do you know who your customers are and what problem you solve?
├─ NO → CUSTOMER DISCOVERY (Step 1)
└─ YES → Can you sell repeatably at a profit?
├─ NO → Have you sold to anyone?
│ ├─ NO → Still CUSTOMER DISCOVERY
│ └─ YES → CUSTOMER VALIDATION (Step 2)
└─ YES → Are you driving demand and growing?
├─ NO → CUSTOMER CREATION (Step 3)
└─ YES → COMPANY BUILDING (Step 4)Do you have a proven, repeatable sales roadmap?
├─ NO → DO NOT HIRE SALESPEOPLE
│ Founders sell. Maybe one Sales Closer.
└─ YES → Are you past Customer Validation?
├─ NO → Still NO. Iterate first.
└─ YES → Now you can staff a sales org.Can customers already do what your product does (via competitors)?
├─ NO → NEW MARKET
│ • Year 1 goal: adoption, not share
│ • Launch: early adopter (low-cost, targeted)
│ • Timeline: 3-7 years to profit
│ • Danger: onslaught launch will burn all your cash
└─ YES → Are you competing on the same dimensions?
├─ YES → EXISTING MARKET
│ • Year 1 goal: market share
│ • Launch: onslaught (if you can afford Lanchester rules)
│ • Timeline: 12-18 months to profit
└─ NO → RESEGMENTED MARKET
• Low-cost or niche?
• Year 1 goal: share + education
• Launch: niche (focused onslaught)| Number | Rule |
|---|---|
| 9 of 10 | New product introductions that fail |
| 3-7 years | Time for a new market to generate profit |
| 12-18 months | Time for an existing market startup to generate cash |
| 3× | Spending needed to attack a monopolist (Lanchester) |
| 1.7× | Spending needed to attack weakest player in fragmented market |
| 74% | Market share threshold = effective monopoly |
| 41% | Market share threshold = guaranteed for new market creator |
| 26% | Below this, no player has real market influence |
| 47% | Market pioneer failure rate (Golder & Tellis) |
| 8% | Early market leader failure rate |
| ~13 years | Average late entry of early market leaders after pioneers |
| >50% | Startups where founding CEO is removed |
| ~9 months | Half-life of a startup VP of Sales post first customer ship |
| ≥2 cycles | Minimum iterations through Steps 1-2 for most startups |
| Pattern | Mechanism | Cure |
|---|---|---|
| "Build it and they will come" | No customer development process; assume product launch = customer acquisition | Customer Discovery before scaling |
| Premature scaling | Hiring full sales/marketing orgs before validating customers | Stay lean through Steps 1-2; "staff that fits in a phone booth" |
| Death spiral | Premature scaling → burn rate → missed numbers → fire VPs → fire CEO | Don't scale until you have a repeatable sales roadmap |
| Wrong Market Type | Using existing-market tactics in a new market (or vice versa) | Definitively determine Market Type; match every activity to it |
| Onslaught in new market | Massive launch spending for customers who don't exist yet | Early adopter launch; preserve cash; focus on adoption not share |
| Branding as strategy | Substituting "brand" for precise Customer Creation activities | Market Type-matched positioning, launch, and demand creation |
| Delegating to VP of Sales | Founders stop talking to customers | Founders in front of customers through at least first iteration |
| Feature-list driven product | MRD from focus groups instead of founder vision + customer validation | "First product for the few, not the many" |
| Kicking out founders | Process-oriented replacements gut innovation | Mission-centric organization; keep founders, add complementary execs |
| Confusing pipeline with roadmap | Measuring funnel metrics before knowing who buys or how | Build sales roadmap first; pipeline comes after |
$800M raised. Automated warehouses. $40M per distribution center. IPO at $8.5B market cap (larger than top 3 grocery chains combined). Bankrupt in 24 months.
What went wrong, step by step:
Counter-example: Tesco - used existing UK retail stores as launching pad, learned what customers wanted, found a profitable model. By 2002: 85,000 orders/week, $559M in sales. Fraction of Webvan's investment.
"Explicitly or implicitly, Tesco understood the process embodied by the Customer Development model."
The framework's core ideas are durable. The specific examples and some assumptions are dated.
Customer Discovery:
Customer Validation:
Customer Creation:
Company Building:
"Products developed with senior management out in front of customers early and often - win. Products handed off to a sales and marketing organization that has only been tangentially involved in the new product development process lose. It's that simple."
Customer Development is not a process for finding features. It's a process for finding customers, a market, and a viable business model - the three things that actually determine whether a startup lives or dies.
The four steps are iterative, not linear. Going backwards is learning, not failure. The whole process can be done by a team that fits in a phone booth. And no amount of funding can accelerate it.
"You cannot create a market or customer demand where there isn't any customer interest."
The framework is foundational. The specific tactics and examples are dated. The core thesis - that customer and market discovery is a separate, iterative process that must run in parallel with product development - remains as true in 2026 as it was in 2005.
© getagentseal, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files in skills/four-steps of getagentseal/founder-playbook.
Open the folder on GitHubat commit e811e63
Four Steps next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Four Steps this skillgetagentseal/founder-playbook | 724 | — | ~7.5k | Automated safety check: Pass | MIT | |
| Game Changing FeaturesopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Company Research Briefdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~3.8k | Automated safety check: Pass | Custom licence | |
| Organic Growth Path Advisordeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~5.2k | Automated safety check: Pass | Custom licence | |
| Product Strategistalirezarezvani/claude-skills | 28k | 2 repos | ~1.8k | Automated safety check: Pass | MIT | |
| PlaidBuildGreatProducts/plaid | 217 | — | ~1.6k | Automated safety check: Pass | MIT |
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
deanpeters/Product-Manager-Skills
Builds a company research brief covering executive quotes, product strategy, transformation efforts and org context, tailored to interview prep, competitor or partnership work.
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
BuildGreatProducts/plaid
Product Led AI Development — guides founders from idea to launched product.
Fokkyp/claude-skills
Produces product-manager competitive analysis reports in Chinese, with a confirm-first scoping gate, three-phase evidence collection and single or multi-product modes.
getagentseal/founder-playbook
Builds lead generation systems using Alex Hormozi's Core Four framework (warm outreach, content, cold outreach, paid ads), lead magnets, and Rule of 100.
getagentseal/founder-playbook
Designs irresistible Grand Slam Offers using Alex Hormozi's value equation, obstacle-solution mapping, value-cost trim/stack, and offer-naming patterns.
getagentseal/founder-playbook
Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant.
getagentseal/founder-playbook
Startup diagnostic router. An agent skill from getagentseal/founder-playbook.
getagentseal/founder-playbook
Cialdini's seven principles of compliance (the classic six — reciprocation, commitment-consistency, social proof, liking, authority, scarcity — plus Unity, added 2016) and Pre-Suasion.
getagentseal/founder-playbook
Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.
Categories
Applies Steve Blank's Customer Development methodology from The Four Steps to the Epiphany. Four Steps is an agent skill from getagentseal/founder-playbook. Applies Steve Blank's Customer Development methodology from The Four Steps to the Epiphany.
Four Steps fits situations like: A startup is searching for customers and a business model before scaling; include we built it but no ones buying; should we hire salespeople yet; how do we find our first customers.
Run `npx skills add getagentseal/founder-playbook --skill four-steps -a claude-code`. Or copy the skill folder (skills/four-steps in getagentseal/founder-playbook) into .claude/skills/four-steps in your project. Claude Code loads it when a task matches its description.
Run `npx skills add getagentseal/founder-playbook --skill four-steps -a codex`. Or copy the skill folder (skills/four-steps in getagentseal/founder-playbook) into .agents/skills/four-steps in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getagentseal/founder-playbook --skill four-steps -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/four-steps, .gemini/skills/four-steps, .github/skills/four-steps and .opencode/skills/four-steps in your project.
SKILL.md names no scripts, command-line tools or credentials: Four Steps is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Four Steps is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 7.5k tokens (SKILL.md is roughly 30k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Four Steps: Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), Company Research Brief (deanpeters/Product-Manager-Skills, 7.2k stars), Organic Growth Path Advisor (deanpeters/Product-Manager-Skills, 7.2k stars) and Product Strategist (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
getagentseal (a GitHub organization) maintains it in getagentseal/founder-playbook, which has 724 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 6, 2026.
Source: getagentseal/founder-playbook on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.