contention-layerlisted

When two skills or agents produce conflicting verdicts on the same output, reads the conflict as a signal rather than an error and harvests new skill candidates. Routes skills born from contention to fh-meta if they are meta-layer, to commons plugin if project-agnostic, or to field harvest if domain-specific. Triggered by "two skills conflict", "they produce different conclusions", "contention-layer", "contention harvest".
chrono-code/forge-harness · ★ 2 · AI & Automation · score 71

Install: claude install-skill chrono-code/forge-harness

# contention-layer — Contention Harvest + New Skill Routing When two skills conflict, **harvest the signal** instead of discarding one. Find the validation angle that neither skill addressed, and onboard new skill candidates into the FH ecosystem according to their routing path. > Philosophical basis: Cognitive dissonance in humans is not a failure but a core asset — the ability to hold contradictions created culture. In the FH ecosystem, conflict is the signal from which new skills are born. ## Triggers ``` /contention-layer # analyze current conflict situation /contention-layer --skills A B # specify two skills for contention analysis ``` Phrase triggers: "two skills conflict" · "weird when used together" · "they produce different conclusions" · "contention harvest" · "contention" ## Step 1. Collect Conflict Points Record clearly which skills conflicted on which output, and in which direction. ``` Conflicting skill A: {skill name} — verdict: {conclusion} Conflicting skill B: {skill name} — verdict: {conclusion} Conflicting output: {TC / diagnostic report / design document / ...} Conflict point: {which item, by which criteria difference} ``` **Conflict type classification**: - `Criteria conflict`: Same item evaluated by different criteria (e.g., coverage 50% = Pass vs Fail) - `Scope conflict`: A includes, B excludes a certain domain - `Order conflict`: Same goal approached with different preconditions - `Philosophy conflict`: The measurement