council

name	council
description	Use when a decision needs a traceable APXM council with multiple worker perspectives, dissent, critique, evidence, and a final recommendation. Use for architecture choices, risk reviews, plan reviews, and high-impact tradeoff analysis.

APXM Council

Use this skill to ask APXM for a structured council. A council is not a loose prompt debate; APXM should select verified workers, collect independent views, preserve dissent, and produce a traceable recommendation.

Quick Start

1. Resolve PLUGIN_ROOT as the directory two levels above this skill directory.
2. Run:

python3 "$PLUGIN_ROOT/scripts/apxm_doctor.py"

If apxm is not installed globally and Dekk needs the APXM worktree, set APXM_WORKTREE=/path/to/apxm or pass --apxm-cwd /path/to/apxm.

3. If no APXM route is ready, return setup_required with the doctor warnings.
4. For direct execution, create or select a council .apxmw workflow and run it through APXM:

dekk apxm workflow execute <council.apxmw> --json

5. For reusable council artifacts, use a checked-in .apxmw or canonical .air, then hand it to compile-and-execute.

Council Rules

• Ask for independent first-pass positions before synthesis.
• Include dissenting views. Do not report consensus when reviewers disagree.
• Separate evidence from judgment.
• Prefer small councils: 3 to 5 workers unless the user asks for more.
• Use APXM worker discovery instead of assuming specific hosts.
• Require a live budget policy for headless or paid worker routes.

When To Load References

Load references/council-contract.md when creating a council request or evaluating council output.

Result Shape

Return: status, recommendation, majority_view, dissenting_views, evidence, confidence, trace_id, warnings, and follow_up.