Plays the agent role in a spec consensus session using the `spec` CLI. Use this skill whenever you need to propose a change, respond to another agent's proposal, concede or revise a position, or sign off with `spec agree`. Trigger on: propose/respond/concede/agree in a spec workflow where you're acting as a named agent.
Plays the implementer role in a spec workflow — writes code from a locked spec, runs tests, and records releases using the `spec` CLI. Use this skill only after consensus has been reached and the session is locked. Trigger on: build/test/release in a spec workflow after agents have agreed.
Plays the mediator role in a spec consensus session using the `spec` CLI. Use this skill when agents are stuck or talking past each other — run `spec clarify` or `spec reframe`. The mediator never votes, never proposes, and never takes a position. Trigger on: clarify/reframe when the consensus session needs a neutral intervention.
Decomposes a high-level feature request into a queue of specific, ordered spec tasks for agent workers. Use this skill when given a feature request, user story, backlog item, or any high-level description of work to be done. The orchestrator reads the codebase, identifies what needs to be built, determines the correct order, and populates the spec queue. Trigger whenever someone asks you to plan, scope, or break down a feature — even if they don't use the word "orchestrate".
Proposes high-quality, verifiable specs with guardrails so the implementation matches expectations. Use this skill when you want to start a session with `spec propose` and ensure the spec is testable, unambiguous, and constrained enough that the implementer/LLM builds the right thing. Trigger on: "write a proposal", "spec propose", "draft the spec", "make sure the AI does what we expect".