memory-backpass: the skill runs the command instead of describing it #85
No reviewers
Labels
No labels
blocked
bug
decision
duplicate
enhancement
help wanted
invalid
landed?
question
ready-to-merge
stale
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/memory!85
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/memory-backpass-skill-as-command"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The
memory-backpassskill now says how to runallod memory backpassand what to do with the PR it opens, instead of carrying the ten-step procedure the command implements. What changes for an agent reading it: the Inputs and Procedure prose and the Failures section are gone, replaced by a running section, an after-the-run section, and a one-line-per-step map that keeps the step numbers the command's code cites, pointing atdocs/allod-memory.mdin allod/tools for the mechanism. What stays identical: the two prompt files, which the command loads from this checkout at run time; the synthesis gates and the self-exclusion marker, which are those prompts' contract; the upstream credit. What proves it:allod skill memory-backpasslists it,.hooks/memory-budget --worktreepasses, and the command had completed a real run on a dev VM before this cut, so the procedure it replaces is proven code, not prose. If it is wrong: revert; nothing executes from this file.Refs allod/strategy#55
Risk
R0. A skill file and one README line.