[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSB504BSMG2SQNJGNPA8C8":3,"skill-same:01M7CSB504BSMG2SQNJGNPA8C8":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CSB504BSMG2SQNJGNPA8C8","backlog-prioritization",null,"Use when ordering board tasks - set priority\u002Fblocked_by\u002Fdeploy_depends_on by severity and dependency, split MoSCoW within a feature, and use RICE\u002FICE only for a genuine \"what next\" call across several features","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fbacklog-prioritization\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: backlog-prioritization\ncategory: pm\ndescription: Use when ordering board tasks - set priority\u002Fblocked_by\u002Fdeploy_depends_on by severity and dependency, split MoSCoW within a feature, and use RICE\u002FICE only for a genuine \"what next\" call across several features\nsource: phuryn\u002Fpm-skills prioritization-frameworks (MIT), adapted\n---\n# Backlog Prioritization\n\n## Overview\n\nPrioritization decides what agents pick up next. TaskTrooper is a local, single-user product with no usage data, so a scored framework with invented numbers (fake \"Reach 200\") is theatre. Order by the levers the board actually enforces, and fall back to an explicit estimate only when several same-level features genuinely need ranking.\n\n**Core principle:** `priority`, `blocked_by`, `deploy_depends_on` and backlog\u002Ftodo are the real order. Score only when they tie.\n\n## The real levers\n\n| Lever | What it controls |\n|---|---|\n| `priority` (critical \u002F high \u002F medium \u002F low) | The only persisted order field; sorts `list_ready_tasks` critical-first, then by age. |\n| `blocked_by` | The enforced START order — a task parks in `blocked` while any listed task is open, and is picked up automatically when the last one lands. |\n| `deploy_depends_on` | The enforced SHIP order — this task is not released until the listed ones are live. |\n| backlog vs todo | The human gate — nothing in backlog is picked up; moving to todo starts it. |\n\n## Priority ladder\n\n- **critical** — data loss or corruption, a security exposure, the product unusable, a broken release.\n- **high** — a core flow broken, a regression of shipped behaviour, an analiz that unblocks two or more tasks, a stated deadline.\n- **medium** — default for a requested feature.\n- **low** — cosmetic, nice-to-have, a Should\u002FCould split-off from MoSCoW.\n\n**Within a level:** the stakeholder's stated order, then unblockers (an analiz or a backend task other work depends on), then smaller work first.\n\n## MoSCoW inside a feature\n\nWhen scoping one feature or task:\n- **Must** → this task's `acceptance_criteria`.\n- **Should \u002F Could** → separate backlog tasks, not folded into this one's criteria — one task per repository and role holding all of that feature's Should\u002FCould items, not one task per item.\n- **Won't** → the `description`'s Out of Scope line, with the reason.\n\n## RICE\u002FICE — only for an explicit \"what's next\" call\n\nUse a lightweight score only when the stakeholder asks \"what should we do next\" across three or more same-priority-level features, and label every factor as an estimate with its basis — never invent a reach number with no usage data behind it.\n\n`score = (Impact × Confidence) ÷ Effort` (ICE; drop Reach — there's no multi-user traffic to count). Impact and Confidence are 1–3 with a one-line reason each; Effort is developer-days from the architect's estimate if one exists, otherwise your own rough guess labelled as such.\n\n## Worked Example\n\nThree candidates in `backlog`:\n- A data-loss bug on task delete → `priority: critical`, `todo` immediately — ladder override, no scoring needed.\n- An analiz for reporting that unblocks three planned tasks → `priority: high` (unblocker), `todo`.\n- A new dark-mode toggle the stakeholder mentioned once → `priority: medium`, stays in `backlog` until they confirm it's next.\n\nIf the stakeholder then asks \"dark mode, bulk delete, or CSV export — what first?\": ICE each in one line (dark mode: Impact 1\u002Flow because cosmetic, Confidence 3, Effort 2 → ICE 1.5; bulk delete: Impact 2, Confidence 3, Effort 1 → ICE 6; export: Impact 2, Confidence 2, Effort 3 → ICE 1.3) and recommend bulk delete first, with the basis stated, not just the number.\n\n## Common Mistakes\n\n- Scoring every backlog item with RICE instead of using `priority`\u002F`blocked_by` directly.\n- Inventing a reach\u002Fimpact number with no basis and presenting it as data.\n- A Should\u002FCould item folded into a Must task's criteria instead of split off.\n- Holding work in `backlog` to fake an order that `blocked_by` should enforce.\n\n## Red Flags\n\n- A known data-loss bug sitting below a feature in `priority`.\n- An unblocking analiz left at `medium` or in `backlog`.\n- A RICE score with a \"Reach\" number nobody can source.\n","# Backlog Prioritization\n\n## Overview\n\nPrioritization decides what agents pick up next. TaskTrooper is a local, single-user product with no usage data, so a scored framework with invented numbers (fake \"Reach 200\") is theatre. Order by the levers the board actually enforces, and fall back to an explicit estimate only when several same-level features genuinely need ranking.\n\n**Core principle:** `priority`, `blocked_by`, `deploy_depends_on` and backlog\u002Ftodo are the real order. Score only when they tie.\n\n## The real levers\n\n| Lever | What it controls |\n|---|---|\n| `priority` (critical \u002F high \u002F medium \u002F low) | The only persisted order field; sorts `list_ready_tasks` critical-first, then by age. |\n| `blocked_by` | The enforced START order — a task parks in `blocked` while any listed task is open, and is picked up automatically when the last one lands. |\n| `deploy_depends_on` | The enforced SHIP order — this task is not released until the listed ones are live. |\n| backlog vs todo | The human gate — nothing in backlog is picked up; moving to todo starts it. |\n\n## Priority ladder\n\n- **critical** — data loss or corruption, a security exposure, the product unusable, a broken release.\n- **high** — a core flow broken, a regression of shipped behaviour, an analiz that unblocks two or more tasks, a stated deadline.\n- **medium** — default for a requested feature.\n- **low** — cosmetic, nice-to-have, a Should\u002FCould split-off from MoSCoW.\n\n**Within a level:** the stakeholder's stated order, then unblockers (an analiz or a backend task other work depends on), then smaller work first.\n\n## MoSCoW inside a feature\n\nWhen scoping one feature or task:\n- **Must** → this task's `acceptance_criteria`.\n- **Should \u002F Could** → separate backlog tasks, not folded into this one's criteria — one task per repository and role holding all of that feature's Should\u002FCould items, not one task per item.\n- **Won't** → the `description`'s Out of Scope line, with the reason.\n\n## RICE\u002FICE — only for an explicit \"what's next\" call\n\nUse a lightweight score only when the stakeholder asks \"what should we do next\" across three or more same-priority-level features, and label every factor as an estimate with its basis — never invent a reach number with no usage data behind it.\n\n`score = (Impact × Confidence) ÷ Effort` (ICE; drop Reach — there's no multi-user traffic to count). Impact and Confidence are 1–3 with a one-line reason each; Effort is developer-days from the architect's estimate if one exists, otherwise your own rough guess labelled as such.\n\n## Worked Example\n\nThree candidates in `backlog`:\n- A data-loss bug on task delete → `priority: critical`, `todo` immediately — ladder override, no scoring needed.\n- An analiz for reporting that unblocks three planned tasks → `priority: high` (unblocker), `todo`.\n- A new dark-mode toggle the stakeholder mentioned once → `priority: medium`, stays in `backlog` until they confirm it's next.\n\nIf the stakeholder then asks \"dark mode, bulk delete, or CSV export — what first?\": ICE each in one line (dark mode: Impact 1\u002Flow because cosmetic, Confidence 3, Effort 2 → ICE 1.5; bulk delete: Impact 2, Confidence 3, Effort 1 → ICE 6; export: Impact 2, Confidence 2, Effort 3 → ICE 1.3) and recommend bulk delete first, with the basis stated, not just the number.\n\n## Common Mistakes\n\n- Scoring every backlog item with RICE instead of using `priority`\u002F`blocked_by` directly.\n- Inventing a reach\u002Fimpact number with no basis and presenting it as data.\n- A Should\u002FCould item folded into a Must task's criteria instead of split off.\n- Holding work in `backlog` to fake an order that `blocked_by` should enforce.\n\n## Red Flags\n\n- A known data-loss bug sitting below a feature in `priority`.\n- An unblocking analiz left at `medium` or in `backlog`.\n- A RICE score with a \"Reach\" number nobody can source.\n",{"name":5,"source":24,"category":25,"description":7},"phuryn\u002Fpm-skills prioritization-frameworks (MIT), adapted","pm","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fbacklog-prioritization",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill backlog-prioritization",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill backlog-prioritization",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill backlog-prioritization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fbacklog-prioritization\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]