[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71P2E8JP9HBVFJBQ46HWCMX":3,"skill-same:01M71P2E8JP9HBVFJBQ46HWCMX":76},{"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":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71P2E8JP9HBVFJBQ46HWCMX","sprint-planning",null,"Plan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsprint-planning\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsprint-planning\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,5,31,32,33,34,35,36,37],"planning","sprint planning","sprint","draft","capacity","use","backlog","for","availability","sprint plan","product","plan","work","team","when","new","knowledge","scope","SET","2026-11-10 10:56:23",false,"---\nname: sprint-planning\ndescription: \"Plan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.\"\ntags: []\ntools: []\nlicense: Apache-2.0\nsource: https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins\nsource_path: \"product-management\u002Fskills\u002Fsprint-planning\"\nsource_commit: 8444efcd48f7012f09797778a36a33e73d0861f4\n---\n# \u002Fsprint-planning\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nPlan a sprint by scoping work, estimating capacity, and setting clear goals.\n\n## Usage\n\n```\n\u002Fsprint-planning $ARGUMENTS\n```\n\n## How It Works\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                    SPRINT PLANNING                                 │\n├─────────────────────────────────────────────────────────────────┤\n│  STANDALONE (always works)                                       │\n│  ✓ Define sprint goals and success criteria                     │\n│  ✓ Estimate team capacity (accounting for PTO, meetings)        │\n│  ✓ Scope and prioritize backlog items                           │\n│  ✓ Identify dependencies and risks                              │\n│  ✓ Generate sprint plan document                                │\n├─────────────────────────────────────────────────────────────────┤\n│  SUPERCHARGED (when you connect your tools)                      │\n│  + Project tracker: Pull backlog, create sprint, assign items   │\n│  + Calendar: Account for PTO and meetings in capacity           │\n│  + Chat: Share sprint plan with the team                        │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n## What I Need From You\n\n- **Team**: Who's on the team and their availability this sprint?\n- **Sprint length**: How many days\u002Fweeks?\n- **Backlog**: What's prioritized? (Pull from tracker, paste, or describe)\n- **Carryover**: Anything unfinished from last sprint?\n- **Dependencies**: Anything blocked on other teams?\n\n## Output\n\n```markdown\n## Sprint Plan: [Sprint Name]\n**Dates:** [Start] — [End] | **Team:** [X] engineers\n**Sprint Goal:** [One clear sentence about what success looks like]\n\n### Capacity\n| Person | Available Days | Allocation | Notes |\n|--------|---------------|------------|-------|\n| [Name] | [X] of [Y] | [X] points\u002Fhours | [PTO, on-call, etc.] |\n| **Total** | **[X]** | **[X] points** | |\n\n### Sprint Backlog\n| Priority | Item | Estimate | Owner | Dependencies |\n|----------|------|----------|-------|--------------|\n| P0 | [Must ship] | [X] pts | [Person] | [None \u002F Blocked by X] |\n| P1 | [Should ship] | [X] pts | [Person] | [None] |\n| P2 | [Stretch] | [X] pts | [Person] | [None] |\n\n### Planned Capacity: [X] points | Sprint Load: [X] points ([X]% of capacity)\n\n### Risks\n| Risk | Impact | Mitigation |\n|------|--------|------------|\n| [Risk] | [What happens] | [What to do] |\n\n### Definition of Done\n- [ ] Code reviewed and merged\n- [ ] Tests passing\n- [ ] Documentation updated (if applicable)\n- [ ] Product sign-off\n\n### Key Dates\n| Date | Event |\n|------|-------|\n| [Date] | Sprint start |\n| [Date] | Mid-sprint check-in |\n| [Date] | Sprint end \u002F Demo |\n| [Date] | Retro |\n```\n\n## Tips\n\n1. **Leave buffer** — Plan to 70-80% capacity. You will get interrupts.\n2. **One clear sprint goal** — If you can't state it in one sentence, the sprint is unfocused.\n3. **Identify stretch items** — Know what to cut if things take longer than expected.\n4. **Carry over honestly** — If something didn't ship, understand why before re-committing.\n","# \u002Fsprint-planning\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](..\u002F..\u002FCONNECTORS.md).\n\nPlan a sprint by scoping work, estimating capacity, and setting clear goals.\n\n## Usage\n\n```\n\u002Fsprint-planning $ARGUMENTS\n```\n\n## How It Works\n\n```\n┌─────────────────────────────────────────────────────────────────┐\n│                    SPRINT PLANNING                                 │\n├─────────────────────────────────────────────────────────────────┤\n│  STANDALONE (always works)                                       │\n│  ✓ Define sprint goals and success criteria                     │\n│  ✓ Estimate team capacity (accounting for PTO, meetings)        │\n│  ✓ Scope and prioritize backlog items                           │\n│  ✓ Identify dependencies and risks                              │\n│  ✓ Generate sprint plan document                                │\n├─────────────────────────────────────────────────────────────────┤\n│  SUPERCHARGED (when you connect your tools)                      │\n│  + Project tracker: Pull backlog, create sprint, assign items   │\n│  + Calendar: Account for PTO and meetings in capacity           │\n│  + Chat: Share sprint plan with the team                        │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n## What I Need From You\n\n- **Team**: Who's on the team and their availability this sprint?\n- **Sprint length**: How many days\u002Fweeks?\n- **Backlog**: What's prioritized? (Pull from tracker, paste, or describe)\n- **Carryover**: Anything unfinished from last sprint?\n- **Dependencies**: Anything blocked on other teams?\n\n## Output\n\n```markdown\n## Sprint Plan: [Sprint Name]\n**Dates:** [Start] — [End] | **Team:** [X] engineers\n**Sprint Goal:** [One clear sentence about what success looks like]\n\n### Capacity\n| Person | Available Days | Allocation | Notes |\n|--------|---------------|------------|-------|\n| [Name] | [X] of [Y] | [X] points\u002Fhours | [PTO, on-call, etc.] |\n| **Total** | **[X]** | **[X] points** | |\n\n### Sprint Backlog\n| Priority | Item | Estimate | Owner | Dependencies |\n|----------|------|----------|-------|--------------|\n| P0 | [Must ship] | [X] pts | [Person] | [None \u002F Blocked by X] |\n| P1 | [Should ship] | [X] pts | [Person] | [None] |\n| P2 | [Stretch] | [X] pts | [Person] | [None] |\n\n### Planned Capacity: [X] points | Sprint Load: [X] points ([X]% of capacity)\n\n### Risks\n| Risk | Impact | Mitigation |\n|------|--------|------------|\n| [Risk] | [What happens] | [What to do] |\n\n### Definition of Done\n- [ ] Code reviewed and merged\n- [ ] Tests passing\n- [ ] Documentation updated (if applicable)\n- [ ] Product sign-off\n\n### Key Dates\n| Date | Event |\n|------|-------|\n| [Date] | Sprint start |\n| [Date] | Mid-sprint check-in |\n| [Date] | Sprint end \u002F Demo |\n| [Date] | Retro |\n```\n\n## Tips\n\n1. **Leave buffer** — Plan to 70-80% capacity. You will get interrupts.\n2. **One clear sprint goal** — If you can't state it in one sentence, the sprint is unfocused.\n3. **Identify stretch items** — Know what to cut if things take longer than expected.\n4. **Carry over honestly** — If something didn't ship, understand why before re-committing.\n",{"name":5,"tags":43,"tools":44,"source":45,"license":14,"description":7,"source_path":46,"source_commit":47},[],[],"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fknowledge-work-plugins","product-management\u002Fskills\u002Fsprint-planning","8444efcd48f7012f09797778a36a33e73d0861f4","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsprint-planning",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-14 03:30:52",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add monoes\u002Fmonomind --skill sprint-planning",{"tool":63,"command":64},"bunx","bunx skills add monoes\u002Fmonomind --skill sprint-planning",{"tool":66,"command":67},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill sprint-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fsprint-planning\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11607,[77,104,138,163,187,214],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":103},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[84,85,86,87,88,89,90,35,91,92,93,94,95,96,97,98,99,100,101,102],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","org","blockchain","2026-11-10 13:02:02",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":108,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":122,"publishedAt":103},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[112,117],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":118,"categoryName":119,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[123,124,125,88,126,127,33,128,92,129,130,30,29,131,132,133,134,135,136,137],"writing","writing plans","plans","superpowers","implementation plan","you","code","tasks","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":148,"publishedAt":103},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000031","产品经理",[131,149,150,151,152,35,153,33,154,155,31,29,156,157,158,159,160,161,24,162],"write spec","spec","user request","problem","acceptance","ask","vague","request","scoping","idea","metrics","feature","problem statement","document",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":173,"publishedAt":103},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[170],{"categoryNo":171,"categoryName":172,"taxonomyType":120,"taxonomyTypeDesc":121},"01JBSEEDCAT000000000000033","数据分析师",[92,131,174,175,26,176,35,24,33,177,178,179,180,31,181,182,183,184,185,186],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":199,"publishedAt":103},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[193,196],{"categoryNo":194,"categoryName":195,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":197,"categoryName":198,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发",[200,201,202,203,26,204,205,206,207,91,208,209,210,92,95,181,211,212,213,183],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":221,"publishedAt":103},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[220],{"categoryNo":197,"categoryName":198,"taxonomyType":115,"taxonomyTypeDesc":116},[202,222,223,224,225,226,19,26,227,228,129,229,230,231,95,181,232,233,183,234],"workflow architect","architect","trees","user journeys","branch","map","workflows","architecture","state","leadership","recovery","operations","systems"]