vestige-auto-memorise
Auto-memorise: fire it yourself
This is the meta-capture skill. The four vestige-record-* skills wait for an explicit cue. Auto-memorise fires proactively whenever you spot a memorable moment — and dispatches inline to the right vestige subcommand without bouncing through another skill.
The point: agentic memory only compounds if capture is automatic. If the agent waits to be told "remember this" every time, the project's accumulated context stays in the user's head — exactly the failure mode Vestige exists to fix.
When to fire (the watch list)
Fire whenever the conversation produces any of the categories below. You decide the category based on the cue, then dispatch via the matching subcommand.
| Category | Cues you watch for | Subcommand | Default importance |
|---|---|---|---|
| Decision | "we'll go with…", "let's use…", "settled —", "going with X over Y because…", "decision:", explicit ## Decision headers, you chose A over B with a stated reason |
vestige decision add |
0.7 (0.85+ if architectural) |
| Preference | "I prefer…", "always…", "never…", "make sure to…", "in this project we…", "convention:", "rule:", correction the user gave that you should bake in | vestige preference add |
0.6 (0.8+ for hard rules) |
| Open question | "TBD:", "open question:", "unclear whether…", "we should figure out…", "follow-up:", "park that", ## Open Questions headers |
vestige question add |
0.5 (0.8+ if blocking) |
| Aha / TIL / gotcha / smell / TODO / root cause / workaround / surprise | "TIL", "turns out…", "the reason X happens is…", "good to know:", "careful — X breaks Y", "non-obvious", "smell:", "refactor candidate", "TODO:", "the bug was…", "I had assumed X but actually Y", "hack until…" | vestige note add |
0.5 (0.6 for smells / root causes) |
Tie-breaker rule of thumb: did the conversation produce a commitment with a why? Decision. A user opinion? Preference. An unknown? Question. Anything else worth keeping? Note.