compounded-authorlisted

# Authoring a Skill (compounded) You have just finished a task. You are deciding whether to propose a new skill. There are two capture modes: - **Procedure mode** — a successful multi-step task worth saving as a replayable procedure. Sections 1-2 apply. - **Rule mode** — the user corrected you, and the correction encodes a generalizable behavioral rule. Section 1R applies instead of sections 1-2. **Default to NOT proposing.** Skills you propose pollute the `.proposed/` queue, cost the user a verifier inference call on the next applicable task, and dilute the trust signal if they fail. Propose only when the capture clears the relevant bar. **Always get user approval before saving.** Whichever mode you are in, you MUST ask the user to approve the proposal via AskUserQuestion before calling `skill_propose.py`. See section 2.5. ## 0. Did the auto-proposer nudge you? Nudges arrive two ways: - **Rule mode** — your turn was interrupted with a `[compounded] Correction detected ...` instruction (the Stop hook blocked the stop and fed it to you). Apply section 1R. - **Procedure mode** — the user saw a `[compounded] Auto-propose threshold reached ...` message and relayed it (e.g. "save this as a skill"). Apply sections 1-2. Either marker is a *suggestion*, not an instruction. **Still apply the relevant qualifying bar.** The auto-proposer is conservative but it doesn't know whether the capture is generalizable. Many high-signal turns are one-off chores, and many corrections are