Orchestrate Advocate, Skeptic, and Practitioner agents to stress-test a spec and produce a structured verdict.
npx skills add https://github.com/djwmobley/pipeline --skill debate-djwmobley
Please help me install this Agent Skill. Skill: debate Source: https://github.com/djwmobley/pipeline/tree/main/skills/debate Command: npx skills add https://github.com/djwmobley/pipeline --skill debate-djwmobley
This skill provides an adversarial design review workflow that pits Advocate, Skeptic, and Domain Practitioner agents against a spec to surface hidden assumptions, feasibility gaps, and scope risks before moving to planning.
Dispatch the Advocate, Skeptic, and Practitioner prompts against the current spec to generate a structured verdict file.
High-intent search queries and answers about installing and using this skill.
An adversarial spec evaluation uses three distinct agent roles—Advocate, Skeptic, and Practitioner—to critique your design specifications. This stress-testing surfaces hidden assumptions, feasibility gaps, and scope risks before you move to project planning.
To run an adversarial review, dispatch the Advocate, Skeptic, and Practitioner prompts against your current spec. The debate generates a structured verdict file containing disposition, agreement points, contested points, and identified risks for mitigation.
A structured debate verdict includes the final disposition, points of agreement among agents, contested points, and identified risks. This formal output documents hard constraints and decisions to enable project governance and inform risk mitigation.
Yes, you can use model-agnostic prompts for automated spec evaluation. The debate skill's internal prompts are entirely model-agnostic, allowing you to run the Advocate, Skeptic, and Practitioner critiques across any compatible language model.
You need an adversarial review when preparing to move from design to planning. It catches issues early by identifying realistic tradeoffs, gaps, and implementation constraints across feasibility and scope before committing to downstream development.
jugrajsinghFacilitates design exploration and produces a structured Markdown document.
jay6697117Plan sprint work and allocate resources using RICE, MoSCoW, and Kano prioritization.
seanGSISGValidate implementation plans for completeness, quality, feasibility, and scope.
thomfilgAutomate Jira task creation through multi-agent consensus with parallel and sequential iterations.
