{"name":"iurykrieger-yoke","owner":{"name":"ClaudePluginHub"},"plugins":[{"name":"iurykrieger-yoke","source":{"source":"github","repo":"iurykrieger/claude-yoke"},"description":"Governed adversarial development for AI agents — v5.0 dual Phase-1 entry path (`/yoke:discover` for product-shaped tasks, `/yoke:fix` for engineering-shaped fixes) atop the v4.0 acceptance-criteria QA cutover and the v3.0 agent council protocol. Phase 1 now offers two authoring entrypoints producing interchangeable Phase-1 artifacts (`.yoke/prds/<slug>.md` or `.yoke/fixes/<slug>.md`); downstream skills read whichever exists via `wm_phase1_artifact_path` without branching on the artifact kind. Phase 3 produces a binding Acceptance Criteria document organised as User Stories → Definition of Done → Acceptance Criteria → Sensor pool, authored through an interactive Senior-QA grill. Three runtime persona subagents (Sr Eng, Sr QA, Sr Staff) spawn in parallel each cycle behind a deterministic sync barrier (Phase A), exchange réplicas inside a bounded council loop with a contradiction-detection arbiter (Phase B), and either advance on consensus or escalate Trigger 4 on cap-exhausted divergence (Phase C). Sensor selection per Acceptance Criterion is a runtime council decision, not an authoring-time tag. All inside a binding human contract. Canonical-memory reads and writes dispatch through providers.yaml to a peer plugin (claude-bedrock is the reference implementation); pluggable canonical-memory providers ship via the documented working-memory contract. The Orchestrator subagent survives in canonize-only mode at full-run termination. Manifesto: yoke.md.","version":"5.0.0","strict":true,"keywords":["harness-engineering","agent-council","council-protocol","binding-spec","canonical-memory","canonical-memory-provider","pluggable-providers","ralph-loop","human-in-the-loop","spec-driven"],"category":"development"}]}