18 lines
986 B
Markdown
18 lines
986 B
Markdown
|
---
|
||
|
|
description: Set up Symphony in the current project — detects the issue tracker, writes a tracker section into CLAUDE.md, drops a starter WORKFLOW.md, and offers to schedule the tick. Idempotent — safe to re-run to update.
|
||
|
|
---
|
||
|
|
|
||
|
|
Invoke the `symphony-init` skill. It will:
|
||
|
|
|
||
|
|
1. Probe the environment for an existing tracker (gh, gitea MCP, `.tracker/` CLI, etc.)
|
||
|
|
and existing Symphony config (`./WORKFLOW.md`, tracker section in `./CLAUDE.md`).
|
||
|
|
2. Interview you for anything it could not detect — which tracker, active/terminal
|
||
|
|
state names, concurrency cap, branch naming, etc.
|
||
|
|
3. Write or update the tracker integration section in `./CLAUDE.md` so future ticks
|
||
|
|
and workers know how to talk to your tracker.
|
||
|
|
4. Drop `./WORKFLOW.md` from the plugin's template, prefilled with what it learned.
|
||
|
|
5. Offer to set up a `/schedule` entry that fires `/symphony-tick` on a cadence.
|
||
|
|
|
||
|
|
Run this once per repo. Re-run any time the tracker changes or you want to update
|
||
|
|
the schedule.
|