Decision council: four adversarial voices for ambiguous calls
Convene a 4-voice council (architect, skeptic, pragmatist, critic) for trade-offs and go/no-go calls — written in Japanese
- What
- Convene a 4-voice council (architect, skeptic, pragmatist, critic) for trade-offs and go/no-go calls — written in Japanese
- Cost
- Free
- Needs
- nothing to install — the skill is a decision-making methodology; agents that can spawn subagents get the full anti-anchoring workflow; no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @affaan-m's four-voice decision council for ambiguous decisions, trade-offs and go/no-go calls (not for code review, task breakdown, architecture design or straightforward facts). Four lenses: the Architect (accuracy, maintainability, long-term impact), the Skeptic (challenges premises and framing, proposes the simplest credible alternative), the Pragmatist (release speed, user impact, operational reality) and the Critic (edge cases, downside risk, failure modes). The anti-anchoring mechanism: the three external voices are launched as fresh subagents with only the question and relevant context — never the full conversation transcript. The workflow: distill the decision into one explicit prompt, gather only the context that would change the answer, form the Architect's own position first (before reading the others), launch the three voices in parallel with a strict role prompt (position, reasoning, risk, one surprise), synthesize with bias guardrails (never dismiss an outside view without explanation, always include the strongest dissent, treat two-against-one as real signal), and deliver a compact scan-on-a-phone-screen verdict (positions, consensus, strongest dissent, premise check, recommendation). Includes persistence rules (only persist when the decision changes something real), multi-round follow-up guidance, and anti-patterns (using the council for code review, handing subagents the whole transcript, hiding disagreement, persisting every trivial decision). Honest caveats: the skill is written in Japanese (lives under `docs/ja-JP/`); pairs with companion ECC skills (`santa-method`, `knowledge-ops`, `search-first`, architecture decision records) not included here; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Decision council is a free Muse skill that convenes a four-voice council for ambiguous decisions, written in Japanese. Four lenses weigh in: the Architect on accuracy and long-term impact, the Skeptic challenging premises with the simplest credible alternative, the Pragmatist on release speed and operational reality, and the Critic on edge cases and failure modes.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: nothing to install — the skill is a decision-making methodology; agents that can spawn subagents get the full anti-anchoring workflow; no accounts or keys required Install "Decision council: four adversarial voices for ambiguous calls" for me. It gives my agent @affaan-m's four-voice council (Architect, Skeptic, Pragmatist, Critic) for ambiguous decisions, trade-offs and go/no-go calls: distill the question, gather only decision-relevant context, form the Architect's position first, launch the other three voices as fresh subagents with question plus context only (anti-anchoring), synthesize with bias guardrails, and deliver a compact verdict with consensus, strongest dissent, premise check and recommendation — plus persistence rules and anti-patterns. Written in Japanese; MIT-licensed. Repository: https://raw.githubusercontent.com/affaan-m/ecc/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/docs/ja-JP/skills/council/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "council". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is a methodology; call it when a real ambiguous decision or go/no-go call comes up). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.