epic-migrate
Migrate epics and tasks from the old scheme to the new one: points, usage, RETRO.md for done epics. Use once per workbench after upgrading the plugin.
- License 许可
- MIT
- 最近更新
- 2026-10-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- epic-migrate
- description
- Migrate epics and tasks from the old scheme to the new one: points, usage, RETRO.md for done epics. Use once per workbench after upgrading the plugin.
03 SKILL.md 正文
Thin wrapper over ticket.py (python3 ${CLAUDE_PLUGIN_ROOT}/skills/start-development/scripts/ticket.py).
- Dry run:
ticket.py migrate --all --dry-run. Read the per-task changes and anypartial:lines. If it refuses, show the problems it names and stop; do not work around it. - Migrate:
ticket.py migrate --all. It prints one line per changed epic, writes the measured RETRO.md tables of done epics, and printsretro-writer: <epic>for each done epic whose Retro section is still the template's. - For each
retro-writer: <epic>line: dispatchworkbench:retro-writer(model sonnet) with the epic slug and itsrecord.md(ticket.py path <epic> record) as the notes, since old epics have no orchestrator notes. Then runticket.py retro <epic>, which commits the filled file aschore(ticket): <epic> retro. - Finally run
ticket.py deltas --all --bucketsand report which buckets left the seed.
Use --transcripts DIR or --logs DIR on migrate only to override the default locations.
04 同仓库更多 Skills
claudy
d claudy
gamma
Literal line one. Literal line two.
beta
Quoted: description with a colon.
alpha
Folded description that spans two lines and ends here.
worktree-merge
Rebases one subagent's worktree onto the base branch, optionally verifies the rebased tree, fast-forwards it into the worktree that has the base checked out (an epic integration tree or the main checkout), verifies every commit landed, and only then removes the worktree and its branch. Keeps the worktree intact on any conflict, dirty tree, or failed check. Use after a subagent returns work created with worktree-create.
worktree-create
Creates one isolated git worktree for one subagent, at <workbench>/.claude/worktrees/<name>, branched from main with the newest origin/main and local main merged in. Refuses a name already in use so two agents can never share a tree. Use once per implementation or review subagent before dispatching it; pair with worktree-merge to land the work and clean up.