Every screen the reworked onboard shows a user, from a bare repo to shipping a feature. It announces itself, shows the project's AIDD setup up front, then walks the official flow one step at a time. Mockups for review — not final wording.
the common case — code already here, so memory comes first
█████╗ ██╗██████╗ ██████╗ +██╔══██╗██║██╔══██╗██╔══██╗ +███████║██║██║ ██║██║ ██║ +██╔══██║██║██║ ██║██║ ██║ +██║ ██║██║██████╔╝██████╔╝ +╚═╝ ╚═╝╚═╝╚═════╝ ╚═════╝ + AI-Driven Development + +👋 I'll walk you through AIDD step by step — nothing runs until you reply. + +Your AIDD setup: + AI tools claude ⚠ + Plugins aidd-context · pm · refine · dev · vcs ✓ + Memory ✗ not set up yet + +You already have code — AIDD just has no memory of it yet. + +⚠ Let's teach the AI about your project first. Every command relies on it. + → Type [1] to generate your project memory. see the flow [m]+
Foundations — step 1 of 2 + + project memory scan your existing code into a memory bank the AI reads + (architecture, testing, conventions — so commands don't guess) + +👉 Type [1] to start. what's this [?] + +No "design the stack" step — your stack already exists, so it's skipped.+
✓ Project memory saved. + +Foundations — step 2 of 2 + + connect it to the AI wire the memory into claude's context file (CLAUDE.md) + so it loads automatically every session + +👉 Type [1] to start. skip [s]+
empty repo — design the stack first, then memory
█████╗ ██╗██████╗ ██████╗ +██╔══██╗██║██╔══██╗██╔══██╗ +███████║██║██║ ██║██║ ██║ +██╔══██║██║██║ ██║██║ ██║ +██║ ██║██║██████╔╝██████╔╝ +╚═╝ ╚═╝╚═╝╚═════╝ ╚═════╝ + AI-Driven Development + +👋 I'll walk you through AIDD step by step — nothing runs until you reply. + +Your AIDD setup: + AI tools claude ⚠ codex ⚠ + Plugins aidd-context · pm · refine · dev · vcs ✓ + Memory ✗ not set up yet + +⚠ Your AI tools have no project memory yet. + → Type [1] to set up the foundations. see the flow [m]+
Foundations — step 1 of 3 + + design your tech stack pick your technologies & architecture + (saved to INSTALL.md — everything builds on it) + +👉 Type [1] to start (asks you a few questions). skip [s] · what's this [?]+
✓ Tech stack set. + +Foundations — step 2 of 3 + + save project knowledge generate the memory files the AI reads + (so commands work with real context, not guesses) + +👉 Type [1] to start. skip [s]+
✓ Project knowledge saved. + +Foundations — step 3 of 3 + + connect it to the AI wire the memory into each AI tool's context file + (CLAUDE.md, AGENTS.md — so it loads automatically) + +👉 Type [1] to start. skip [s]+
foundations ready — the official flow
█████╗ ██╗██████╗ ██████╗ +██╔══██╗██║██╔══██╗██╔══██╗ +███████║██║██║ ██║██║ ██║ +██╔══██║██║██║ ██║██║ ██║ +██║ ██║██║██████╔╝██████╔╝ +╚═╝ ╚═╝╚═╝╚═════╝ ╚═════╝ + AI-Driven Development + +👋 Welcome back. + +Your AIDD setup: + AI tools claude ✓ + Plugins aidd-context · pm · refine · dev · vcs ✓ + Memory aidd_docs/ · 8 files synced ✓ + +All set. Build your next feature — the AIDD flow: + + brainstorm turn a vague idea into something precise + │ + spec the contract of what to build (optional) + │ + plan break it into phases + │ + implement build it, phase by phase + │ + assert check it behaves + │ + review verdict before shipping + │ + commit save the work + │ + pull request ship it + +Run it: + [1] Walk it with me — one step at a time, I explain each. + [2] Let SDLC drive the whole flow from one request. + map [m] · explore all commands [?] · stop [x]+
Your first feature — step 1 of 8: Brainstorm. + + What: turn your rough idea into something precise enough to build. + Why: a fuzzy idea makes every next step guess. + +👉 Type [1] to start. whole flow [m] · skip to spec [s]+
Feature flow — step 4 of 8: Implement. (brainstorm ✓ · spec ✓ · plan ✓) + + What: build the plan, phase by phase. + Why: small verified phases beat one big leap. + +👉 Type [1] to start. whole flow [m] · back [<]+
AIDD feature flow: + + brainstorm → spec* → plan → implement → assert → review → commit → PR + (* optional) + + back [<]+
The map view is the same canonical sequence shown as a standalone cookbook — one source, two doors.
the flow tracks your progress
🔍 Healthy — unsaved changes in progress. + + Flow: brainstorm ✓ · spec ✓ · plan ✓ · [implement] · assert · review · commit · PR + +👉 Next: finish your changes [1] + review them [2] · both [OK] · more [?]+
🔍 Healthy — changes ready to review. + + Flow: brainstorm ✓ · spec ✓ · plan ✓ · implement ✓ · assert ✓ · [review] · commit · PR + +👉 Next: review your changes [1] + ship them [2] · both [OK] · more [?]+
🔍 Healthy — reviewed, ready to ship. + + Flow: brainstorm ✓ · … · review ✓ · commit ✓ · [pull request] + +👉 Next: open a pull request [1] (you run this one yourself) + more [?]+
every ⚠ says what's wrong and the next action
👋 Welcome back. + +Your AIDD setup: + AI tools claude ✓ codex ⚠ + Plugins aidd-context · pm · refine · dev · vcs ✓ + Memory aidd_docs/ · 8 files synced ✓ + +⚠ codex is installed but its memory isn't wired (no AGENTS.md). + → Type [1] to wire it. build a feature instead [m]+
👋 Welcome back. + +Your AIDD setup: + AI tools claude ⚠ + Plugins aidd-context · pm · refine · dev · vcs ✓ + Memory aidd_docs/ · 8 files synced ✓ + +⚠ claude's memory block drifted from the canonical shape. + → Type [1] to re-wire it.+
🔍 Healthy — but no tests yet. + + Flow: ready for new work. + +⚠ This project has no tests, so changes aren't protected. + → Next: add tests [1] + start new work [2] · improve the project [3] · explore [?]+
[?] opens the full view — ids, tiers, reasons
Details — + + 1. finish your changes aidd-dev:02-implement (it will ask you a few questions) + 2. review your changes aidd-dev:05-review (runs on its own) + + AI tools claude ✓ + Plugins aidd-context · pm · refine · dev · vcs ✓ + Memory aidd_docs/ · 8 files synced ✓ + + explain <n> · recap · stop · back [<]+