Council & Solo

Every altitude in APO has two modes. Council, when the question is contentious and you want more than one head on it. Solo, when the path is clear and you just need it sharpened. Knowing which one to reach for is half the skill.

Solo — one focused pass

Solo is a single skill doing one job well. /we:story is the workhorse: it sits with you in plan mode and produces a build-ready Story — a minimal ticket plus a detailed plan with context, acceptance criteria, a user journey, and the design decisions (including the alternatives you rejected and why). The same shape exists at every altitude: /we:vision, /we:saga, /we:epic each formulate one artifact at their level.

When the work is obvious, go Solo and skip straight to refinement.

Council — many lenses, one room

Sometimes a decision is genuinely contested and no single perspective is enough. That is when you call a meeting.

/we:council   # convene a council on a topic — role-lens deliberation + synthesis
/we:meet      # a structured meeting at vision | saga | epic | story altitude

A Council convenes several agents, each carrying a distinct lens — Product Owner, Architect, Security, UX, and more. They deliberate in a shared conversation, address each other directly, and disagree out loud. The lead session synthesizes where they agree, where they pull against each other, and what it recommends. If you run weside, these are your own Companions; without an account, the plugin ships nine generic role-agents.

/we:meet wraps a Council at a specific altitude and decomposes the artifact into the next level down — a Vision meeting yields Sagas, an Epic meeting yields Stories.

How they hand off

Council first, then Solo. A /we:meet story session surfaces the tensions, then hands the result straight to /we:story, which locks it into a build-ready plan. The deliberation feeds the refinement; the refinement feeds the Build pipeline.

Both modes ship in the we plugin.