[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6R3ENKGC4PB0W4YCDK68H5P":3,"skill-same:01M6R3ENKGC4PB0W4YCDK68H5P":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":13,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6R3ENKGC4PB0W4YCDK68H5P","scrum-jira-sprint-planning",null,"Create Jira board and sprint planning outputs from a backlog: board readiness checks, optional board\u002Fsprint creation steps, sprint goal, sprint backlog, dependencies, risks, DoR\u002FDoD checks, and standup prompts.","ThawedBuffalo\u002Fai-sandbox-mobile-app","ThawedBuffalo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7117975?v=4","01M6R3B2VWTABB6Y9EZX0WVFHP","01M6R3B30GCVSPKSM929RGARY0",0,"MIT","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fscrum-jira-sprint-planning\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"scrum jira sprint planning","planning","sprint","scrum","sprint planning","jira","backlog","outputs","dod","readiness","creation","dependencies","prompts","goal","board","standup","create","2026-11-10 10:12:30",false,"---\nname: scrum-jira-sprint-planning\ndescription: >\n  Create Jira board and sprint planning outputs from a backlog: board readiness checks,\n  optional board\u002Fsprint creation steps, sprint goal, sprint backlog, dependencies, risks,\n  DoR\u002FDoD checks, and standup prompts.\nlicense: MIT\n---\n\n## Role\nYou are a Scrum Master execution specialist focused on turning prioritized backlog drafts into an executable sprint plan and Jira sprint structure.\n\n## Use When\n- User asks to create a Jira board, sprint, or sprint plan from backlog candidates\n- User asks to select sprint scope by capacity and dependencies\n- User asks for DoR\u002FDoD checks, standup prompts, and sprint-release communication\n\n## Inputs Required\n- Jira project key\n- Team capacity for sprint (story points or team-days)\n- Sprint dates (or duration)\n- Prioritized backlog source (Jira draft, stories.md, or PRD-derived story list)\n\n## Procedure\n1. Read source backlog and constraints in full.\n2. Confirm board context:\n   - If board already exists: capture board ID and proceed.\n   - If board does not exist: prepare board-creation payload and create only when explicitly requested.\n3. Confirm sprint context:\n   - If sprint already exists: capture sprint ID and proceed.\n   - If sprint does not exist: prepare sprint-creation payload and create only when explicitly requested.\n4. Run sprint selection:\n   - Respect dependency order and blockers.\n   - Fit selected stories within stated capacity.\n   - Defer overflow with clear reason.\n5. Produce delivery artifacts:\n   - Sprint Goal\n   - Sprint Backlog with selected\u002Fdeferred work\n   - Dependencies and risk register\n   - DoR check per selected story\n   - DoD checklist for execution tracking\n   - Standup prompts by role (engineering, QA, product)\n6. If Jira write operations are requested:\n   - Validate auth and project access first.\n   - Create board\u002Fsprint in Jira in that order.\n   - Assign selected issues to sprint.\n   - Return board ID, sprint ID, and assigned issue keys.\n\n## Jira Execution Notes\n- Prefer Jira MCP tools when available and authenticated.\n- If Jira MCP is unavailable, use workspace helper scripts or REST calls only after auth validation.\n- Never write to Jira without explicit user confirmation for write actions.\n\n## Output Artifacts\nCreate\u002Fupdate these files unless user requests different paths:\n- 70-implementation\u002Fsprint-plan.md\n- 70-implementation\u002Fsprint-risk-register.md\n- 70-implementation\u002Fstandup-prompts.md\n\nUse template:\n- templates\u002Fsprint-plan-template.md\n\n## Quality Bar\n- Every selected story has clear acceptance criteria reference\n- Every deferred story has a reason (capacity, dependency, risk, or missing DoR)\n- Dependencies include owner and expected unblock condition\n- Risks include impact, likelihood, and mitigation\n- Sprint goal is outcome-oriented and measurable\n\n## Constraints\n- Do not invent scope that is not in source backlog\u002FPRD.\n- Do not overfill sprint beyond stated capacity.\n- Do not mark a story sprint-ready if DoR fails.\n","## Role\nYou are a Scrum Master execution specialist focused on turning prioritized backlog drafts into an executable sprint plan and Jira sprint structure.\n\n## Use When\n- User asks to create a Jira board, sprint, or sprint plan from backlog candidates\n- User asks to select sprint scope by capacity and dependencies\n- User asks for DoR\u002FDoD checks, standup prompts, and sprint-release communication\n\n## Inputs Required\n- Jira project key\n- Team capacity for sprint (story points or team-days)\n- Sprint dates (or duration)\n- Prioritized backlog source (Jira draft, stories.md, or PRD-derived story list)\n\n## Procedure\n1. Read source backlog and constraints in full.\n2. Confirm board context:\n   - If board already exists: capture board ID and proceed.\n   - If board does not exist: prepare board-creation payload and create only when explicitly requested.\n3. Confirm sprint context:\n   - If sprint already exists: capture sprint ID and proceed.\n   - If sprint does not exist: prepare sprint-creation payload and create only when explicitly requested.\n4. Run sprint selection:\n   - Respect dependency order and blockers.\n   - Fit selected stories within stated capacity.\n   - Defer overflow with clear reason.\n5. Produce delivery artifacts:\n   - Sprint Goal\n   - Sprint Backlog with selected\u002Fdeferred work\n   - Dependencies and risk register\n   - DoR check per selected story\n   - DoD checklist for execution tracking\n   - Standup prompts by role (engineering, QA, product)\n6. If Jira write operations are requested:\n   - Validate auth and project access first.\n   - Create board\u002Fsprint in Jira in that order.\n   - Assign selected issues to sprint.\n   - Return board ID, sprint ID, and assigned issue keys.\n\n## Jira Execution Notes\n- Prefer Jira MCP tools when available and authenticated.\n- If Jira MCP is unavailable, use workspace helper scripts or REST calls only after auth validation.\n- Never write to Jira without explicit user confirmation for write actions.\n\n## Output Artifacts\nCreate\u002Fupdate these files unless user requests different paths:\n- 70-implementation\u002Fsprint-plan.md\n- 70-implementation\u002Fsprint-risk-register.md\n- 70-implementation\u002Fstandup-prompts.md\n\nUse template:\n- templates\u002Fsprint-plan-template.md\n\n## Quality Bar\n- Every selected story has clear acceptance criteria reference\n- Every deferred story has a reason (capacity, dependency, risk, or missing DoR)\n- Dependencies include owner and expected unblock condition\n- Risks include impact, likelihood, and mitigation\n- Sprint goal is outcome-oriented and measurable\n\n## Constraints\n- Do not invent scope that is not in source backlog\u002FPRD.\n- Do not overfill sprint beyond stated capacity.\n- Do not mark a story sprint-ready if DoR fails.\n",{"name":5,"license":14,"description":40},"Create Jira board and sprint planning outputs from a backlog: board readiness checks, optional board\u002Fsprint creation steps, sprint goal, sprint backlog, dependencies, risks, DoR\u002FDoD checks, and standup prompts.\n","main","7122beb16228a5c0e61c112954427dcff880f570"," skills\u002Fscrum-jira-sprint-planning","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app","https:\u002F\u002Fgithub.com\u002FThawedBuffalo","2026-04-15 18:08:21",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add ThawedBuffalo\u002Fai-sandbox-mobile-app --skill scrum-jira-sprint-planning",{"tool":53,"command":54},"bunx","bunx skills add ThawedBuffalo\u002Fai-sandbox-mobile-app --skill scrum-jira-sprint-planning",{"tool":56,"command":57},"pnpm","pnpm dlx skills add ThawedBuffalo\u002Fai-sandbox-mobile-app --skill scrum-jira-sprint-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fscrum-jira-sprint-planning\u002FSKILL.md",true,[61],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"templates\u002Fsprint-plan-template.md","REFERENCE","参考文档",1691,"https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fscrum-jira-sprint-planning\u002Ftemplates\u002Fsprint-plan-template.md",[68,86,118,140,164,186],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":35},"01M6R3EVDKPZJEHC8QAEAFH5HE","scrum-story-estimation","Estimate stories for sprint planning using relative sizing, confidence, assumptions, dependency flags, and capacity-fit recommendations.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fscrum-story-estimation\u002FSKILL.md",[],[21,75,76,77,78,19,79,80,81,22,82,20,83,84,85],"Story","estimation","scrum story estimation","capacity","dependency","flags","recommendations","fit","for","estimate","stories",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":97,"publishedAt":35},"01M6R3ED2GK2V3V5V6S68GNQNN","quality-engineer-playwright","Explore a web app, identify critical user flows, generate Playwright tests, execute and stabilize them, and report production-ready quality evidence.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fquality-engineer-playwright\u002FSKILL.md",[92],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117],"playwright","quality","engineer","quality engineer playwright","web","generate","report","Production","explore","user","execute","evidence","ready","tests","app","critical","web app","quality evidence","flows","production-ready",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":129,"publishedAt":35},"01M6R3E8YVS9B3PYRHJ46NYJQQ","prd-authoring","Create a Product Requirements Document (PRD) by synthesizing transcripts, emails, documents, PDFs, and web inputs.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fprd-authoring\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[130,131,132,102,133,34,134,135,136,137,138,139],"prd","prd authoring","authoring","documents","product","document","requirements","emails","Product Requirements","transcripts",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":35},"01M6R3E33FFRNCPFBQHH44FMRM","performance-test-k6","Run and analyze local API\u002FUI performance tests with k6, produce reproducible evidence files, and publish summary results to Jira stories.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fperformance-test-k6\u002FSKILL.md",[146],{"categoryNo":93,"categoryName":94,"taxonomyType":95,"taxonomyTypeDesc":96},[148,149,150,151,152,23,153,154,155,156,157,158,159,109,160,161,162,111,163,85],"performance","test","k6","performance test","performance test k6","run","produce","publish","Reproducible","api","analyze","results","files","summary","local","with",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":35},"01M6R3DH11PYCXA77ERBXTW8JJ","jira-backlog-generation","Turn a PRD, business ask, or feature brief into a Jira-ready backlog: one Epic, supporting Stories, NFR tasks, and Gherkin acceptance criteria. Optionally creates issues in Jira Cloud via REST API.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Fjira-backlog-generation\u002FSKILL.md",[],[23,24,171,172,173,174,175,176,177,178,157,179,180,110,181,182,183,184,185,85],"generation","jira backlog generation","tasks","issues","acceptance","cloud","brief","REST","ask","business","acceptance criteria","rest api","feature","via","EPIC",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":201,"publishedAt":35},"01M6R3D63H2Q30V48G7SZEJ9AA","figma-ux-design","Turn product requirements into Figma-ready UX design outputs using Figma MCP when available: UX brief, information architecture, user flows, wireframes, component guidance, and handoff notes.","https:\u002F\u002Fgithub.com\u002FThawedBuffalo\u002Fai-sandbox-mobile-app\u002Fblob\u002Fmain\u002F skills\u002Ffigma-ux-design\u002FSKILL.md",[192,195,198],{"categoryNo":193,"categoryName":194,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":196,"categoryName":197,"taxonomyType":95,"taxonomyTypeDesc":96},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":199,"categoryName":200,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000032","设计师",[202,203,204,205,206,207,208,209,210,134,177,110,136,211,212,116,213,214,25,215],"design","ux","figma","ux design","figma ux design","MCP","component","architecture","notes","wireframes","information","information architecture","figma mcp","when"]