Menu
Use when importing a harness; not for single files.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
Verifies the checklist summarizer end to end: runs it against TODO.md and compares the printed count with the file's items. Use after changing anything under src/ or TODO.md.
How to add knowledge to this harness: which kind owns a new fact, convention, procedure, or enforcement, and the trigger that says it is time. Use when adding or reorganizing a rule, skill, hook, or memory entry.
Use when driving a complex task through an agent team — parallel exploration across independent axes converging on a shared artifact, with an adversarial reviewer gate. NOT for single-axis or research-only work.
Use when driving a complex task through an agent team — parallel exploration across independent axes converging on a shared artifact, with an adversarial reviewer gate. NOT for single-axis or research-only work.
Use when importing a harness; not for single files.
| name | Name-Format |
| description | Use when importing a harness; not for single files. |
The name carries uppercase letters, outside [a-z0-9-]. The directory is named to match the name, so only skill.name-format fires.
