council
Council Facilitator
Role
Facilitate a multi-advisor roundtable by dispatching archetype subagents, surfacing tensions, tracking position evolution, and synthesizing actionable recommendations. The facilitator never argues positions — it coordinates archetypes, enforces debate protocols, and preserves dissent in the final synthesis.
Procedures
Step 1: Confirm Scope and Mode
- Determine execution mode:
- Standard mode: user invoked the council directly. Run all 6 phases.
- Embedded mode: a parent skill invoked the council as a sub-step. Skip Phase 1 (context confirmation) and Phase 6 (decision capture). Return synthesis output for the parent to extract.
- If standard mode, restate the dilemma in one sentence, list 2-4 explicit constraints (timeline, team size, tech stack, compliance), and name the decision owner. If anything is ambiguous, ask the user to clarify before proceeding.
- If embedded mode, treat the parent's prompt as the confirmed context and proceed directly to Step 2.
Step 2: Select Advisors
- Read
references/archetypes.mdto review the full archetype catalog and selection heuristics. - Select 3-5 advisors based on dilemma complexity:
More from pedronauck/skills
skill-best-practices
Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.
243architectural-analysis
Deep architectural audit focused on finding dead code, duplicated functionality, architectural anti-patterns, type confusion, and code smells. Use when user asks for architectural analysis, find dead code, identify duplication, or assess codebase health. Don't use for style/formatting issues, performance profiling, security audits, or feature-level code review.
200brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
175typescript-advanced
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects. Don't use for plain JavaScript, runtime validation libraries (Zod, Yup), or basic TypeScript syntax questions.
172ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
169no-workarounds
Enforce root-cause fixes over workarounds, hacks, and symptom patches in all software engineering tasks. Use when debugging issues, fixing bugs, resolving test failures, planning solutions, making architectural decisions, or reviewing code changes. Activates gate functions that detect and reject common workaround patterns such as type assertions, lint suppressions, error swallowing, timing hacks, and monkey patches. Don't use for trivial formatting changes or documentation-only edits.
169