1. What pogoprompt does
In the early pilot, you describe one web-app workflow in ordinary words. pogoprompt asks the questions a good developer would ask, then writes the plan pack you review before handing it to Claude Code.
Legacy saved plans only.The remaining build-plan and guidance material in this reference applies only to eligible legacy saved plans. Build plans — a website, a phone app, or a personal tool that runs on your own computer — end in a full pack of build files tailored to your coding tool. Guidance plans — research, a study guide, and the like — end in one focused brief instead.
pogoprompt plans and hands off, and that is all it does. It does not build, run, host, or deploy anything, and the plan is a starting point you should read before you rely on it.
2. Starting with your idea
Everything starts in the idea box. A sentence or two is enough; more detail is welcome but never required.
Legacy saved plans only.Beside the box you pick what your idea should end in — a website, a phone app, a personal tool, research, and so on. If you leave it alone, pogoprompt reads your idea and picks for you. When it does, you see a plain notice saying which one it chose, and you can change it. A one-line note under the choice always says what that category ends in.
Legacy saved plans only.Choosing a website, a phone app, or a personal tool also offers a few refinement chips — the sort of website, app, or tool you mean. They sharpen the plan; picking none is fine.
3. Boost
Boost is the optional control beside the idea box. It rewrites what you typed into a sharper version of the same idea before any planning starts. You always see the result and can keep it, edit it, or ignore it.
Boost may also ask you a few short questions first, when answering them would make the rewrite meaningfully better. If you are signed in, you can save a boosted idea and reuse it later.
Boost is included — it costs no credits — with sensible daily limits so it stays available to everyone.
4. Choosing your builder
New early-pilot plans are prepared for Claude Code. You review the pack before handing it to your own Claude Code account.
Legacy saved plans only.Your builder is the coding tool that will do the building. The whole plan is written for the one you pick: its file layout, its conventions, and the way it likes to be instructed. Guidance plans ask for a tool in the same place, for the same reason.
Legacy saved plans only.The list comes in two groups. Guided coding agents work inside your own project folder, so they can also receive step-by-step build guidance — an optional extra download called skills. All-in-one app builders work in the browser and receive the plan itself.
Legacy saved plans only.Picking one now is not permanent: a finished build plan can be re-tailored for a different builder later — see Changing a finished plan.
5. How your app earns
For the web-app workflow in this pilot, one early step asks how what you are building will make money — up to three ways, or none at all if you would rather not decide yet. It takes a moment and costs nothing.
It is asked before the questions start on purpose. Money touches accounts, access, and what people can do for free, so deciding it up front keeps every later answer consistent with it. Your choice is what the Payment plan file is written from.
6. Plans and credits
The early pilot is a one-time purchase for one project. Open Settings → Plans for the current offer before starting the interview.
Legacy saved plans only.Subscriptions are flat. Each billing period includes a set number of credits, which reset at the start of the next one and do not roll over. Credits you buy outright never expire. When your balance reaches zero the paid actions simply pause until it is topped up — there is never an overage charge and never a surprise bill. There is a one-time plan too, if a subscription is not what you want.
Legacy saved plans only.What each option includes, and what it costs, is shown in Settings → Plans. You can change or cancel a subscription any time through the billing page in Settings → Account.
7. The planning interview
This is the heart of it. pogoprompt asks you questions in small batches — one to four at a time, shown one after another. Each question offers three suggested answers plus Something else, where you can write your own. Arrow keys move between the suggestions and the number keys 1–4 pick one.
Nothing is sent while you look around: moving, choosing, and typing change nothing until you press Send answers, which commits the whole batch at once. If two of your answers pull in opposite directions, you get a card that shows the clash and lets you settle it. Before you generate, you can reopen an earlier batch and change an answer.
The interview never runs past 20 answers in total, and it ends when pogoprompt has what it needs. It cannot be turned off: a plan built from no answers at all would defeat the point of asking.
8. Design inspiration and references
Once the interview is complete, an optional panel lets you point at the look you want: a website whose style you like, any brand or design rules you have to follow, and up to five reference files of your own. All of it is optional and none of it costs a credit.
This shapes the Design direction file and nothing else. It never changes your features, your answers, or any other decision in the plan. Your reference files stay private to your account.
9. Generating your pack
Finishing the interview does not start the writing. Generate is a separate button you press when you are ready; that is the moment the plan's credits are spent. You then watch the files being written, one at a time.
A build plan is built around six main documents:
- Product promise — what the app is, who it is for, and what it will not do.
- Feature plan — every feature and how you will know it works.
- Build order — the work broken into phases, in the order to do them.
- Builder instructions — the standing rules your coding tool follows while it builds.
- Design direction — how it should look and feel.
- Payment plan — how the app earns, built from the choice you made earlier. A plan that charges nothing does not carry this file.
The pack you download carries a few supporting files besides these — checklists and hand-off steps your coding tool uses as it builds, so seeing more than six files in it is normal.
Legacy saved plans only.A guidance plan comes out as one focused brief for the subject you asked about, rather than a set of build files.
10. Getting the plan into your tool
For this early pilot, one project ends in a complete pack you review and then hand to Claude Code. You can download and keep the delivered files.
Legacy saved plans only.Eligible legacy saved plans may also show these additional delivery routes:
- Copy — the whole plan to your clipboard, ready to paste.
- Download — a zip of the files.
- Save to a folder — write the files straight into a folder you choose, in supported browsers.
- Open in your builder — for the browser-based builders, opens them with the plan in hand.
- Command line — a one-time code you paste after
npx pogopromptto pull the plan into the folder you are standing in. - Send to GitHub — with your explicit permission, creates a private repository in your own GitHub account and puts the files in it.
- Let your builder fetch your plans — an advanced connection you set up once; after that, a coding tool that supports it pulls this plan — and any plan you save later — straight into a project folder, without you exporting anything.
Legacy saved plans only.If you chose a guided coding agent, the panel also offers the optional skills and Autorun download: extra files that teach your tool how to work through the plan phase by phase.
11. The Drift-Proof score — Legacy saved plans only
Every build plan carries a Drift-Proof score out of 100. It measures one thing: how well the plan protects itself against a build wandering away from what you asked for — whether the promises are specific, whether the features say how you will know they work, whether the boundaries are drawn.
It grades the plan, not the app. A high score does not mean your finished app will work, and no score can tell you whether the idea is a good one. Guidance plans carry no score at all.
12. Changing a finished plan — Legacy saved plans only
Two actions sit on a finished build plan. Rebuild writes it again from the same answers. Use a different builder re-tailors it for another coding tool. Each costs 50 credits from the same balance a new plan draws on. Both are for build plans only.
If you do not have enough credits for one of them, nothing is lost: the finished plan stays exactly where it is, and you can still open, copy, and download it.
The sidebar keeps your work in two lists. In progress holds drafts you have not generated yet; a draft you never come back to expires 30 days after your last activity on it. Ready holds finished plans, which stay saved up to the number your plan allows.
13. Account and settings
Everything about your account lives in one place — the Settings dialog, opened from your name at the bottom of the sidebar. Account shows your email, your current plan, the billing page, and sign out. Plans shows the one-project pilot. Existing subscribers can manage billing there.
The same dialog holds How it works, a short tour of the product, a FAQ, and Theme for light or dark.Legacy saved plans only.The credential for the command line is in Account, next to a legacy saved plan's details.
14. Still stuck?
Write to contact@pogoprompt.ai — a real person reads it, and mail sent there receives a reply within two business days. Tell us what you were doing and what happened instead; that is usually enough to sort it out in one round.
The Settings dialog's How it works and FAQ sections cover the short version of this page, without leaving your workspace.