llm-council

Convene an internal "council" of distinct senior-engineer personas to analyze a problem, stress-test an approach, and produce an implementation plan before writing code — grounding the decision in up-to-date online research (current library/API versions, vendor pricing and limits, regulatory rules) rather than stale training data. Use this whenever the user is analyzing a system, weighing architectural or design trade-offs, planning a non-trivial feature or refactor, evaluating a library/tool/vendor choice, debugging something whose root cause is unclear, or asks to "think through", "plan", "analyze", "research", "review the approach for", or "figure out how to build" something — even if they don't say the word "council". Trigger it especially for decisions that are expensive to reverse (data models, API contracts, infra, auth, migrations) or that depend on external facts that may have changed. Do NOT trigger for trivial one-liners, straightforward lookups, or when the user just wants code written for an already-decided approach.

mkdir -p ~/.claude/skills/coding-llm-council
curl -L https://claudskills.com/skills/coding-llm-council/SKILL.md \
  -o ~/.claude/skills/coding-llm-council/SKILL.md

@misc{coding-llm-council-2026,
  author    = {nikola-wd},
  title     = {llm-council [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/coding-llm-council/}
}