OpenAI Symphony
Set up and run OpenAI Symphony with isolated issue workspaces, workflow contracts, and unattended Codex orchestration for Linear projects.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/ivangdavila/symphonySetup
On first use, read setup.md and establish integration boundaries before proposing commands or workflow edits.
When to Use
Use this skill when the user wants an unattended orchestration service that reads Linear issues, creates per-issue workspaces, and drives Codex in app-server mode until work reaches review or done states. It is optimized for Symphony rollout, workflow authoring, safety hardening, and day-2 operations.
Architecture
Memory lives in ~/symphony/. See memory-template.md for setup.
~/symphony/
|-- memory.md # Activation policy, environment profile, and operating defaults
|-- workflow-notes.md # WORKFLOW.md decisions, state map, and prompt policy
|-- incidents.md # Runtime failures, retries, and mitigations
`-- run-history.md # Launch evidence, validations, and release notes
Quick Reference
Use the smallest relevant file for the task.
| Topic | File |
|---|---|
| Setup and activation behavior | setup.md |
| Memory template and status values | memory-template.md |
| Upstream spec map and implementation checkpoints | SPEC.md |
| Starter workflow contract used by the service | WORKFLOW.md |
| Bootstrap and launch runbook | setup-runbook.md |
| WORKFLOW.md contract template | workflow-template.md |
| Security hardening and trust checks | safety-guardrails.md |
| Incident triage and recovery | incident-playbook.md |
Requirements
- Repository access for the target project and a safe workspace root
- Linear personal API key in
LINEAR_API_KEY - OpenAI auth for Codex (
OPENAI_API_KEYor equivalentcodexlogin session) - Git remote credentials (
GITHUB_TOKENor SSH key access) for clone/fetch/push hooks codexbinary with app-server supportgitfor workspace bootstrap hooks- explicit user approval of target environment before unattended operation
- Trusted environment policy approved by the user before unattended operation
Core Rules
1. Treat SPEC.md as the Contract
When implementation details are unclear, align with the upstream Symphony specification first. Do not invent incompatible state models, config keys, or agent-runner behavior.
2. Keep WORKFLOW.md Repository-Owned and Validated
All orchestration policy must live in versioned WORKFLOW.md front matter plus prompt body. Validate YAML and template variables before launch, because invalid workflow files halt dispatch.
3. Enforce Per-Issue Workspace Isolation
Map each issue identifier to a dedicated workspace key and run Codex only inside that directory. Never execute agent work in shared roots or outside the configured workspace boundary.
4. Respect State-Driven Orchestration
Dispatch only active tracker states, stop sessions on terminal states, and preserve idempotent recovery after restarts. A run can end in a workflow-defined handoff state, not only Done.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-ivangdavila-symphony": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
Animations
Create performant web animations with proper accessibility and timing.
Arduino
Develop Arduino projects avoiding common wiring, power, and code pitfalls.
Bulgarian
Write Bulgarian that sounds human. Not formal, not robotic, not AI-generated.
Arabic
Write Arabic that sounds human. Not formal, not robotic, not AI-generated.
Assistant
Manage tasks, communications, and scheduling with proactive and organized support.