[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSCGJ3BPC6HAR06V0RKPET":3,"skill-same:01M7CSCGJ3BPC6HAR06V0RKPET":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},"01M7CSCGJ3BPC6HAR06V0RKPET","requirements-writing",null,"Use when capturing what a feature must do - write testable user-story requirements that state WHAT and WHY, never HOW, with assumptions made explicit","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\u002Frequirements-writing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: requirements-writing\ncategory: pm\ndescription: Use when capturing what a feature must do - write testable user-story requirements that state WHAT and WHY, never HOW, with assumptions made explicit\n---\n# Requirements Writing\n\n## Overview\n\nA requirement is a promise about behavior, written so QA can later prove it and a developer can build it without guessing. The recurring failures are requirements that specify implementation (HOW), bundle several behaviors into one, or hide assumptions that later surface as defects.\n\n**Core principle:** State WHAT and WHY. HOW belongs to the architect and developers.\n\n## The shape\n\n- **User story:** As [persona], I want [capability], so that [outcome].\n- **Context:** why now, what problem it solves.\n- **Constraints:** hard limits (locale, performance, compliance) treated as given.\n- **Assumptions:** stated explicitly — an unstated assumption becomes a defect.\n\n## Rules\n\n- **WHAT\u002FWHY, not HOW — but field-aware.** `description` and `acceptance_criteria` state WHAT and WHY: \"Users can export tasks to CSV\" — not \"add a `\u002Fexport` endpoint using library X.\" Endpoints, files and tables belong only in `technical_description`, only once verified with code tools (`get_repo_tree`, `codebase_search`\u002F`grep_code`), and only for small direct tasks you write yourself. A criterion may name an endpoint only when the API itself is the product surface (see acceptance-criteria-gwt's API-surface example) — not as a stand-in for what a user sees.\n- **Independently testable.** If a requirement contains \"and\", consider splitting.\n- **No solutioning in `description`\u002F`acceptance_criteria`.** Naming a datastore, framework, or endpoint there is an architect\u002Fdev decision leaking in, even though the same name is correct in `technical_description`.\n\n## Worked Example\n\n```\n❌ \"Add a Redis cache to the task list endpoint so it's fast.\"\n   (HOW — names the tech; \"fast\" is untestable)\n\n✅ Story: As a project member, I want the task list to load quickly,\n          so that I can scan my board without waiting.\n   Context: boards with 500+ tasks feel sluggish today.\n   Constraint: list renders \u003C 500ms at p95 for 1000 tasks.\n   Assumption: 1000 tasks is the realistic upper bound per project.\n```\n\nThe architect chooses caching vs indexing vs pagination — the requirement fixes only the outcome and the bound.\n\n## Common Mistakes\n\n- Prescribing the implementation.\n- \"Fast\u002Fintuitive\u002Frobust\" with no measurable target.\n- One requirement covering three behaviors.\n- Assumptions left unstated.\n\n## Red Flags\n\n- The requirement names a library, table, or endpoint.\n- You can't say how QA would prove it.\n- An adjective where a number belongs.\n","# Requirements Writing\n\n## Overview\n\nA requirement is a promise about behavior, written so QA can later prove it and a developer can build it without guessing. The recurring failures are requirements that specify implementation (HOW), bundle several behaviors into one, or hide assumptions that later surface as defects.\n\n**Core principle:** State WHAT and WHY. HOW belongs to the architect and developers.\n\n## The shape\n\n- **User story:** As [persona], I want [capability], so that [outcome].\n- **Context:** why now, what problem it solves.\n- **Constraints:** hard limits (locale, performance, compliance) treated as given.\n- **Assumptions:** stated explicitly — an unstated assumption becomes a defect.\n\n## Rules\n\n- **WHAT\u002FWHY, not HOW — but field-aware.** `description` and `acceptance_criteria` state WHAT and WHY: \"Users can export tasks to CSV\" — not \"add a `\u002Fexport` endpoint using library X.\" Endpoints, files and tables belong only in `technical_description`, only once verified with code tools (`get_repo_tree`, `codebase_search`\u002F`grep_code`), and only for small direct tasks you write yourself. A criterion may name an endpoint only when the API itself is the product surface (see acceptance-criteria-gwt's API-surface example) — not as a stand-in for what a user sees.\n- **Independently testable.** If a requirement contains \"and\", consider splitting.\n- **No solutioning in `description`\u002F`acceptance_criteria`.** Naming a datastore, framework, or endpoint there is an architect\u002Fdev decision leaking in, even though the same name is correct in `technical_description`.\n\n## Worked Example\n\n```\n❌ \"Add a Redis cache to the task list endpoint so it's fast.\"\n   (HOW — names the tech; \"fast\" is untestable)\n\n✅ Story: As a project member, I want the task list to load quickly,\n          so that I can scan my board without waiting.\n   Context: boards with 500+ tasks feel sluggish today.\n   Constraint: list renders \u003C 500ms at p95 for 1000 tasks.\n   Assumption: 1000 tasks is the realistic upper bound per project.\n```\n\nThe architect chooses caching vs indexing vs pagination — the requirement fixes only the outcome and the bound.\n\n## Common Mistakes\n\n- Prescribing the implementation.\n- \"Fast\u002Fintuitive\u002Frobust\" with no measurable target.\n- One requirement covering three behaviors.\n- Assumptions left unstated.\n\n## Red Flags\n\n- The requirement names a library, table, or endpoint.\n- You can't say how QA would prove it.\n- An adjective where a number belongs.\n",{"name":5,"category":24,"description":7},"pm","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Frequirements-writing",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 requirements-writing",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill requirements-writing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill requirements-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Frequirements-writing\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",[],[]]