Developer path

Product Package standard

What the final Developer assessment contains and how to prepare it.

The Product Package is the final assessment of the Developer path. It is one folder in git and one presentation. It proves that you own a product from end to end.

The eight parts

# Part What it must show
1 Current state What exists today, honestly: what works, what is a plan, what is missing. Use FOUND, NOT FOUND and PLANNED.
2 Product website A public page that explains the product, who it is for and how to start. Source in git.
3 Brand name The name, the one-sentence promise, the brand sheet and why you chose it.
4 Product and service catalogue Your Product Catalogue and a catalogue entry for each product or service.
5 Roadmap 4 to 8 epics in order, with dates, reasons and an out-of-scope list.
6 Demo A five-minute walk-through of the real journey with fake data.
7 Next-version mockups Three or more mockups, each linked to an epic.
8 Evidence of complete epic management History of your epics, moved dates with reasons, decision log, weekly notes, closed milestones and AI-use notes.

Folder layout

product-package/
  README.md              start here: one paragraph and links
  01-current-state.md
  02-website/            link and source
  03-brand/              brand sheet
  04-catalogue/          master, orbital, android, tech, entries
  05-roadmap/            epics and order
  06-demo/               link or script
  07-mockups/
  08-evidence/           notes, decision log, ai-use

The presentation

15 minutes plus questions:

  1. 1 minute: the product and the customer.
  2. 2 minutes: current state.
  3. 3 minutes: demo.
  4. 4 minutes: roadmap, order, risks and what you chose not to do.
  5. 2 minutes: catalogue and brand.
  6. 1 minute: how you used AI.
  7. 2 minutes: next-version mockups.

Then answer questions without notes.

What reviewers look for

  • Is it your thinking?
  • Does it cover the whole product, not just one part?
  • Can agents build from your epics?
  • Is it honest about what is not finished?

Rules

  • Use fake data in the demo and in screenshots.
  • No secrets in the folder.
  • Disclose AI use in 08-evidence/ai-use.md.
  • Every claim is something you verified.

Key points

  • Eight parts, one folder, one presentation.
  • Honesty beats polish.
  • Score yourself with the rubric before you present.

Back to the library