Decide on paper, then build.

Answer plain-English questions in Claude, get six documents and a PDF.

Six planning documents fanned out like a stack of paper: product requirements, technical requirements, app flow, design brief, backend schema, and a gold implementation plan with a build-order checklist

About an hour, one question at a time. Works for websites, portals, apps and SaaS.

Most projects go wrong before anyone writes code.

Builders guess at the tools

Halfway through, someone picks a payment provider or a database nobody agreed to, and the price changes.

Nobody agrees what done means

“A booking page” means one thing to you and another to the person quoting it. Six months later you find out which.

Customer data lands wherever it was easiest

Who can see what gets decided by accident, usually after something has already gone wrong.

You answer questions. Claude does the writing.

Your job is the reading and the deciding. The drafting, the structure and the cross-checking are handled for you.

  1. Start the interview

    Tell Claude what you want to plan. It asks one question at a time and shows an example answer under each.

    You sayI want to plan a website before I build it.

  2. Get six documents

    Stuck on a question? Ask for a suggestion and edit it. Each document builds on the ones before it.

    You saySuggest.

  3. Review the deck

    Everything arrives as a letter-size deck with your logo and name on it. Ask for changes until it is right.

    You sayChange Doc 2: we use Square, not Stripe.

  4. Approve and save the PDF

    Hand the PDF to your freelancer, agency, team or AI coding tool, and sign off stage by stage.

    You sayApproved.

Six documents. Each one builds on the last.

A claim only counts if you can check it. Every document ends with a short check for you to run before you approve it.

  1. Product requirementsWhat does it do, feature by feature?
  2. Technical requirementsWhat tools does it run on, decided once?
  3. App flowWhich page comes next, and where do people land when something goes wrong?
  4. Design briefYour real colours, fonts and tone, so every screen looks like you.
  5. Backend schemaWhere does your data live, and who can see it?
  6. Implementation planWhat gets built in what order, and where do you sign off?
3
Document 3 of 6App flowHow people move through it

Tidewater Pottery Studio, version 1

Book a classVisitor or member
  1. 1Class list
  2. 2Class details
  3. 3Choose a seat
  4. 4Pay
  5. ✓Confirmed

When something goes wrong

  1. !Payment fails
  2. Back to checkout, reason shown
  3. ↻Seat held for 15 minutes
Before you approve, checkDead ends. Walk each journey as one of your own customers. Every red path should still let the person finish what they came to do.

A page from the sample plan that ships with the kit, for an invented pottery studio.

Start free. Add help only if you want it.

The same six documents at every step. What changes is how much of the work you do yourself.

The free GitHub kit

On your own

FreeMIT licensed

For people comfortable running one command in a terminal with Claude Code.

  • Interview, six documents, deck and PDF
  • Use it on as many projects as you like
  • Includes a full worked example
$ npm install
> /plan-project
View on GitHub

Done with you, or done for you

With an expert

Felipe Suarez has delivered web and e-commerce projects for global companies for over 15 years. Bring him in at the point you need him.

  • Plan reviewHe reviews your six documents with you on a call and sends written fixes.
  • Planning sprintHe runs the interviews with you and your team.
  • Managed projectHe plans, builds and manages it for you and your team.
Book a call

A short form first, so the call starts prepared.

Made by the person who used to hold these projects together.

Felipe Suarez spent years as the project manager between the people who wanted something built and the people building it. The projects that went well started with the same thing: someone had written down what was being built, how it worked and who could see what.

The Plan-First Kit turns that habit into a guided conversation, so you can do it yourself, or bring him in when the stakes are high. felipesuarez.com

  • 15+ yearsdelivering web and e-commerce projects
  • 6.5 yearsleading global e-commerce operations at VMware
  • Magento, Digital River, CleverBridgeplatforms worked across

Before you start

Do I need to know how to code?

No. Every question is in plain English and comes with an example answer. If you get stuck, ask Claude to suggest something and edit it.

Does the kit build my website or app?

No. It produces the six documents your builder needs before they start. Hand the PDF to a freelancer, an agency, your own team or an AI coding tool.

What is the difference between the free kit and the paid edition?

The same six documents come out of both. The free GitHub kit runs in Claude Code on your computer and needs a terminal. The Project and Skill Edition runs inside Claude with nothing to install, and includes a setup guide.

What do I need to use it?

A Claude account. The Project and Skill Edition needs a plan that includes Projects or Skills, so check Anthropic’s site for the current options. Claude is not included with the kit.

Can I get help if I’m stuck?

Yes. Book a call for a plan review, a planning sprint where Felipe runs the interviews with your team, or a managed project where he plans, builds and manages it for you.

Is it safe to use for a real business?

Planning needs no passwords, card numbers or customer data, so never paste them into the chat. The kit asks about what you will store and who should see it, but it is not legal advice. For anything regulated, check with a professional.

Plain-English notes on planning before you build.

Short, practical lessons on planning websites, portals and apps without the jargon. Unsubscribe any time.

Example form. Connect it to your email service before launch.

Write it down once. Build it right.

Start with the free kit, or get the no-terminal edition. If the project matters, bring in someone who has done this for years.