consort v0.1.0

First release of consort — a two-vendor development lifecycle for Claude Code. The principal (any strong Claude Code session model) orchestrates, synthesizes, and verifies; Codex (gpt-5.6) implements and cross-reviews. The value is the finding only one model caught.

What's in it

• Pipeline skills — /consort:run (interview → spec → plan → implement → review → gate), /consort:review (standalone cross-model review of the working diff), /consort:plan.
• Panel + synthesis — blind independent drafts from both voices in the front phases, scored and merged with per-idea attribution.
• Delegation spine — the principal hands one task at a time to Codex with a five-part brief; verbose output stays on disk, structured results come back.
• Pluggable Codex backend — auto-uses the official Codex Claude Code plugin's companion runtime when installed, falls back to the raw codex exec CLI. Force either with CONSORT_CODEX_BACKEND=plugin|exec.
• State on disk — every phase resumes from .consort/; the session dying loses nothing.
• Shared JSON schemas (spec / findings / task-result) so two vendors are machine-comparable; MIT licensed.

Requirements

Claude Code, plus either the Codex plugin or a local codex CLI (ChatGPT or API auth). Swap the implementer model via CONSORT_IMPL_MODEL.