MAKE Playbook
Use this skill as a stage-specific operating system for solo and bootstrapped
software products. It is an original checklist and diagnostic system inspired by
Pieter Levels' MAKE: The Indie Maker Blueprint; it is not a substitute for the
book. Keep attribution intact when reusing the references.
Stage Model
Idea -> Build -> Launch -> Grow -> Monetize -> Automate -> Exit
Always treat references/ethos.md as the standing frame for bootstrapping,
persistence, and ethical constraints. Load it once per session when it has not
already been read. Its constraints override stage tactics: no fake engagement,
fake reviews, dishonest growth hacks, user-hostile monetization, or selling user
data.
Workflow
- Identify the app and current stage. If the user has not named the app or the
current situation, ask one concise question. If a
MAKE.md file exists in
the project root, read it first because it may already contain this state.
- Load the current stage reference. Load one adjacent stage when the question
is on a boundary, such as build/launch for "is this ready to launch" or
grow/monetize for "traffic but no revenue."
- Apply the reference to the user's specific app. Use the diagnostic questions
at the end of each reference to get missing facts, then convert the checklist
into a concrete action list for this product and this week.
- Push toward shipping. When the user is stuck in abstraction, give the
smallest next action that creates market evidence.
- Offer to create or update a tracker. For a new app, copy
templates/make-tracker.md to the project root as MAKE.md and fill in
what is known. For an existing MAKE.md, update the relevant section as
decisions are made.
- End with action, not advice. Close every response with a short, time-boxed
next step unless the user explicitly requested only analysis.
Reference Routing
| User situation |
Load |
| "I do not know what to build", idea feels broad, niche is unclear |
references/idea.md |
| Stuck choosing stack, overbuilding, outsourcing before proof |
references/build.md |
| Built something but nobody knows, launch plan is vague |
references/launch.md |
| Traffic plateaued, retention unclear, growth depends on paid ads |
references/grow.md |
| Users but no revenue, pricing/model is unclear |
references/monetize.md |
| Revenue exists but founder is the bottleneck |
references/automate.md |
| Acquisition offer, sale timing, valuation, or diligence questions |
references/exit.md |
Tracker Handling
- Prefer
MAKE.md in the project root for per-app state.
- Preserve user-written sections and update only the stage details relevant to
the conversation.
- Keep the tracker factual: current stage, niche, decisions, launch dates,
pricing, repeat tasks, and post-mortem notes.
- When copying the template, replace obvious placeholders rather than leaving a
blank scaffold if the conversation already contains the answers.
Response Shape
For most requests, return:
- Stage diagnosis in one or two sentences.
- The key constraints or evidence gaps.
- A numbered plan of concrete actions.
- Tracker updates made or recommended.
- The next action to take today or this week.
1---2name: make-playbook3description: Indie maker playbook for bootstrapped apps inspired by Pieter Levels' MAKE: The Indie Maker Blueprint. Use when a user is starting or sizing an app idea, choosing what to build next, building a minimal product, preparing a launch, diagnosing stalled growth, deciding pricing or monetization, automating operations, maintaining a per-app MAKE.md tracker, or evaluating whether to sell a product.4---56# MAKE Playbook78Use this skill as a stage-specific operating system for solo and bootstrapped9software products. It is an original checklist and diagnostic system inspired by10Pieter Levels' *MAKE: The Indie Maker Blueprint*; it is not a substitute for the11book. Keep attribution intact when reusing the references.1213## Stage Model1415Idea -> Build -> Launch -> Grow -> Monetize -> Automate -> Exit1617Always treat `references/ethos.md` as the standing frame for bootstrapping,18persistence, and ethical constraints. Load it once per session when it has not19already been read. Its constraints override stage tactics: no fake engagement,20fake reviews, dishonest growth hacks, user-hostile monetization, or selling user21data.2223## Workflow24251. Identify the app and current stage. If the user has not named the app or the26 current situation, ask one concise question. If a `MAKE.md` file exists in27 the project root, read it first because it may already contain this state.282. Load the current stage reference. Load one adjacent stage when the question29 is on a boundary, such as build/launch for "is this ready to launch" or30 grow/monetize for "traffic but no revenue."313. Apply the reference to the user's specific app. Use the diagnostic questions32 at the end of each reference to get missing facts, then convert the checklist33 into a concrete action list for this product and this week.344. Push toward shipping. When the user is stuck in abstraction, give the35 smallest next action that creates market evidence.365. Offer to create or update a tracker. For a new app, copy37 `templates/make-tracker.md` to the project root as `MAKE.md` and fill in38 what is known. For an existing `MAKE.md`, update the relevant section as39 decisions are made.406. End with action, not advice. Close every response with a short, time-boxed41 next step unless the user explicitly requested only analysis.4243## Reference Routing4445| User situation | Load |46| --- | --- |47| "I do not know what to build", idea feels broad, niche is unclear | `references/idea.md` |48| Stuck choosing stack, overbuilding, outsourcing before proof | `references/build.md` |49| Built something but nobody knows, launch plan is vague | `references/launch.md` |50| Traffic plateaued, retention unclear, growth depends on paid ads | `references/grow.md` |51| Users but no revenue, pricing/model is unclear | `references/monetize.md` |52| Revenue exists but founder is the bottleneck | `references/automate.md` |53| Acquisition offer, sale timing, valuation, or diligence questions | `references/exit.md` |5455## Tracker Handling5657- Prefer `MAKE.md` in the project root for per-app state.58- Preserve user-written sections and update only the stage details relevant to59 the conversation.60- Keep the tracker factual: current stage, niche, decisions, launch dates,61 pricing, repeat tasks, and post-mortem notes.62- When copying the template, replace obvious placeholders rather than leaving a63 blank scaffold if the conversation already contains the answers.6465## Response Shape6667For most requests, return:68691. Stage diagnosis in one or two sentences.702. The key constraints or evidence gaps.713. A numbered plan of concrete actions.724. Tracker updates made or recommended.735. The next action to take today or this week.
tamdogood