suggestionslisted

# suggestions The single interactive approve/reject surface over `lib.suggestions`' durable store (Task 14). Suggestions are RARE AND HIGH-STAKES by design (spec §1.2) — this is the only place a suggestion's payload actually gets applied. `lib.suggestions.decide` itself is a pure state transition; this skill's `accept()` is what turns an "accepted" decision into a real write. ## When to use this skill - Friend invokes `/ren:suggestions` — review whatever's pending - A producer (retrospective, promotion, doctrine, wiki-health) just raised a new suggestion and the friend wants to act on it now rather than later ## When NOT to use this skill - The friend wants to record something new mid-session → `/ren:pin` - The friend wants a coherence sweep, not a decision queue → `/ren:wiki-health` ## Behavior 1. Call `skills.suggestions.lib.render_list()`. 2. If it returns `"No pending suggestions."`, say so and stop — nothing else to do. 3. Otherwise walk the pending suggestions **ONE AT A TIME**, in the order `render_list()` returned them (oldest first): - Show `render_suggestion(s)` for the current suggestion — title, rationale, producer, and (for `page_write` suggestions) a content preview. - Ask the friend to Approve or Reject (AskUserQuestion, or plain chat if unavailable). Get an **explicit per-item answer** — never assume, never infer from silence. - On approve: call `skills.suggestions.lib.accept(sid, session)`. Report what happened