op-suggestlisted

Use to capture a high-signal moment to the user's personal queue at `~/.achron-spine/bucket/SUGGESTIONS.md`. Fires on four narrow conditions only — (1) explicit user signal ("we should add this to the manual," "remember this," "next time we hit this, let's…," "let's not forget this"); (2) repeated friction — Claude was corrected on the same pattern 2+ times in this session; (3) end-of-session reflection ("what did we learn here?," "anything worth capturing?," natural stopping point with a learning frame); (4) the user invokes `/bucket suggest`. Never fires on speculation ("it'd be cool if…"), one-off friction, mid-task ideation, or Claude's own hunches without user reaction. Appends one entry to the queue and gets out of the way — never modifies `chapters/` or `skills/core/`, never edits existing bucket files, never interrupts the task in progress.
TimTGelhard/ACHRON-spine · ★ 1 · Code & Development · score 74

Install: claude install-skill TimTGelhard/ACHRON-spine

# op-suggest — capture to the queue Append one entry to `~/.achron-spine/bucket/SUGGESTIONS.md` and stop. Curation (`/bucket curate`) acts later. Rationale (why the threshold is high, why missed signals are free): [`chapters/personalization/19c-suggestion-loop.md`](../../../chapters/personalization/19c-suggestion-loop.md). Expand `~` to `$HOME` before reading; `install.sh` makes `~/.achron-spine` resolve to the spine clone. ## Bucket-loop gate Before doing anything else: read `~/.claude/achron-spine-profile.md` `## Spine defaults` → `Bucket loop:`. If `off`: - Implicit triggers (friction-counter, end-of-session reflection) → silently exit; do not append. - Explicit triggers (`/bucket suggest` slash command, user said "remember this") → still append. Treat explicit user invocation as overriding the profile setting one-shot; the user knows they're capturing. Default if the field is absent: `off` (the audit-recommended default after the round-6 flip — a user who never ran `/onboard` shouldn't have the bucket loop firing in the background; the spine + profile still work without it). ## When to fire — exactly four conditions | Trigger | Confirm before logging | |---|---| | Explicit user signal — "we should add this," "remember this," "next time…" | User named it. Log it. | | Same friction 2+ times this session — same mistake, same direction, same correction | You can quote both corrections. If not, it's not a pattern yet. | | End-of-session reflection — "what did we learn?,