ECC Council
Convene a four-voice council (Architect, Skeptic, Pragmatist, Critic) for ambiguous decisions, tradeoffs, and go/no-go calls.
- What
- Convene a four-voice council (Architect, Skeptic, Pragmatist, Critic) for ambiguous decisions, tradeoffs, and go/no-go calls.
- Cost
- Free
- Needs
- Use "ECC Council" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a four-voice decision council for ambiguous decisions, tradeoffs, and go/no-go calls. It comes from the ECC framework but works fully without it. The in-context Claude voice takes the Architect lens (correctness, maintainability, long-term implications) while three fresh subagents take Skeptic (premise challenge, simplification, assumption breaking), Pragmatist (shipping speed, user impact, operational reality), and Critic (edge cases, downside risk, failure modes). Each external voice receives only the decision question and compact context, never the full transcript; that is the anti-anchoring mechanism. The workflow: extract the real question, gather only the necessary context, form the Architect position first, launch the three voices in parallel with a strict prompt shape (position, reasoning, risk, one surprise, under 300 words), then synthesize with bias guardrails (never dismiss a view without explaining why, always include the strongest dissent, treat two-against-one as a real signal) into a compact, phone-scannable verdict. One round by default. From the affaan-m/ECC repository (MIT). Honest caveats: four voices means roughly four times the tokens per decision, so reserve it for genuinely ambiguous calls, not code review, implementation planning, or straight factual questions. Persist the outcome only when it changes something real. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "ECC Council" with your Muse. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/pi/core/skills/ecc-council/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Convene a council on: [your decision, e.g. ship now vs hold for polish]." 3. Answer the one clarifying question if asked, then read the four positions and the verdict; check the strongest dissent before deciding. Tip: give each voice only the question and the essential constraints; feeding full transcripts destroys the anti-anchoring value. Safety: a skill is plain-text instructions; it runs nothing by itself. Four voices cost about four times the tokens; use it for ambiguous decisions, not routine tasks.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.