A hand over that says the cut and the gates once, and does not restate the blueprint - #80
Merged
Merged
Conversation
…e the blueprint The hand over of `/surface-plan` is played again after every amendment, and each time it said how the body of the blueprint is cut and which gates the loop will run. Sessions also restated what the blueprint and the plan hold, right after sending the developer to read the blueprint. In the first campaign of the evaluations the judge scored this as noise on every case (#67). Refs #67
This was referenced Oct 3, 2026
PierreMardon
added a commit
that referenced
this pull request
Oct 3, 2026
The report of the second campaign of the evaluations, kept for the next one to be compared with: `evals/reports/2026-10-03-e830bc236e9b/`. It measures the chain after the four first fixes drawn from the first campaign (#78, #79, #80, #81), on `01-overdue-list` and `03-overdue-reminders`, three runs each: 67 sessions, 17.07 USD at list price. - `report.md` and `summary.json` of the campaign, as `report --against evals/reports/2026-10-03-6bf7c06609a6/summary.json --keep` wrote them. Nothing else changes. Refs #77
This was referenced Oct 3, 2026
Closed
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The hand over of
/surface-planis played again after every amendment, and each time it said how the body of the blueprint is cut and which gates the loop will run. Sessions also restated what the blueprint and the plan hold, right after sending the developer to read the blueprint. In the first campaign of the evaluations the judge scored this as noise on every case (#67).What was done
Step 11 of
skills/surface-plan/SKILL.md:plan-draftedline: the cut and its reason in one line, and the gates. The first hand over is not always revision 1: after a block during planning, an instruction that amends the plan leads to revision 2 before anything was handed over.interview.mdthe revision carries, in one line, and the cut or the gates again only when the revision changed them.The last point goes beyond the part the prompt asked for, which is all #67 planned to fix: it sits in the same step, and the same campaign measures it.
Tests
The test of the hand over holds the three sentences in their order. The lint and the prompt tests pass locally; the CI runs every gate.
Not checked yet
No real session was run on this change. The rest of #67, what sessions tell of the chain's own steps without being asked, is left as it is.
Refs #67, #77