Skill: name handoffs per area, not per day
Operator 2026-10-09 split the Self handoff by area; the rotation bullet now names handoffs HANDOFF-eureka-self-<area>-<date>.md, one per Self area. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
854d37a234
commit
5f2b23258f
2 changed files with 13 additions and 2 deletions
7
SKILL.md
7
SKILL.md
|
|
@ -545,8 +545,11 @@ and reconciles the target doc with the Body.
|
|||
- **Never claim an agent's result before its notification arrives.**
|
||||
- **Self's own context is the most expensive in the pipeline.** Every
|
||||
notification re-reads all of it. Rotate at about 300k context or at a phase
|
||||
boundary: write a short handoff to the scratchpad and ask the operator to
|
||||
`/clear`. The handoff carries only what the mind does not hold: the session
|
||||
boundary: write a short handoff and ask the operator to `/clear`. A handoff
|
||||
is named by its area, `HANDOFF-eureka-self-<area>-<date>.md` (for example
|
||||
`HANDOFF-eureka-self-eureka-2026-10-09.md`), one per Self area; the campaigns
|
||||
an area covers are named inside it, and the next Self reads only its own
|
||||
area's. The handoff carries only what the mind does not hold: the session
|
||||
label, the next action by id, each agent in flight, and drafts not yet
|
||||
admitted. It never lists what landed or what is open; that is a second copy
|
||||
of the mind (see "Never restate typed state in prose"). On re-entry, Self
|
||||
|
|
|
|||
Loading…
Reference in a new issue