run-engineering-councillisted

Convene an independent multi-perspective engineering council before high-stakes or hard-to-reverse work — major architecture, a new plugin or subsystem, external integrations, risky migrations, security-sensitive or AI-system design, or build-vs-buy. Invoke proactively when a change is large, cross-cutting, or costly to undo, not only when explicitly asked; skip it for routine bug fixes and simple docs.
johnoconnor0/johns-os · ★ 0 · AI & Automation · score 73

Install: claude install-skill johnoconnor0/johns-os

# Run Engineering Council ## Trigger Use proactively before starting an enormous, irreversible, or cross-cutting change, and whenever the user asks for a council review. The user-prompt intake flags high-stakes signals (new plugin/subsystem, architecture, external provider/integration, migration, security, AI-system, build-vs-buy) and suggests this skill — act on that suggestion rather than waiting to be asked. ## When To Use - Major architecture decisions. - New plugin, subsystem, or platform-shaping work. - Build-vs-buy choices. - Risky or irreversible migrations. - Security-sensitive or external-integration designs. - Scaling or AI-system design tradeoffs. ## Inputs Inspected - Council question. - Relevant lifecycle artifacts. - Repo evidence and external constraints supplied by the user. ## Workflow 1. Confirm the decision is high-stakes enough for council review (see When To Use). If a normal implementation plan is sufficient, use that instead. 2. Collect the explicit question and context files or directories. Do not broaden scope silently. 3. **Subagent council (default — real multi-perspective analysis).** Spawn the five advisor subagents IN PARALLEL, each with the same question and context: `council-contrarian`, `council-first-principles`, `council-expansionist`, `council-outsider`, `council-executor`. Each returns a Markdown draft with the sections `Position`, `Evidence Reviewed`, `Analysis`, `Evidence Gaps`, `Recommendation`. Write each to `.project/.enginee