22 lines
1.3 KiB
Markdown
22 lines
1.3 KiB
Markdown
|
---
|
||
|
|
description: Push stories from docs/planning/stories.md into the project's issue tracker. Reads the project's CLAUDE.md to learn how to write to whatever tracker the project uses (GitHub Issues, Gitea, tracker CLI, Linear, etc.). Always shows a dry run before creating anything.
|
||
|
|
---
|
||
|
|
|
||
|
|
Invoke the `composer` skill in *load* mode. It will:
|
||
|
|
|
||
|
|
1. Read `docs/planning/stories.md` and `docs/planning/roadmap.md`.
|
||
|
|
2. Read the project's `CLAUDE.md` for the tracker integration section. If
|
||
|
|
no tracker section is documented, exit with `tracker_integration_missing`
|
||
|
|
and point the user at `/symphony-init` (which can write the section) or
|
||
|
|
suggest adding one manually.
|
||
|
|
3. Build the planned write set — milestones, epics/parents, stories, labels.
|
||
|
|
4. **Show a dry run.** Print every command the skill would run, grouped by
|
||
|
|
epic. Wait for user confirmation.
|
||
|
|
5. On confirmation, execute the writes. On any failure, stop and report —
|
||
|
|
do not auto-continue past errors that might leave a partial write.
|
||
|
|
6. Record the created issue IDs back into `stories.md` so the file becomes the
|
||
|
|
source-of-truth map between local plan and tracker reality.
|
||
|
|
|
||
|
|
After load, suggest `/symphony-init` if the project doesn't already have
|
||
|
|
Symphony configured. Composer's job ends here; Symphony's begins.
|