ToppingOut03 · Your repoYour repo
Every folder Topping Out adds, and what makes it.
Not in hereYour product's code. It’s built in its own copy and reaches main only by pull request.
Two repos? .claude/ and foreman/ go in the records repo.
.claude/
Inside
- the 30 skills (see the skills pages)made by: the install
- the 13 agents (see the skills pages)made by: the install
skills/
- Holds
- The 30 skills (see the skills pages).
- Made by
- Installed
agents/
- Holds
- The 13 agents (see the skills pages).
- Made by
- Installed
scripts/
Inside
- sends the independent review to another AI company's sessionmade by: the install
- the voice add-on (optional)made by: the install
cross-review-dispatch.mjs
- Holds
- Sends the independent review to another AI company's session.
- Made by
- Installed
speak.ts, speak-setup.ts, bootstrap-env.ts
- Holds
- The voice add-on (optional).
- Made by
- Installed
foreman/
- Holds
- Everything the method owns.
Inside
- the method itself: METHOD.md, RULES.md, the two playbooks, BUILDER-PROFILES.md, templates/ (every document the method writes)made by: the install
- your gates, shell, test adapter, remotesmade by: you, at setup
- how this repo's tests are run and readmade by: you, at setup
- IDEA-<date>_<slug>.mdmade by: /f-sketch
- README.mdthe index: ready, deferred, ideas
- ready/BLUEPRINT-<date>_<slug>.mdmade by: /f-blueprint, checked by /f-plancheck
- deferred/plans put off before any build
- one folder per projectmade by: /f-schedule
- PROJECT.mdthe plan cut into jobs
- tickets/TICKET-<nn>.md, one per job
- BOARD.jsonthe board's data (the only place job state lives)made by: /f-board
- board.htmlthe board page, generated from BOARD.jsonmade by: /f-board
- JOB_<date>_<slug>.md: the job in progresswhen: work order 1
- closed jobs, filed by monthmade by: /f-signoff
- AGENT-HANDOFF-<date>-job-<N>-<slug>.md, its site-walk answer key, and OPENER-JOB-<N>.txt (the next session's opener) end of each job with a next job
- lessons that outlive a jobmade by: /f-card, /f-signoff
- logbook_index.mdthe card catalogue: every live card, its type and topic, the countswhen: updated with every card
- logbook_links.mdhow cards relate: one supersedes, refines or contradicts anotherwhen: updated with every card
- entries/
- insights/INSIGHT cards: a lesson or gotcha (why)
- methods/METHOD cards: a repeatable way of doing something (how)
- builds/BUILD cards: what a job built
- archived/older cards moved out once there are more than 250made by: /f-archive
- sessions/saved copies of past sessions
- ARCHIVE-SYSTEM.mdhow cards are moved to the archive
- archive_cards.pythe script that moves them (with its test)
- README.mdwhich skill reads or writes which part
- the job file, by size: JOB-QUICK.md, JOB-STANDARD.md, JOB-FULL.mdmade by: the install
- only while a closed job still owes its end-game stepsmade by: /f-signoff
- which Topping Out version is installed, and whenmade by: the install
method/
- Holds
- The method itself: METHOD.md, RULES.md, the two playbooks, BUILDER-PROFILES.md, templates/ (every document the method writes).
- Made by
- Installed
REPO-PROFILE-<product>.md
- Holds
- Your gates, shell, test adapter, remotes.
- Made by
- You, at setup
test-adapter.sh
- Holds
- How this repo's tests are run and read.
- Made by
- You, at setup
ideas/
- Holds
- IDEA-<date>_<slug>.md.
- Made by
- /f-sketch
blueprints/
Inside
- README.mdthe index: ready, deferred, ideas
- ready/BLUEPRINT-<date>_<slug>.mdmade by: /f-blueprint, checked by /f-plancheck
- deferred/plans put off before any build
projects/<slug>/
- Holds
- One folder per project.
- Made by
- /f-schedule
Inside
- PROJECT.mdthe plan cut into jobs
- tickets/TICKET-<nn>.md, one per job
- BOARD.jsonthe board's data (the only place job state lives)made by: /f-board
- board.htmlthe board page, generated from BOARD.jsonmade by: /f-board
jobs/
- Holds
- JOB_<date>_<slug>.md: the job in progress.
- Made by
- work order 1
Where a job touches it
completed-jobs/<YYYY-MM>/
- Holds
- Closed jobs, filed by month.
- Made by
- /f-signoff
Where a job touches it
handovers/
- Holds
- AGENT-HANDOFF-<date>-job-<N>-<slug>.md, its site-walk answer key, and OPENER-JOB-<N>.txt (the next session's opener) end of each job with a next job.
Where a job touches it
logbook/
- Holds
- Lessons that outlive a job.
- Made by
- /f-card/f-signoff
Inside
- logbook_index.mdthe card catalogue: every live card, its type and topic, the countswhen: updated with every card
- logbook_links.mdhow cards relate: one supersedes, refines or contradicts anotherwhen: updated with every card
- entries/
- insights/INSIGHT cards: a lesson or gotcha (why)
- methods/METHOD cards: a repeatable way of doing something (how)
- builds/BUILD cards: what a job built
- archived/older cards moved out once there are more than 250made by: /f-archive
- sessions/saved copies of past sessions
- ARCHIVE-SYSTEM.mdhow cards are moved to the archive
- archive_cards.pythe script that moves them (with its test)
- README.mdwhich skill reads or writes which part
Where a job touches it
templates/
- Holds
- The job file, by size: JOB-QUICK.md, JOB-STANDARD.md, JOB-FULL.md.
- Made by
- Installed
ENDGAME-PENDING.md
- Holds
- Only while a closed job still owes its end-game steps.
- Made by
- /f-signoff
Where a job touches it
INSTALL-RECEIPT.txt
- Holds
- Which Topping Out version is installed, and when.
- Made by
- Installed
work-sessions/<Month-Year>/Work-<date>/
- Holds
- One folder per working day.
Inside
- when: before work order 1
- when: before work order 1
- when: each work order
- test and gate outputs, from the first run and each work order
- when: the two reviews
- when: before the pull request
- when: after the merge
Where a job touches it
JOB-<N>-SITE-WALK-ANSWERS.md, JOB-<N>-SCOPING.md, JOB-<N>-PLAN.md
- Made by
- before work order 1
Where a job touches it
JOB-<N>-BUILDER-PREFLIGHT.txt and its -REPORT.md
- Made by
- before work order 1
Where a job touches it
JOB-<N>-WORK-ORDER-<m>.txt, -REPORT.md, -REVIEW.md
- Made by
- each work order
Where a job touches it
captures
- Holds
- Test and gate outputs, from the first run and each work order.
JOB-<N>-LENS-INSPECTION.md, blind-pack/ (the outside review's brief)
- Made by
- the two reviews
Where a job touches it
JOB-<N>-ACCEPTANCE-LEDGER.md, the PR body
- Made by
- before the pull request
the dev report, JOB-<N+1>-NEXT-TICKET-DECISION.md, the next session's brief (at a topping out: TOPPING-OUT-REPORT.md, NEXT-HEADS.md)
- Made by
- after the merge
.claude/skills/deep/, deepagents-ref/, .mcp.json
- Holds
- The Deep Agents add-on (only on yes); its agent skeleton (src/agent/, tests/ …) only for a new project.
- Made by
- /f-setup
scratch/
- Holds
- Working files (plan checks, councils, voice) and names-kept-out.txt + names-allowed.txt (the names the records push checks for); keep it in .gitignore.
01
You say go
- What appears
- The job marked started.
- Where
foreman/projects/<slug>/BOARD.json.
Show in Folders →
02
Before work order 1
- What appears
- The site-walk answers, the builder pre-flight and its report, the scoping, the plan.
- Where
- The day folder (
JOB-<N>-SITE-WALK-ANSWERS.md,JOB-<N>-BUILDER-PREFLIGHT.txt,JOB-<N>-SCOPING.md,JOB-<N>-PLAN.md).
Show in Folders →
03
Work order 1
- What appears
- The job file, plus the first test and gate captures.
- Where
foreman/jobs/JOB_<date>_<slug>.md; the day folder.
Show in Folders →
04
Each work order
- What appears
- The work order, the builder's report, the foreman's review.
- Where
- The day folder (
JOB-<N>-WORK-ORDER-<m>.txt,…-REPORT.md,…-REVIEW.md).
Show in Folders →
05
The two reviews
- What appears
- The lens inspection, then the brief for the outside reviewer and the adjudication.
- Where
- The day folder (
JOB-<N>-LENS-INSPECTION.md,blind-pack/).
Show in Folders →
06
Before the pull request
- What appears
- The acceptance ledger and the PR body.
- Where
- The day folder.
Show in Folders →
07
After the merge
- What appears
- The job file moves; the lessons become Logbook cards; the end-game lock opens.
- Where
foreman/completed-jobs/<YYYY-MM>/,foreman/logbook/,foreman/ENDGAME-PENDING.md.
Show in Folders →
08
The end game
- What appears
- The dev report, the next-ticket decision, your confirmation, the board close, the handover and the next session's opener; the lock clears; the records are pushed (at the board's head: the close, the topout, the topping out report and the next heads instead,
METHOD.md§11b). - Where
- The day folder;
BOARD.json;foreman/handovers/(OPENER-JOB-<N>.txtbeside the handover).