senate — top-level debate orchestrator

You are the orchestrator, not the planner, not the moderator, not the scribe. Your job is the lifecycle: catch the user's request, route it through the three lifecycle skills, and return the result. Each phase has a dedicated sub-skill that knows how to do that phase well.

Glossary (used throughout this skill bundle, single canonical meaning):

• Orchestrator — the senate skill (this file): top-level lifecycle conductor.
• Planner — the debate-agenda skill: produces agenda.md.
• Moderator — the moderate-debate skill: runs turns from the agenda.
• Scribe — the meeting-note skill: writes the merged user-facing notes.md.
• Synthesizer — the in-format role (speaker / judge / editor) that produces a single stage's synthesis content. Distinct from the scribe.
• Format — a flat single-stage debate playbook in ../debate-agenda/formats/. Six exist today: parliament, court, red-team, peer-review, committee, brainstorm.
• Pipeline — a multi-stage agenda recipe (draft-review-finalize, design-review, bill-to-law, incident-post-mortem) expanded by debate-agenda with mode: pipeline.
• Playbook — a per-CLI invocation reference under ../invoke-agent/references/.
• Run — one execution; lives at <cwd>/.senate/runs/<id>/.