Where Findy is
You are here: Plan the build phases (/build-pack) It is the next thing to run.
1 feature(s) are planned and none has been through /build-pack yet. Nothing before it was skipped. One step ran ahead of its place: Plan the animations. The work stands; the steps before them still need doing.
15 features listed, 1 written up yet. Click any station for what it does.
Done Not yet You are here Skipped: should have happened by now Ran ahead of its place Black: happens once Blue: repeats for every feature
1 Set up Once, ever
Create the folder (init.sh): Done. A setup script typed into the terminal. It makes the project folder and puts the first handful of commands in it. Run once, ever.
Create the folder
(init.sh)
Write the product spec (/spec-writer): Done, first ran 2026-08-23. Produces the spec: the document that wins every argument about what the product is, plus a short lookup version of it.
Write the product spec
(/spec-writer)
Set up the project (/bootstrap-project): Done, first ran 2026-08-26. Writes the instructions every session reads, the bookkeeping files, the design folder, the list of features, and installs the rest of the commands.
Set up the project
(/bootstrap-project)
2 Plan one feature For each feature, starting here
Lock the architecture (/pre-pack-architectural-surface): Done, first ran 2026-09-02. Walks one feature and everything it leans on, finds every architecture decision nobody has made yet, and puts them to you one at a time. The next step refuses to start without its receipt, on purpose.
Lock the architecture
(/pre-pack-architectural-surface)
Write the feature spec (/feature-plan): Done, first ran 2026-09-03. Writes four files for the feature: what it does, the shapes its data takes, every state each screen can be in (loading, empty, no signal, gone wrong), and how you know it passed. Screen designs need those states and cannot invent them.
Write the feature spec
(/feature-plan)
first feature only, then straight on
Choose the design tool (/design-platform): Done, first ran 2026-08-29. Records which tool draws the screens. Every design command reads that record. Once, and again only if you switch tools.
Choose the design tool
(/design-platform)
Load the design system (/design-system-push): Done, first ran 2026-08-29. Puts your colours, lettering and motion into the design tool before its first drawing. Skip it and the tool applies its own defaults, and you meet them as finished screens. Runs again whenever your colours or lettering change. Can run alongside the screen list; neither reads the other.
Load the design system
(/design-system-push)
List every screen (/screen-inventory): Done, first ran 2026-08-30. Lists every screen the whole app needs, once, from the product spec. The method allows that list to be made before the first feature is written up, so design is never left waiting; it is not allowed to be the only thing that runs. Then, as each feature is written up, its states and fields are added to the same list, and that feature's screens are drawn from it.
List every screen
(/screen-inventory)
Map the screen flow (/screen-inventory --flow): Done. Every screen as a grey block with the real words in it and an arrow off every tappable thing. The first moment the app can be looked at rather than read as a list, and the cheapest moment to move something.
Map the screen flow
(/screen-inventory --flow)
Draw the screens (in the design tool): Done. The design tool draws this feature's screens, from the screen list and the states in the feature spec. Not a command of this method.
Draw the screens
(in the design tool)
Check the designs (design-check): Done. Reads the designs against the screen list and writes one report. That report saying PASS is the single thing that lets anybody write a line of code.
Check the designs
(design-check)
3 Build it The same feature
Plan the build phases (/build-pack): You are here. Turns the feature into numbered build phases and stops. It writes no code. Several features can be planned and built side by side once their groundwork is done.
YOU ARE HERE
Plan the build phases
(/build-pack)
Plan the animations (/animate): Ran ahead, first ran 2026-09-01. Decides what has to move before any artwork is made, because a flat picture cannot be taken apart afterwards. Visual phases only.
Plan the animations
(/animate)
RAN AHEAD
Preflight the design (/design-preflight): Not yet. Screens the phase against the design system and lists what artwork it needs. Visual phases only; needs the build plan first.
Preflight the design
(/design-preflight)
Generate the assets (/asset-forge): Not yet. Makes the artwork the preflight flagged as missing. Runs only when something was flagged.
Generate the assets
(/asset-forge)
Build the code (/build-team): Not yet. A guide and a builder work through the phase. Code and tests.
Build the code
(/build-team)
Try it on the phone (/feel-check): Not yet. You hold the phone and say whether it feels right. Between visual phases.
Try it on the phone
(/feel-check)
4 Check and close Eight checks, then close the session
Code review (/pr-review-toolkit:review-pr): Not yet. Check 1 of 8. Reads the code.
Code review
(/pr-review-toolkit:review-pr)
Review the diff (/review-diff): Not yet. Check 2 of 8. Reads the diff, which is the exact set of lines that changed.
Review the diff
(/review-diff)
Security review (/security-review): Not yet. Check 3 of 8. Reads the change for security holes.
Security review
(/security-review)
Audit the diff (/diff-audit): Not yet. Check 4 of 8. Reads the change against what was meant.
Audit the diff
(/diff-audit)
App safety audit (app-safety-audit.py): Not yet. Check 5 of 8. Reads the finished app for what could go wrong.
App safety audit
(app-safety-audit.py)
Test the tests (test-strength.py): Not yet. Check 6 of 8. Breaks the code on purpose and checks the tests notice.
Test the tests
(test-strength.py)
Find temporary code (temp-code.py): Not yet. Check 7 of 8. Refuses while any temporary shortcut is undeclared or overdue.
Find temporary code
(temp-code.py)
Visual QA on a phone (/visual-qa, plus a phone test): Not yet. Check 8 of 8, and the only one that opens the running app. The other seven all come back clean on a build that launches to a blank screen.
Visual QA on a phone
(/visual-qa, plus a phone test)
Close the session (/close): Runs every session, first ran 2026-08-24. Files what was learned, updates the bookmarks, saves and uploads. Then back to stage 2 with the next feature. Since September 2026 it asks the guide for the next step rather than deciding itself.
Close the session
(/close)
5 Launch Once every feature is done
both at the same time
Pass the security gate (/security-floor): Not yet. The security floor for the app itself. Blocking before any real user.
Pass the security gate
(/security-floor)
App store preflight (/store-preflight): Not yet. App-store readiness for Apple and Google. Blocking before submission.
App store preflight
(/store-preflight)
After stage 4 the route goes back to stage 2 with the next feature, until every feature is done; then stage 5.
Any time, off the route
(/implementation-guide) (/secure-machine) (/setup-tools) (/guardian) (/diary)
How this page was made. Every mark was worked out from the project's own files on 3 September 2026: the stage from the session-start check, which commands ran from the session records, and steps that are not commands from the one file each of them leaves behind. Nothing is remembered. If this page and a bookmark file disagree, believe this one.