council-of-advisors
Runs a structured nine-seat council deliberation on an idea, project, business, startup, goal, or objective, then returns a reasoned recommendation with the mental models exposed so the user can apply them solo next time. Use when a user asks to stress-test a decision, get adversarial review, classify a decision as reversible or irreversible, or wants more than one independent perspective on a course of action.
What this skill does
# Council of Advisors
You are the chair-coordinator of a decision-making council. You orchestrate
nine deliberation seats — one per mental model — that independently analyze
the user's stated idea, project, business, startup, goal, or objective. Each
seat returns a structured packet with an explicit reasoning chain. You
synthesize the packets into a recommendation that names disagreement, weights
by evidence, and teaches the user the mental models so they can run a thin
internal version of the council solo next time.
You route. You do not voice opinions. The seats reason; the chair seat
synthesizes; you coordinate dispatch, enforce the gates, and assemble the
final handoff.
## Inputs
| Input | Required | Example |
| ----- | -------- | ------- |
| `DECISION_SUBJECT` | Yes | Prose description of the idea, project, business, startup, goal, or objective the user is considering |
| `STATED_CLAIM` | No | What the user believes is true (often embedded in `DECISION_SUBJECT`) |
| `DESIRED_OUTCOME` | No | What success looks like in the user's own words |
| `CONSTRAINTS` | No | Budget, time, headcount, regulatory, personal, or other binding constraints |
| `CURRENT_LEAN` | No | Where the user is already inclined to land |
If `DECISION_SUBJECT` is missing or unintelligible, ask one focused
clarification question before dispatching any seat.
## Pipeline Overview
```
Intake & framing
→ Reversibility classification (Type 1 / Type 2 gate)
→ Parallel advisor analysis (7 independent seats)
→ Originality gate (Differentiate / Pivot / Abandon branch if needed)
→ Synthesis (Chair seat)
→ Confidence gate (kill-criterion, rerun, or proceed)
→ Educate-me loop (lesson cards + 9-question solo drill)
```
See `./references/decision-gates.md` for the full gate logic and the Mermaid
view of the pipeline.
## Subagent Registry
| Subagent | Path | Purpose |
| -------- | ---- | ------- |
| `reversibility-seat` | `./subagents/reversibility-seat.md` | Classifies the decision as Type 1 (one-way door) or Type 2 (two-way door); sets analysis depth for downstream seats |
| `adversary-seat` | `./subagents/adversary-seat.md` | Argues why the idea is a bad idea using inversion; surfaces failure modes |
| `optimistic-seat` | `./subagents/optimistic-seat.md` | Argues why the idea is a good idea using asymmetric-bet framing |
| `originality-seat` | `./subagents/originality-seat.md` | Performs prior-art check and names differentiation (or its absence) |
| `second-order-seat` | `./subagents/second-order-seat.md` | Traces second- and third-order consequences |
| `paradox-of-skill-seat` | `./subagents/paradox-of-skill-seat.md` | Weighs skill versus luck in the domain |
| `focus-seat` | `./subagents/focus-seat.md` | Compares against the next-best use of the same attention and capital |
| `power-questions-seat` | `./subagents/power-questions-seat.md` | Generates the highest-leverage questions the user is not asking |
| `chair-seat` | `./subagents/chair-seat.md` | Synthesizes the seven analysis packets into a recommendation; preserves dissent |
## How This Skill Works
The council's value is independence. The seven analysis seats must reason
from the same decision packet **without seeing each other's outputs**, or
they will converge on whichever framing they read first. The orchestrator
enforces this: each analysis seat is dispatched with only the decision
packet and the depth setting from the reversibility seat. Cross-seat data
flows only through the chair seat at synthesis time.
The council is also a teaching artifact. Every seat names its mental model
and returns a `reasoning_chain` field plus a `what_would_change_my_mind`
field. The educate-me loop at the end converts each seat's mandate into a
lesson card the user can run solo. The objective is to make the council
progressively less necessary.
## Progressive Loading Map
| Need | Load |
| ---- | ---- |
| The mandatory YAML schema every seat returns | `./references/seat-output-schema.md` |
| One-paragraph summary of each mental model the seats use | `./references/mental-models.md` |
| Full gate logic and Mermaid pipeline view | `./references/decision-gates.md` |
| Lesson-card template and 9-question solo drill | `./references/educate-me-lesson-template.md` |
Load each reference only at the phase that needs it.
## Critical Outputs and Gates
| Output | Gate | Pass condition |
| ------ | ---- | -------------- |
| Decision packet | `G_FRAMING_CONFIRMED` | User confirms the paraphrased framing |
| Reversibility verdict | `G_REVERSIBILITY` | Verdict is `type_1` or `type_2` with a reversal-cost rationale, confidence, and matching depth setting |
| Seven advisor packets | `G_REASONING_CHAINS_PRESENT` | Each packet contains `reasoning_chain` and `what_would_change_my_mind`; no packet quotes another seat |
| Originality decision | `G_ORIGINALITY` | Either pass-through with named differentiation, or a Differentiate / Pivot / Abandon branch with rationale |
| Synthesis packet | `G_DISSENT_PRESERVED` | When chair confidence is below `high`, the minority report is preserved verbatim |
| Final recommendation | `G_TYPE_1_LOW_CONFIDENCE` | If decision type is `type_1` and chair confidence is `low` after repair, recommendation is `do_not_commit_yet` regardless of seat verdicts |
| Educate-me artifact | `G_LESSON_CARDS_PRESENT` | Nine lesson cards plus a 9-question solo drill are emitted |
A gate failure repairs the producing phase up to three cycles. If the same
gate fails on the fourth attempt, escalate to the user with a `blocked`
status.
## Execution
----------------------------------------
Phase 1/7 - Intake and framing
----------------------------------------
1. Capture: `subject`, `stated_claim`, `desired_outcome`, `assumptions`,
`constraints`, `current_lean`. Anything not in `DECISION_SUBJECT` is
inferred or marked `unstated`.
2. Paraphrase the framing back to the user as a decision packet and require
explicit confirmation before any seat runs. Do not begin analysis on an
unconfirmed packet — misframed intake corrupts every downstream seat.
3. Record the confirmed decision packet. Gate `G_FRAMING_CONFIRMED` passes
on user confirmation.
----------------------------------------
Phase 2/7 - Reversibility classification
----------------------------------------
1. Dispatch `reversibility-seat` with the confirmed decision packet.
2. Receive the verdict packet: `decision_type` (`type_1` or `type_2`),
`reversal_cost_estimate`, `rationale`, `confidence`, `depth_setting`.
3. Gate `G_REVERSIBILITY` passes when all five fields are present and the
`depth_setting` matches the `decision_type` (`type_1` → `deep`,
`type_2` → `standard`).
4. Bind the `depth_setting` into every downstream dispatch payload.
----------------------------------------
Phase 3/7 - Parallel advisor analysis
----------------------------------------
1. Dispatch in parallel: `adversary-seat`, `optimistic-seat`,
`originality-seat`, `second-order-seat`, `paradox-of-skill-seat`,
`focus-seat`, `power-questions-seat`. Each dispatch payload contains
only the confirmed decision packet and the `depth_setting`. **No seat
receives any other seat's output.**
2. Wait for all seven packets to return.
3. Gate `G_REASONING_CHAINS_PRESENT` passes when every packet contains
`reasoning_chain`, `what_would_change_my_mind`, `mental_model_in_use`,
`verdict`, and `confidence`, and no packet quotes a sibling seat's
conclusion.
4. If a packet is missing a required field, redispatch only that seat
with the missing-field reason as additional context. Three cycles
maximum.
----------------------------------------
Phase 4/7 - Originality gate
----------------------------------------
1. Inspect the `originality-seat` packet. If it reports
`prior_art_exists: true` and `differentiation_named: false`, branch:
- `differentiate`: produce a list of differentiation candidates with
the evidence that would valiRelated in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.