🤖 Rewrite implementation skill and Athanor for lean building

The implementation skill now states the lean loop: attack the plan against the code before building, build phases in blocks with a cheap gate between them, test and review once per phase, one fix pass, stop. Harness mechanics, model observations and the run-log template move to references with dated, sourced claims. The Athanor becomes a build furnace pinned to claude-opus-5-5: one phase per turn, no planning, no plan attack, no self-review. It no longer preloads superpowers; those skills stay available as tools.
2026-10-05 22:12:31 +02:00
parent 08e22a731d
commit e51520723c
5 changed files with 283 additions and 72 deletions
@@ -0,0 +1,63 @@
+# Run log and handoff notes
+
+The run log is the record of a build: one file per build plan, in the workpad's `reports/` folder (name it per the `workpad` skill, e.g. `<YYYY-MM-DD-hh>-<slug>-run.md`). Each phase appends to it. The phase reviewer reads it; a successor Athanor starts from it.
+
+Rules:
+
+- Take every time from `date` when you write it. Never estimate or count forward by feel.
+- Durations in summaries come from git commit times.
+- Stamp the exact model id from your system prompt. If you dispatched an agent and its id is unknown, write "unknown", not a guess.
+- Totals stay **provisional** until the phase review, fix pass and re-check have closed.
+
+## Header
+
+```markdown
+# Run log — <plan title>
+
+- Plan: <path>  ·  Build plan: <path>
+- Branch: <branch>  ·  Start commit: <hash>
+- Trunk notes: <path or "none">
+- Athanor: <model id>  ·  Session journal: <path>
+```
+
+## Per phase
+
+```markdown
+## Phase <N> — <title>
+
+| Block | Owner (model id) | Start | End | Commit | Tokens (if known) |
+|---|---|---|---|---|---|
+```
+
+## Handoff note (one per block, written by the block's owner)
+
+```markdown
+### Block <N.M> — <title>
+
+- Model: <exact id>
+- Start / end: <`date` output> / <`date` output>
+- Done: <what changed, in a few lines>
+- Deviations from plan: <what, and why> — or "none"
+- Flagged for review: <anything the reviewer should look at, e.g. a semantic you were unsure of>
+- Left for later: <work deferred to a later block or phase>
+- Expected broken: <areas that do not build or pass yet, and which block fixes them>
+- Commits: <hashes>
+```
+
+## Phase close (written by the Athanor)
+
+```markdown
+### Phase <N> close
+
+- Gate: <command> — <result>
+- Tests: <command> — <result> (fallout fixed in block <N.M>)
+- Flags for the reviewer: every deviation and every "flagged for review" line above, one per bullet, with its block.
+- Not run / untested: <anything the tests do not cover>
+- Status: provisional until review, fix pass and re-check close.
+```
+
+After the review, Igor (or the fixer) appends the review report path, the fix-pass commits, the re-check result, and the minors logged as follow-ups.
+
+## Trunk notes (optional, written at intake)
+
+Short, for the next agent that has not read the code: key files and seams, invariants the phase touches, every consumer of a changed semantic, the gate command, known traps. A page, not a design document.