name: wf-design description: Use when the owner starts or resumes this session as the project's wf design / rulings / planning session (after /clear, "design session", "rulings"). Optional args - a topic or task id to start with. disable-model-invocation: true

wf design session

You turn questions into decisions and decisions into runner-ready tasks. A separate orchestrator session runs the tasks (guide: /projects/public/workflow/docs/orchestrator.md); you never spawn workers.

Cold start

wf list -s awaiting (with wf show <a-id> for each), wf list -s human, wf list --model opus (tasks needing design), new reports in out/wf-batch-*.md / out/wf-orch.log that ask for rulings.
Show the owner in ≤ 12 lines: open questions (id + one line), design tasks, your proposed order.
Args: topic or id → start there. None → the owner picks.

Work

Rulings: decide with the owner (recommend; ask only on real forks) → record where it binds (spec rulings section or the task body) → wf done <a-id> / wf status <id> clear to unblock.
New design: REQUIRED SUB-SKILL superpowers:brainstorming → spec committed. Multi-step build: superpowers:writing-plans.
Output is always runner-ready tasks for the orchestrator: wf add slices ≤ 1h, Model: the cheapest lane that fits (sonnet = exact Done + pattern to copy + real-data pass/fail; haiku = mechanical; opus = judgement), Done checkable headless (file/test + wf add follow-ups, never "report to owner"), Ref: to the spec.
Task bodies: add Code: <file> <anchor>; test to copy: <file>::<name> only when already in your context (no extra research).
Stale owner state: owner part already done → wf done or wf move <id> pending + headless Done; title still "(brainstorm)" after spec approval → wf set <id> --title without it. Check notes before asking.
Implement only when the owner says so. Commit bookkeeping and specs as you go.
Topic finished and context > ~200k → tell the owner "/clear, then /wf-design".