Harness feedback-loop curator. Activate on demand to read friction tags from the harness-friction wing, cluster them, and open one issue per cluster on the canonical/feedback repos in provenance blocks. --deep sweeps wing=transcripts; auto mode (#42) runs scheduled.
Tag a friction encountered during real work. Activate the moment any recognition signal fires (user pushback, second-time tool surprise, sibling-skill workaround, etc.). The single canonical implementation of the friction-tagging protocol — all other skills point here.
Realise a user-gate validation of an artifact (spec, plan, any document) through the configured backend: plannotator (browser review, opt-in) or internal (AskUserQuestion, default). The canonical gate implementation; invoke it instead of reimplementing a gate inline.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: