Repository navigation
Tell the seats to write notes only when another seat needs them - #133
Merged
Merged
Conversation
The shared rule, the keep-notes skill, and the notes README now say: read the notes when the task depends on earlier work, and add only a decision, a finding, a reading, or a procedure that another seat or a later session needs. The journal of the room keeps routine steps. The guide-a-build-step skill records a failed check, a reading, or a change from the plan at once. It records the states of the steps when the person pauses or the build ends. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017XXF74KSFZJyMgz5Xnegas
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017XXF74KSFZJyMgz5Xnegas
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
2 participants
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.
Requested by Andrei · project thread
Before: every seat read the notes before it acted and added to them by default. The Engineer recorded and pushed each build step, and the room goal asked for each part and each step in the notes.
After: a seat reads the notes when its task depends on earlier work, and adds only a decision, a finding, a reading, or a procedure that another seat or a later session needs. The room journal keeps routine steps. During a build, the Engineer records a failed check, a reading, or a change from the plan at once, and sets the states of the steps when the person pauses or the build ends.
How: one shared rule in
src/domain/definitions.ts, thekeep-notesskill (description and one paragraph),guide-a-build-stepstep 6, the build room goal, theshared/notesdescription,notes/README.md,notes/build/README.md,docs/notes.md, and one line ofplanning/next.md. Two scripted tests pin the new wording. Existing workspaces keep their seeded notes README: notes are seeded once.pnpm checkpasses locally (6 stages). Not tested live: the cloud container has no model key, so whether the seats now write fewer notes is unconfirmed.🤖 Generated with Claude Code
https://claude.ai/code/session_017XXF74KSFZJyMgz5Xnegas
Generated by Claude Code