[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CTG360SZV7BD425CM00058":3,"skill-same:01M6CTG360SZV7BD425CM00058":65},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":54},"01M6CTG360SZV7BD425CM00058","sprint-prioritizer",null,"Ranks features and work items by impact, effort and risk. Use when planning a sprint or deciding what to build next.","vibbs\u002Fcompany-os","vibbs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7379149?v=4","01M6CT6M03CAS1H7RA89F3965B","Vibbs Dod","01M6CT6M4MY60C9FFQ3AAR2RSK",6,"MIT","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fsprint-prioritizer\u002FSKILL.md",[],[19,20,21,22,23,24,25],"sprint prioritizer","planning","risk","work","use","build","next","2026-11-10 10:12:30",false,"---\nname: sprint-prioritizer\ndescription: Ranks features and work items by impact, effort and risk. Use when planning a sprint or deciding what to build next.\nruntimes:\n  claude:\n    user-invocable: true\n---\n\n# Sprint Prioritizer\n\n## Reference\n- **ID**: S-PROD-03\n- **Category**: Product\n- **Inputs**: feature backlog, impact estimates, effort estimates, risk assessments, strategic goals\n- **Outputs**: prioritized sprint plan → artifacts\u002Fproduct\u002F\n- **Used by**: Product Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\nTakes a backlog of features and work items and produces a prioritized sprint plan by scoring each item on impact, effort, and risk, ensuring the team works on the highest-value items first.\n\n## Procedure\n\n### Step 0: Define Sprint Capacity\n\nBefore prioritization, establish capacity constraints:\n- **Sprint duration**: default 2 weeks (configurable)\n- **Available hours**: default for solopreneur is 28h productive per week (56h per sprint)\n- **Effort scale**: 1 = 1 day, 2 = 3 days, 3 = 1 week, 4 = 2 weeks, 5 = 3+ weeks (split required)\n- **Default weights**: Impact 40%, Effort 30%, Risk 20%, Strategic Alignment 10%\n\nRead `company.stage` from config — at `idea`\u002F`mvp`, bias toward Impact weight (50%) and reduce Strategic Alignment (0%) since survival trumps strategy.\n\n### Steps\n1. Collect the candidate feature\u002Fwork-item backlog for the upcoming sprint.\n2. For each item, score **impact** (1-5): user value, revenue potential, strategic alignment.\n3. For each item, score **effort** (1-5): engineering complexity, dependencies, unknowns.\n4. For each item, score **risk** (1-5): technical risk, market risk, dependency risk.\n5. Calculate a priority score: `(Impact * weight) \u002F (Effort + Risk)` using agreed weights.\n6. Rank items by priority score, highest first.\n7. Apply capacity constraints — fit items into available sprint capacity.\n8. Flag items with high risk that may need spikes or de-risking work first.\n9. Produce the prioritized sprint plan with rationale for top selections.\n10. Save to `artifacts\u002Fproduct\u002F` and validate using `.\u002Ftools\u002Fartifact\u002Fvalidate.sh`.\n\n## Quality Checklist\n- [ ] All candidate items have impact, effort, and risk scores\n- [ ] Scoring criteria are consistent across items\n- [ ] Sprint capacity constraints are applied realistically\n- [ ] High-risk items have mitigation plans or spike tasks\n- [ ] Top priorities align with current strategic goals\n- [ ] Rationale is documented for any overrides of the calculated ranking\n- [ ] Artifact passes validation\n","# Sprint Prioritizer\n\n## Reference\n- **ID**: S-PROD-03\n- **Category**: Product\n- **Inputs**: feature backlog, impact estimates, effort estimates, risk assessments, strategic goals\n- **Outputs**: prioritized sprint plan → artifacts\u002Fproduct\u002F\n- **Used by**: Product Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\nTakes a backlog of features and work items and produces a prioritized sprint plan by scoring each item on impact, effort, and risk, ensuring the team works on the highest-value items first.\n\n## Procedure\n\n### Step 0: Define Sprint Capacity\n\nBefore prioritization, establish capacity constraints:\n- **Sprint duration**: default 2 weeks (configurable)\n- **Available hours**: default for solopreneur is 28h productive per week (56h per sprint)\n- **Effort scale**: 1 = 1 day, 2 = 3 days, 3 = 1 week, 4 = 2 weeks, 5 = 3+ weeks (split required)\n- **Default weights**: Impact 40%, Effort 30%, Risk 20%, Strategic Alignment 10%\n\nRead `company.stage` from config — at `idea`\u002F`mvp`, bias toward Impact weight (50%) and reduce Strategic Alignment (0%) since survival trumps strategy.\n\n### Steps\n1. Collect the candidate feature\u002Fwork-item backlog for the upcoming sprint.\n2. For each item, score **impact** (1-5): user value, revenue potential, strategic alignment.\n3. For each item, score **effort** (1-5): engineering complexity, dependencies, unknowns.\n4. For each item, score **risk** (1-5): technical risk, market risk, dependency risk.\n5. Calculate a priority score: `(Impact * weight) \u002F (Effort + Risk)` using agreed weights.\n6. Rank items by priority score, highest first.\n7. Apply capacity constraints — fit items into available sprint capacity.\n8. Flag items with high risk that may need spikes or de-risking work first.\n9. Produce the prioritized sprint plan with rationale for top selections.\n10. Save to `artifacts\u002Fproduct\u002F` and validate using `.\u002Ftools\u002Fartifact\u002Fvalidate.sh`.\n\n## Quality Checklist\n- [ ] All candidate items have impact, effort, and risk scores\n- [ ] Scoring criteria are consistent across items\n- [ ] Sprint capacity constraints are applied realistically\n- [ ] High-risk items have mitigation plans or spike tasks\n- [ ] Top priorities align with current strategic goals\n- [ ] Rationale is documented for any overrides of the calculated ranking\n- [ ] Artifact passes validation\n",{"name":5,"runtimes":31,"description":7},{"claude":32},{"user-invocable":33},true,"main","e842fb6d0e04360c47db78bc2e2e2987314d64d4","os\u002Fskills\u002Fsprint-prioritizer",2,"https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os","https:\u002F\u002Fgithub.com\u002Fvibbs","Principal Engineer · Applied AI · building ArcAI @ GrowthArc","2026-10-21 02:08:08",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":33},[44,47,50],{"tool":45,"command":46},"npx","npx skills add vibbs\u002Fcompany-os --skill sprint-prioritizer",{"tool":48,"command":49},"bunx","bunx skills add vibbs\u002Fcompany-os --skill sprint-prioritizer",{"tool":51,"command":52},"pnpm","pnpm dlx skills add vibbs\u002Fcompany-os --skill sprint-prioritizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fsprint-prioritizer\u002FSKILL.md",[55,61],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"agents\u002Fopenai.yaml","REFERENCE","参考文档",366,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FReverse-Analysis\u002Fcompetition-prompt-injection\u002Fagents\u002Fopenai.yaml",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fprompt-injection.md",996,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FReverse-Analysis\u002Fcompetition-prompt-injection\u002Freferences\u002Fprompt-injection.md",[66,75,83,93,109,126],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":26},"01M6CTHBW1E64ECYGD105N4S5E","typo-field","Fixture skill with a misspelled top-level field.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Ftypo-field\u002FSKILL.md",[],[73,74],"typo field","fixture skill",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":26},"01M6CTHABTV8FKVDHFMMKPAV51","spaced-comments","Fixture skill with comments and spaces after block keys.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fspaced-comments\u002FSKILL.md",[],[82,74],"spaced comments",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":26},"01M6CTH8MHC14KB65ZDHYBJW1N","crlf-comments","Fixture skill with Windows line endings.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fcrlf-comments\u002FSKILL.md",[],[90,91,92,74],"crlf comments","CRLF","windows",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":26},"01M6CTH6TBKTDP9G8QB1Z2K0TY","claude-fields","Fixture skill using top-level fields Claude Code documents.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fclaude-fields\u002FSKILL.md",[],[100,101,102,103,104,105,74,106,107,108],"claude fields","explore","documents","src","grep","read","Bash","code","testing",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"publishedAt":26},"01M6CTH46BGKXH80RWS876Y2CW","workflow-router","Maps an objective to the artifacts, stages and agents it needs. Use when deciding what happens next or which agents to involve.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[121,122,123,25,124,23,125],"workflow","router","workflow router","maps","artifacts",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":26},"01M6CTH27653SRVP2FMEQN3J5B","weekly-review","Summarizes your week: what shipped, AI spend, support themes, security health and next priorities. Use at the end of each week.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[133,134,135,25,23,136,137,138,139],"weekly review","review","priorities","health","save","support","security"]