bmad-quick-dev
Deprecated: forwards to bmad-build. Do not use unless invoked by name.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- bmad-quick-dev
- description
- Deprecated: forwards to bmad-build. Do not use unless invoked by name.
03 SKILL.md 正文
Deprecated Build Alias
On Activation
- Check whether either legacy customization file exists:
{project-root}/_bmad/custom/bmad-quick-dev.toml{project-root}/_bmad/custom/bmad-quick-dev.user.toml
- If neither legacy file exists, output exactly
bmad-quick-dev is deprecated. Redirecting to bmad-build. Please use bmad-build in the future., invokebmad-buildexactly once with the user's original input verbatim, then execute no further steps in this shim. - For every legacy file that exists, use its matching new filename:
{project-root}/_bmad/custom/bmad-quick-dev.tomlbecomes{project-root}/_bmad/custom/bmad-build.toml.{project-root}/_bmad/custom/bmad-quick-dev.user.tomlbecomes{project-root}/_bmad/custom/bmad-build.user.toml.
- If the matching new file does not exist, tell the user that the customization file uses the deprecated name and offer to rename it. Rename it only after explicit approval. If approval is declined or unavailable, or the rename fails, HALT and do not invoke any skill.
- If the matching new file already exists, do not overwrite it. Read both files, explain their differences, and propose the exact content for the new file. Resolve conflicting values with the user. Only after the user explicitly approves that content, save and verify the new file, then remove the legacy file. If approval is declined or unavailable, or any operation fails, HALT and do not invoke any skill.
- After every detected legacy file has been migrated successfully and no legacy file remains, output exactly
bmad-quick-dev is deprecated. Redirecting to bmad-build. Please use bmad-build in the future., invokebmad-buildexactly once with the user's original input verbatim, then execute no further steps in this shim.
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.