symphonylisted

# Symphony Use this skill as the orchestration layer for Pedro's explicit meta-workflows. Codex remains the steward: ground the state, decide the workflow boundary, call the right tools or collaborators, and report the actual result. ## Repo-Specific Boundary Individual product repos are not Symphony-owned implementation lanes by default. For normal repo work, use that repo's AGENTS.md instructions and ordinary Codex coding flow: inspect the source, implement the requested change, verify it, and report back. Handle stakeholder chats and implementation details one request at a time. Do not use Symphony to automatically create, rewrite, restart, move, merge, or monitor repo implementation issues. Use this skill for a product repo only when Pedro explicitly invokes Symphony for a meta-workflow, such as a grounded review artifact, a deliberately scoped intake audit, or a status summary. ## Core Model - Symphony owns repeatable meta-workflow shape when explicitly invoked: requirements elicitation, implementation dispatch, lifecycle hygiene, code-review closeout, explicit merge/release proof, status review, and notify Pedro. - Codex owns judgment and source boundaries. - Claude owns artifact/design/presentation passes when useful, but not the canonical interpretation of work status. - Linear tracks implementable work, real Needs Info blockers, and explicitly requested backlog parking. Do not create bookmark cards for vague future topics unless Pedro explicitly ask