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.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryScience & researchStars0
About this skill
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.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
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.
About this listing
Category
Science & research
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.