[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSCM89M36DKGD2M96Y8THJ":3,"skill-same:01M7CSCM89M36DKGD2M96Y8THJ":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CSCM89M36DKGD2M96Y8THJ","scope-management",null,"Use when defining a feature - name what is in scope, out of scope, and assumed, and handle mid-flight expansion without corrupting in-progress tasks","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\u002Fscope-management\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: scope-management\ncategory: pm\ndescription: Use when defining a feature - name what is in scope, out of scope, and assumed, and handle mid-flight expansion without corrupting in-progress tasks\n---\n# Scope Management\n\n## Overview\n\nScope is defended by what you write DOWN, especially the \"out of scope\" line. Undocumented scope drifts; a task whose AC quietly grows mid-flight is the classic cause of a blown estimate and a bounced UAT.\n\n**Core principle:** Name the boundary explicitly. New scope becomes a new task, never an edit to an in-progress one.\n\n## For every feature, write\n\n- **In scope:** concrete deliverables in this iteration.\n- **Out of scope:** explicitly named items deferred or excluded — this line does the real work.\n- **Assumptions:** constraints treated as given.\n\nTaskTrooper has no epic. For a single direct task, this lives in its own `description`. For a feature that spans several tasks via analiz, it lives on the **analiz task** (`description` or `add_task_document`) — never re-written per implementation task.\n\n## Mid-flight expansion\n\nWhen a request grows while work is in progress: **create a new task** for the expansion. Do NOT edit the AC of an in-progress task — a moving target invalidates the developer's plan and QA's scenarios and silently inflates the estimate.\n\n**Except when the human changes the task themselves.** A comment the task's owner writes ON the task (\"also show the logos in the marquee\"), or their own edit of its description or criteria, is not mid-flight expansion to push back on — it is the task's requirement now. It outranks the original description and its out-of-scope list; every role builds, reviews, tests and accepts against it. Do not split it into a new task or treat it as creep unless the human asks for that.\n\n## MoSCoW inside a feature\n\nMust → this task's `acceptance_criteria`. Should\u002FCould → separate backlog tasks, never folded into this one. Won't → the Out of scope line, with a reason (see backlog-prioritization).\n\n## Dropping a criterion deliberately\n\nUse `cancel_criterion` with a reason when a criterion is descoped, superseded by a later human comment, or moved to another task — never to get past work that simply wasn't done. `cancel_criterion` says \"we're not shipping this here,\" which is a scope decision; a rejected `review_criterion` says \"this doesn't work yet,\" which is a defect. Don't use one for the other.\n\n## A new idea found during UAT\n\nSomething the PM or QA notices in QA or human_uat that nobody asked for is a candidate for a new backlog task (`create_board_task`, priority low, same repository\u002Fproject) — it is never a gap on the current task and never blocks its approval. Only something that breaks a criterion, a human comment, or the original request is a gap.\n\n## Worked Example\n\nFeature: \"task export.\"\n- In scope: CSV export of a project's tasks via the board UI.\n- Out of scope: PDF export, scheduled\u002Femailed exports, custom column selection.\n- Assumptions: export is on-demand; ≤ 10k tasks per project.\n\nMid-sprint the stakeholder says \"also email it weekly.\" That's the out-of-scope \"scheduled export\" — create a new task for it, keep the in-progress CSV task untouched, and tell the stakeholder it's queued separately.\n\n## Common Mistakes\n\n- Omitting the \"out of scope\" line → scope creeps by default.\n- Editing an in-progress task's AC to absorb new asks.\n- \"We'll figure out scope later\" → later is a UAT surprise.\n\n## Red Flags\n\n- A feature with an in-scope list but no out-of-scope list.\n- An in-progress task whose AC changed after work started.\n","# Scope Management\n\n## Overview\n\nScope is defended by what you write DOWN, especially the \"out of scope\" line. Undocumented scope drifts; a task whose AC quietly grows mid-flight is the classic cause of a blown estimate and a bounced UAT.\n\n**Core principle:** Name the boundary explicitly. New scope becomes a new task, never an edit to an in-progress one.\n\n## For every feature, write\n\n- **In scope:** concrete deliverables in this iteration.\n- **Out of scope:** explicitly named items deferred or excluded — this line does the real work.\n- **Assumptions:** constraints treated as given.\n\nTaskTrooper has no epic. For a single direct task, this lives in its own `description`. For a feature that spans several tasks via analiz, it lives on the **analiz task** (`description` or `add_task_document`) — never re-written per implementation task.\n\n## Mid-flight expansion\n\nWhen a request grows while work is in progress: **create a new task** for the expansion. Do NOT edit the AC of an in-progress task — a moving target invalidates the developer's plan and QA's scenarios and silently inflates the estimate.\n\n**Except when the human changes the task themselves.** A comment the task's owner writes ON the task (\"also show the logos in the marquee\"), or their own edit of its description or criteria, is not mid-flight expansion to push back on — it is the task's requirement now. It outranks the original description and its out-of-scope list; every role builds, reviews, tests and accepts against it. Do not split it into a new task or treat it as creep unless the human asks for that.\n\n## MoSCoW inside a feature\n\nMust → this task's `acceptance_criteria`. Should\u002FCould → separate backlog tasks, never folded into this one. Won't → the Out of scope line, with a reason (see backlog-prioritization).\n\n## Dropping a criterion deliberately\n\nUse `cancel_criterion` with a reason when a criterion is descoped, superseded by a later human comment, or moved to another task — never to get past work that simply wasn't done. `cancel_criterion` says \"we're not shipping this here,\" which is a scope decision; a rejected `review_criterion` says \"this doesn't work yet,\" which is a defect. Don't use one for the other.\n\n## A new idea found during UAT\n\nSomething the PM or QA notices in QA or human_uat that nobody asked for is a candidate for a new backlog task (`create_board_task`, priority low, same repository\u002Fproject) — it is never a gap on the current task and never blocks its approval. Only something that breaks a criterion, a human comment, or the original request is a gap.\n\n## Worked Example\n\nFeature: \"task export.\"\n- In scope: CSV export of a project's tasks via the board UI.\n- Out of scope: PDF export, scheduled\u002Femailed exports, custom column selection.\n- Assumptions: export is on-demand; ≤ 10k tasks per project.\n\nMid-sprint the stakeholder says \"also email it weekly.\" That's the out-of-scope \"scheduled export\" — create a new task for it, keep the in-progress CSV task untouched, and tell the stakeholder it's queued separately.\n\n## Common Mistakes\n\n- Omitting the \"out of scope\" line → scope creeps by default.\n- Editing an in-progress task's AC to absorb new asks.\n- \"We'll figure out scope later\" → later is a UAT surprise.\n\n## Red Flags\n\n- A feature with an in-scope list but no out-of-scope list.\n- An in-progress task whose AC changed after work started.\n",{"name":5,"category":24,"description":7},"pm","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fscope-management",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill scope-management",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill scope-management",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill scope-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fscope-management\u002FSKILL.md",true,[],[49,55,62,69,76,83],{"skillNo":50,"name":51,"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":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":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":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",[],[]]