consensus
/consensus
Use when choosing among architectural, technology, build-vs-buy, or feature alternatives with meaningful tradeoffs, especially high-impact, multi-team, hard-to-reverse, or risk-heavy decisions.
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when choosing among architectural, technology, build-vs-buy, or feature alternatives with meaningful tradeoffs, especially high-impact, multi-team, hard-to-reverse, or risk-heavy decisions.
Original author description
Use when choosing among architectural, technology, build-vs-buy, or feature alternatives with meaningful tradeoffs, especially high-impact, multi-team, hard-to-reverse, or risk-heavy decisions.
How it works
- Workflow
- Guardrails
- Output
- Validation
- Example
- References
SKILL.md preview
--- name: consensus description: "Use when choosing among architectural, technology, build-vs-buy, or feature alternatives with meaningful tradeoffs, especially high-impact, multi-team, hard-to-reverse, or risk-heavy decisions." --- # Consensus Choose among alternatives through structured comparison and stance rotation. <workflow> ## Workflow 1. Load the comparison procedure and stance-rotation method below. 2. Select sequential or isolated-subagent mode from the decision's scope and reversibility. 3. Compare the alternatives, rotate through the required stances, and synthesize a recommendation. </workflow> <guardrails> ## Guardrails Require genuine differences between views. Do not manufacture disagreement or let one stance contaminate the others when isolated analysis is required. </guardrails> ## Output State the decision, points of agreement and disagreement, a recommendation with low/medium/high confidence, conditions that would change it, and concrete next steps. <validation> ## Validation Confirm each stance contributed distinct evidence and the confidence level is proportional to the comparison. </validation> <example> ## Example Compare two API approaches, identify their operational and migration costs, then recommend one with explicit reversal conditions. </example> ## References - [Consensus strategy](references/consensus-strategy.md) — comparison procedure and mode selection. - [Stance rotation](references/stance-rotation.md) — alternative-stance method and isolation rules. - [Stance definitions](../perspectives/references/stances.md) — advocate, critic, and neutral views.
Files in this package (4)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
- references/consensus-strategy.md 1 KB
- references/stance-rotation.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · cofin/flow | 100 | Apache-2.0 |
| corespeed-io/consensus | 100 | MIT |
| materialofair/oh-my-codex | 96 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 8737599e1f5f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100decision-record
Use when choosing between alternatives with trade-offs — X-or-Y decisions or a weighted decision matrix / gewichtete Entscheidungsmatrix ('score my options'); ADR via `adr-create`. - 100decision-analysis
MANDATORY trade-off evaluation. You MUST invoke this skill when the user faces a choice between alternatives — build-vs-buy, rewrite-vs-patch, technology selection, resource allocation, priority decisions. Do NOT default to the first reasonable option. Do NOT skip evaluating "do… - 100tech-assessment
This skill should be used when the user asks to "assess technology", "technology evaluation", "tech stack analysis", "technical feasibility", "technology trends", "build vs buy", "technology roadmap", "architecture assessment", or needs guidance on evaluating technologies,… - 90tech-risk-assessment
Assess the security risk of a technology or product decision for leadership — new technology/vendor adoption, build-vs-buy, third-party/supply-chain, or M&A technical due diligence — and give a clear recommendation with trade-offs. Use to inform a strategic technology decision. - 100game-changing-features
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'. - 100chief-technology-officer
Use when a task needs the judgment of a Chief Technology Officer — deciding build vs buy for a core system, choosing whether an architecture bet is worth a full rewrite, sizing an SLA/uptime commitment against engineering cost, structuring engineering teams around a product…