capture-frictionlisted

Use when this tick or session hit real, disproportionately costly friction with the harness (a pitfall it could have warned about, a slow gate, missing operational knowledge), touched structural debt it can't fix right now (a duplicate surface, a hand-roll a sanctioned crate already covers), or can ground an apply-ready diff — to the harness's operating layer, or advocating a process-phrase re-cut — in a named invariant. Files one terse capture to .flume/friction/, .flume/refactor/, or .flume/amendments/ in the documented format — exceptional, never a duty; most ticks file nothing.
duct-tape-and-markdown/temper · ★ 1 · Code & Development · score 67

Install: claude install-skill duct-tape-and-markdown/temper

# Capture friction, structural debt, or a harness amendment Three sibling channels, one skill: `.flume/friction/` carries agent→human harness feedback; `.flume/refactor/` carries agent→plan structural-debt observations; `.flume/amendments/` carries agent→human apply-ready harness diffs (0044). Same bar, same shape; only the target directory, filename prefix, and drain audience differ. Check the target directory first — never re-file an already-filed capture. **The bar, both channels: exceptional, never a duty.** Most ticks/sessions file nothing. A capture names something you actually hit or touched THIS tick, with its actual cost — never speculative, never a substitute for finishing the job. ## Friction — `.flume/friction/<phase>-<slug>.md` What qualifies: a pitfall the harness could have warned about, a disproportionately lengthy process, missing operational knowledge, or a gate firing on a false positive — recurrence × cost, something the next session/tick would likely hit too. ``` ## Symptom What happened, concretely. ## Cost this tick Minutes, retries, reverted commits — the actual price paid. ## Suggested fix One idea is enough — a rule, a skill, a CLAUDE.md line, a prompt edit, a gate change, or an inbox item when the fix is product work. ``` Humans drain it out of band (session-open sweep): implement or route the fix into whichever harness owns it, then delete the file. Full bar and format detail: `.flume/friction/README.md`. ## Refactor — `.flume/refactor/<ph