tk-studio-migrate
Designed migration of a project's planning binding to Jira — closed inventory, export→transform→import→verification, copy-then-verify-then-flag cutover, source retained read-only until explicit operator clearance (AD-16). Use when the user says "migrate planning to jira", "rebind to jira", "tk migrate", or asks to move the project's backlog into the team's tracker.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- tk-studio-migrate
- description
- Designed migration of a project's planning binding to Jira — closed inventory, export→transform→import→verification, copy-then-verify-then-flag cutover, source retained read-only until explicit operator clearance (AD-16). Use when the user says "migrate planning to jira", "rebind to jira", "tk migrate", or asks to move the project's backlog into the team's tracker.
02 资源文件 1
- 其他customize.toml607 B
03 SKILL.md 正文
tk-studio-migrate
Rebinding a project to Jira is a verified migration, not a copy (ST-8.2, AD-16). The deterministic core owns the safety rules; nothing here is a shortcut around them.
Behavior (both modes)
-
Preview first (no writes, backend not contacted):
uv run "${CLAUDE_PLUGIN_ROOT}/lib/migrate.py" run --directory <project-root> --dry-run -
Run the migration:
uv run "${CLAUDE_PLUGIN_ROOT}/lib/migrate.py" run --directory <project-root>In order: closed inventory (validated canonical entities + every current-projection file, hashed, persisted to
.tk-studio/migrations/jira.jsonbefore any move — nothing off the inventory may ever be deleted) → import through the jira adapter (lib/jirabackend.py— the only surface that talks to the backend, AD-4; API-token preflight incl. the org-admin toggle and issue-type scheme confirmation, AD-7) → verification (entity counts, complete id map, content hashes against both the inventory and the promote snapshots, spot round-trip read back from Jira) → cutover: source projection files marked read-only, then the flag —planning.backend: jirain tracked config, edited textually so human-authored bytes survive — written last and re-verified through config resolution. A crash at any point still reads from the source binding. -
Any verification mismatch halts
blockedwith every discrepancy listed; the flag is not written and no partial state reads as migrated. Other blocks: nothing to migrate, invalid canonical export, jira preflight failure (each gap named — never a silent 401), a local overlay overriding the flag, clearance without--confirm. -
Clearance is a separate, explicit act — the source stays read-only until the operator decides:
uv run "${CLAUDE_PLUGIN_ROOT}/lib/migrate.py" clear --directory <project-root> --confirmDeletes only inventory-listed files; anything else found is reported as a leftover and never deleted.
status --directory <root>reports the record. Attended: never runclearwithout the operator explicitly confirming in conversation; headless:--confirmis the recorded clearance — absent, the run endsblocked, never a prompt (AD-11). -
Headless: end with the status block:
{"status": "complete", "intent": "tk-studio-migrate", "artifacts": [".tk-studio/migrations/jira.json"], "reason": null}
If the deterministic core is unrunnable — a tool call denied by permissions, uv/python unavailable — end blocked with the status block naming the unrunnable core as reason: never a question, never a headless run that ends without the block (AD-11).
Rules
- No-delete-before-clearance and the closed inventory are absolute (AD-16); a mismatch is fixed by a human, never worked around.
- Canonical files are never a migration source in the deletable sense — they stay authoritative under every binding, Jira included (AD-4/AD-5).
- Credentials ride
JIRA_API_TOKEN(+JIRA_EMAIL) only — never any config file or the migration record (AD-3). - All paths resolve through
${CLAUDE_PLUGIN_ROOT}.
04 同仓库更多 Skills
tk-studio-track
Tracking verbs on the bound Jira project — `block` moves a story the loop cannot progress, and each dependent story, to "Blocked - Awaiting User" with a comment that @mentions the owner (or, with `--engagement`, one engagement's questions issue, which `close` later moves to "Done"); `reply` posts the owner's answer (or "Done.") with the owner's host-only token and moves the issue to "Block Resolved"; `validate` checks that resolution and passes the issue back to work or re-blocks it with a follow-up. Use when the user says "block this story", "tk track block", "put it in the owner's inbox", "reply to the blocked issue", "validate the resolution", or a supervisor or engagement payload names this skill.
tk-studio-session
Session discipline as a surface — land a boundary handoff (optionally carrying knowledge deltas) and end the session, or resume a fresh session from a run workspace alone. Use when the user says "hand off this run", "tk session", "resume the run", or a boundary/budget trigger says the session must split.
tk-studio-research
Run a chartered research pass — survey the topics a charter scopes, grade every finding by evidence, land the findings in the run workspace, and emit observation events for recommendation-worthy ones. Use when the user says "run the ecosystem watch", "tk research", or a research job's invoke-skill directive names this skill.
tk-studio-report
One-verb human defect report — "the skill did the wrong thing" — recorded as a report event in the local measurement ledger. Use when the user says "tk report", "report a defect", "that skill misbehaved", or "log a studio issue".
tk-studio-playable-judge
The playable-verify leg's screenshot judge (Story 34.3) — reads only a playable run's report.json and its frames, answers the fixed rubric (scene loaded, player visible and framed, no magenta or error overlay, HUD reads, the named moments shown) with pass or fail and findings each naming a frame and a rubric line. Driven headless by the supervisor's host leg on the project's sandbox tier; use when the payload names a playable `media` folder, or the user says "judge the playable frames".
tk-studio-plan-sync
Planning adapter — canonicalize BMad-native planning artifacts (normalize pass, sole id authority) and sync them with the bound planning backend. Use when the user says "sync the plan", "normalize planning artifacts", "tk plan sync", or after stock BMad planning flows produce or change epics/stories.