[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757SGJGQ2CGEJGWY9SSVYA3":3,"skill-same:01M757SGJGQ2CGEJGWY9SSVYA3":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M757SGJGQ2CGEJGWY9SSVYA3","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\"","SevWren\u002FDaily-Motivation-Brain-Helper","SevWren","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4411791?v=4","01M757KRED8NN6CAZAHKC73C6K","01M757KRFHMA61WJTBVGCAPXS0",1,"MIT","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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","b469548b8e522c5d7fbf5e126591af14e0dc3744",".claude\u002Fskills\u002Fbmad-sprint-planning",0,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper","https:\u002F\u002Fgithub.com\u002FSevWren","Mindset:  Improving yourself one day at a time -> made possible by utilizing today's technologies to fit your individual needs.","2026-10-25 09:39:17",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add SevWren\u002FDaily-Motivation-Brain-Helper --skill bmad-sprint-planning",{"tool":37,"command":38},"bunx","bunx skills add SevWren\u002FDaily-Motivation-Brain-Helper --skill bmad-sprint-planning",{"tool":40,"command":41},"pnpm","pnpm dlx skills add SevWren\u002FDaily-Motivation-Brain-Helper --skill bmad-sprint-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002FSKILL.md",true,[45,51,57,61,65,69,73,79,83],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"customize.toml","OTHER","其他",1606,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Fcustomize.toml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Ffix-sprint-status.md","REFERENCE","参考文档",2747,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Freferences\u002Ffix-sprint-status.md",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fgenerate-tracking.md",2636,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Freferences\u002Fgenerate-tracking.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Freadiness-gate.md",1821,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Freferences\u002Freadiness-gate.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fstatus-view.md",1674,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Freferences\u002Fstatus-view.md",{"path":70,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fvalidate.md",592,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Freferences\u002Fvalidate.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fsprint_plan.py","SCRIPT","脚本",28454,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Fscripts\u002Fsprint_plan.py",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"scripts\u002Ftests\u002Ftest_sprint_plan.py",21953,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Fscripts\u002Ftests\u002Ftest_sprint_plan.py",{"path":84,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":85,"sourceHtmlUrl":86},"sprint-status-template.yaml",2397,"https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fbmad-sprint-planning\u002Fsprint-status-template.yaml",[88,95,102,109,116,123],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M757YEXC4V515X48TR4A7FW3","repo-doc-audit","Performs a comprehensive Repository Documentation Audit and Governance Standard (RDAGS) against an entire codebase. Use this skill whenever the user wants to audit, evaluate, or assess repository documentation — including requests like \"audit my repo docs\", \"find doc inconsistencies\", \"check for documentation drift\", \"governance review\", \"find dead or orphan knowledge\", \"check my CLAUDE.md or AGENTS.md for accuracy\", or any systematic documentation quality evaluation. Always trigger this skill when the user asks to run a documentation audit or governance review, even if they describe only part of the standard (e.g., \"check traceability\" or \"find contradictions in my docs\"). Produces five output files: Repository-Audit-Report.md (full 18-section report) plus Direct-Contradictions.md, Semantic-Contradictions.md, Traceability-Failures.md, and Proposed-Repository-Governance-Improvements.md as standalone action-oriented findings documents.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Frepo-doc-audit\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M757YCKK0QMK7JRZFPMXTGN4","writing-great-skills","Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fwriting-great-skills\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M757Y8AM0HGTW50KFG5MWCRD","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":18},"01M757Y5RN0J4Y7XQQKSR8Z7D3","teach","Teach the user a new skill or concept, within this workspace.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fteach\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":18},"01M757Y0R3DYWN3D07TKJWXDMD","self-reflect","Enterprise-grade forensic self-reflection over recent git history. Multi-axis audit with pass\u002Ffail gates, mandate compliance matrix, platform drift forensics, test quality review, and ranked generation constraints.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fself-reflect\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":18},"01M757XYVBYVHJPP46YNDQGJER","handoff","Compact the current conversation into a handoff document for another agent to pick up.","https:\u002F\u002Fgithub.com\u002FSevWren\u002FDaily-Motivation-Brain-Helper\u002Fblob\u002Fmain\u002FCLAUDE\u002Fskills\u002Fproductivity\u002Fhandoff\u002FSKILL.md",[],[]]