[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79RKHV27533JB7VY2THXM4N":3,"skill-same:01M79RKHV27533JB7VY2THXM4N":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79RKHV27533JB7VY2THXM4N","bmad-sprint-planning",null,"Gate planning readiness, generate sprint status tracking from epics, summarize sprint progress, and validate or repair the tracking file. Use when the user says \"run sprint planning\", \"generate sprint plan\", \"check implementation readiness\", \"show sprint status\", \"validate sprint status\", or \"fix sprint status\"","thkennedy\u002Ftk-studio","thkennedy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4164502?v=4","01M79QZ8DMP5FF2HC6GS3S6FDF","Tim Kennedy","01M79QZ8EM9JBWJ15R5JNC4PW3",0,"MIT","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bmad-sprint-planning\ndescription: 'Gate planning readiness, generate sprint status tracking from epics, summarize sprint progress, and validate or repair the tracking file. Use when the user says \"run sprint planning\", \"generate sprint plan\", \"check implementation readiness\", \"show sprint status\", \"validate sprint status\", or \"fix sprint status\"'\n---\n\n# Overview\n\nYou are a senior developer about to commit to this plan. Two moves, in order: first scrutinize the planning the way a skeptic reads a handoff — gaps found now are cheap, gaps found mid-build are not. Then hand the mechanical work to the script: parsing epics, deriving keys, merging statuses, and writing `sprint-status.yaml` are deterministic jobs, not judgment calls. Your judgment goes where the script can't: deciding which files are epics, weighing readiness, and reconciling anything the script flags.\n\n## On Activation\n\n1. Resolve customization: `uv run {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}\u002Fcustomize.toml` directly and use defaults.\n2. Execute each entry in `{workflow.activation_steps_prepend}` in order.\n3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n4. Load `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` (and `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{planning_artifacts}`, `{implementation_artifacts}`, `{project_knowledge}` (skip gracefully if unset), `{date}`. Stay in `{communication_language}` for every turn, not just the greeting.\n5. Greet `{user_name}`, detect intent, and load only what that intent needs:\n   - **readiness** — check implementation readiness only: load `references\u002Freadiness-gate.md`, run the gate, report, stop\n   - **sprint-planning** — the full flow (also the refresh path for an existing `sprint-status.yaml`): load `references\u002Freadiness-gate.md`, then on PASS `references\u002Fgenerate-tracking.md`\n   - **status** — \"show sprint status\", \"where are we\": skip the gate, load `references\u002Fstatus-view.md`\n   - **validate** — check the tracking file's format: load `references\u002Fvalidate.md`\n   - **fix** — repair or rebuild a broken `sprint-status.yaml`: load `references\u002Ffix-sprint-status.md`\n\n   If interactive and unclear, ask; for headless behavior see `## Headless Mode`.\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding.\n\n## If the Script Fails\n\nThis rule covers every intent: when `sprint_plan.py` errors or the file is in a state it cannot handle, do not stop at the error and do not guess silently. Read the files yourself, deliver the same outcome by best judgment, tell the user the deterministic path failed and why, and offer the fix flow (`references\u002Ffix-sprint-status.md`) to restore a file the script can work with.\n\n## On Completion\n\nWhatever the intent, close out in `{communication_language}` per the loaded reference, then run `{workflow.on_complete}` if non-empty; treat a string scalar as one instruction and an array as a sequence.\n\n## Headless Mode\n\nWhen invoked headless, do not ask. Run the gate and, unless intent was readiness-only, generate tracking. Ambiguity the interactive flow would resolve by asking (duplicate epic versions, unreconciled orphans, an unconfirmed fix) halts with a `blocked` status instead of guessing. End with a JSON response:\n\n```json\n{\n  \"status\": \"complete\",\n  \"intent\": \"sprint-planning\",\n  \"gate\": \"PASS\",\n  \"status_file\": \"{implementation_artifacts}\u002Fsprint-status.yaml\",\n  \"findings\": [],\n  \"warnings\": []\n}\n```\n\n`gate` is `PASS`, `CONCERNS`, or `FAIL`; on `FAIL` include `findings` and the saved findings path if written, and omit `status_file`. `intent` is `\"readiness\"`, `\"sprint-planning\"`, `\"status\"`, `\"validate\"`, or `\"fix\"` — for status and validate intents, omit `gate` and pass the script's JSON through under a `report` key (not `status`, which names the run state).\n\n## References\n\n- `scripts\u002Fsprint_plan.py` — the deterministic parser\u002Fgenerator\u002Fmerger; subcommands `generate`, `status`, `validate`. Its JSON output is the contract this skill reads; argparse errors are JSON too\n- `references\u002Freadiness-gate.md` — the PASS\u002FCONCERNS\u002FFAIL gate: artifact inventory and the implementability question\n- `references\u002Fgenerate-tracking.md` — epic discovery, the generate command, and acting on its JSON report\n- `references\u002Fstatus-view.md` — the status view: counts, risks, open action items, next recommended action\n- `references\u002Ffix-sprint-status.md` — rebuild a broken tracking file: evidence-gathering subagents, user confirmation, pristine regeneration\n- `references\u002Fvalidate.md` — format validation of an existing `sprint-status.yaml`\n- `sprint-status-template.yaml` — the documented file format and status vocabulary; the script embeds the same block and the test suite pins the two copies together\n","# Overview\n\nYou are a senior developer about to commit to this plan. Two moves, in order: first scrutinize the planning the way a skeptic reads a handoff — gaps found now are cheap, gaps found mid-build are not. Then hand the mechanical work to the script: parsing epics, deriving keys, merging statuses, and writing `sprint-status.yaml` are deterministic jobs, not judgment calls. Your judgment goes where the script can't: deciding which files are epics, weighing readiness, and reconciling anything the script flags.\n\n## On Activation\n\n1. Resolve customization: `uv run {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`. On failure, read `{skill-root}\u002Fcustomize.toml` directly and use defaults.\n2. Execute each entry in `{workflow.activation_steps_prepend}` in order.\n3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n4. Load `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` (and `config.user.yaml` if present). Resolve `{user_name}`, `{communication_language}`, `{document_output_language}`, `{project_name}`, `{planning_artifacts}`, `{implementation_artifacts}`, `{project_knowledge}` (skip gracefully if unset), `{date}`. Stay in `{communication_language}` for every turn, not just the greeting.\n5. Greet `{user_name}`, detect intent, and load only what that intent needs:\n   - **readiness** — check implementation readiness only: load `references\u002Freadiness-gate.md`, run the gate, report, stop\n   - **sprint-planning** — the full flow (also the refresh path for an existing `sprint-status.yaml`): load `references\u002Freadiness-gate.md`, then on PASS `references\u002Fgenerate-tracking.md`\n   - **status** — \"show sprint status\", \"where are we\": skip the gate, load `references\u002Fstatus-view.md`\n   - **validate** — check the tracking file's format: load `references\u002Fvalidate.md`\n   - **fix** — repair or rebuild a broken `sprint-status.yaml`: load `references\u002Ffix-sprint-status.md`\n\n   If interactive and unclear, ask; for headless behavior see `## Headless Mode`.\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. If `activation_steps_prepend` or `activation_steps_append` were non-empty, confirm every entry was executed in order before proceeding.\n\n## If the Script Fails\n\nThis rule covers every intent: when `sprint_plan.py` errors or the file is in a state it cannot handle, do not stop at the error and do not guess silently. Read the files yourself, deliver the same outcome by best judgment, tell the user the deterministic path failed and why, and offer the fix flow (`references\u002Ffix-sprint-status.md`) to restore a file the script can work with.\n\n## On Completion\n\nWhatever the intent, close out in `{communication_language}` per the loaded reference, then run `{workflow.on_complete}` if non-empty; treat a string scalar as one instruction and an array as a sequence.\n\n## Headless Mode\n\nWhen invoked headless, do not ask. Run the gate and, unless intent was readiness-only, generate tracking. Ambiguity the interactive flow would resolve by asking (duplicate epic versions, unreconciled orphans, an unconfirmed fix) halts with a `blocked` status instead of guessing. End with a JSON response:\n\n```json\n{\n  \"status\": \"complete\",\n  \"intent\": \"sprint-planning\",\n  \"gate\": \"PASS\",\n  \"status_file\": \"{implementation_artifacts}\u002Fsprint-status.yaml\",\n  \"findings\": [],\n  \"warnings\": []\n}\n```\n\n`gate` is `PASS`, `CONCERNS`, or `FAIL`; on `FAIL` include `findings` and the saved findings path if written, and omit `status_file`. `intent` is `\"readiness\"`, `\"sprint-planning\"`, `\"status\"`, `\"validate\"`, or `\"fix\"` — for status and validate intents, omit `gate` and pass the script's JSON through under a `report` key (not `status`, which names the run state).\n\n## References\n\n- `scripts\u002Fsprint_plan.py` — the deterministic parser\u002Fgenerator\u002Fmerger; subcommands `generate`, `status`, `validate`. Its JSON output is the contract this skill reads; argparse errors are JSON too\n- `references\u002Freadiness-gate.md` — the PASS\u002FCONCERNS\u002FFAIL gate: artifact inventory and the implementability question\n- `references\u002Fgenerate-tracking.md` — epic discovery, the generate command, and acting on its JSON report\n- `references\u002Fstatus-view.md` — the status view: counts, risks, open action items, next recommended action\n- `references\u002Ffix-sprint-status.md` — rebuild a broken tracking file: evidence-gathering subagents, user confirmation, pristine regeneration\n- `references\u002Fvalidate.md` — format validation of an existing `sprint-status.yaml`\n- `sprint-status-template.yaml` — the documented file format and status vocabulary; the script embeds the same block and the test suite pins the two copies together\n",{"name":5,"description":7},"main","ecd23b3c0458cd511812f643d9111e3d7c8235f4","apps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio","https:\u002F\u002Fgithub.com\u002Fthkennedy","https:\u002F\u002Ftimothyhkennedy.com","Just a guy who loves making tools, automation and games.","2026-11-10 20:38:16",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add thkennedy\u002Ftk-studio --skill bmad-sprint-planning",{"tool":38,"command":39},"bunx","bunx skills add thkennedy\u002Ftk-studio --skill bmad-sprint-planning",{"tool":41,"command":42},"pnpm","pnpm dlx skills add thkennedy\u002Ftk-studio --skill bmad-sprint-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002FSKILL.md",true,[46,52,58,62,66,70,74,80,84],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"customize.toml","OTHER","其他",1606,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Fcustomize.toml",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Ffix-sprint-status.md","REFERENCE","参考文档",2747,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Freferences\u002Ffix-sprint-status.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fgenerate-tracking.md",2636,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Freferences\u002Fgenerate-tracking.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Freadiness-gate.md",1821,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Freferences\u002Freadiness-gate.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fstatus-view.md",1674,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Freferences\u002Fstatus-view.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fvalidate.md",592,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Freferences\u002Fvalidate.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Fsprint_plan.py","SCRIPT","脚本",28454,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Fscripts\u002Fsprint_plan.py",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Ftests\u002Ftest_sprint_plan.py",21953,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Fscripts\u002Ftests\u002Ftest_sprint_plan.py",{"path":85,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":86,"sourceHtmlUrl":87},"sprint-status-template.yaml",2397,"https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fapps\u002Fsupervisor\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Fsprint-status-template.yaml",[89,96,103,110,117,124],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79RYSQ8C3MWDFTDSRAYFJYA","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.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-track\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M79RYMVE0031EV5B64MBGD8V","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\u002Fbudget trigger says the session must split.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-session\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M79RYFM9ATWHM6HAXJ3D19WV","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.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-research\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M79RYA1AWZZF83KBHGR6JDN3","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\".","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-report\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M79RY33VMYR5YNPVFKWRNW9S","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\".","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-playable-judge\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M79RXY4AM8JM6ZK2MAR3W3X2","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\u002Fstories.","https:\u002F\u002Fgithub.com\u002Fthkennedy\u002Ftk-studio\u002Fblob\u002Fmain\u002Fplugins\u002Ftk-studio\u002Fskills\u002Ftk-studio-plan-sync\u002FSKILL.md",[],[]]