Peace & AI

PRODUCTDEV KIT

Your app, worked out before it is built.

What goes in the first version, how it works screen by screen, and a spec your builder can follow. Open the kit in Claude or Codex and ask “What do I do next?”

Before you start: you need Claude Code or Codex (from a Claude or ChatGPT subscription).

Already have a brief, sketches or a business plan (from the Biz Dev kit, say)? Put them in the kit’s my-documents folder before you start. Your agent reads them first and only asks what’s missing.

Download productdev kit

v0.2.0 · ZIP · 48 KB · 2026-10-10

HOW TO START

Three steps, then your agent takes over.

  1. Get Claude or Codex

    Either works. Both need a paid plan.

    Claude

    The desktop app. Pro, Max, Team or Enterprise.

    MacWindows

    Codex

    Comes with the ChatGPT desktop app.

    Get ChatGPT
  2. Download and unzip the kit

    Mac: double-click the zip. Windows: right-click it, then Extract All.

    Keep the productdev-kit folder somewhere easy, like Documents. Your work will live there.

  3. Open it and ask

    Claude: the Code tab → Local → Select folder → productdev-kit.
    Codex: open the productdev-kit folder as your project.

    If asked whether you trust the folder, say yes. Then type:

    What do I do next?

WHAT YOU WORK OUT

One question at a time, in plain words.

  • Your app

    What it does for your business, and what it replaces.

  • Who uses it

    Customers, you and your staff, and what each must be able to do.

  • The first version

    The smallest app that proves the idea. The rest waits, written down.

  • How it works

    Every journey and screen, including what happens when things go wrong.

  • A mock-up to try

    Click through it, then watch three to five real people use it.

  • The build spec

    Exactly what to build, and a numbered list of checks it must pass.

  • Building it

    Hand it to the webdev kit, which builds from the spec.

  • The next version

    After launch: what happened, and what to build next.

It keeps your place in PROGRESS.md: stop any time, pick up later. Your work stays on your computer, in the kit’s business folder (where your bizdev kit plan goes too, if you made one).

WHERE IT FITS

Three kits, one folder passed along.

  • bizdev kit

    The business: customers, offer, numbers, brand.

  • productdev kit

    The app: what it does, the first version, the spec. You are here.

  • webdev kit

    The build: your app, online, on your own domain.

No business plan yet? Start here anyway; your guide asks what it needs.

WHAT IT COSTS

Nothing extra.

Claude Code or CodexComes with a Claude or ChatGPT subscription
Anything elseNothing. No other accounts, nothing to install. (Building and running the app has small costs of its own: see the webdev kit.)

FOR THE CURIOUS

What is in the kit.

Instructions your agent follows to guide you, and four skills it reads when the work calls for them: product requirements (who, what, and what goes first), user journeys and screens, mock-ups and testing them with people, and the build spec with its gap check.

Why test with only a handful of people: most of what confuses users shows up in the first five, and several small rounds beat one big one (Nielsen Norman Group).

Your requirements and spec are written in the format the webdev kit reads. The spec says what the app does, never how: the builder makes the technical choices.

Updates look after themselves. Once a day your agent checks here for a newer kit and installs it when you say yes. The download is checked against its published fingerprint; your work and progress are never touched.

WHEN YOU ARE READY

Then build it with the webdev kit.

It reads your spec and builds the first version from it, checking each item on the list. No questions twice.