[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSFQN8BT5FM58EMRF19GTT":3,"skill-same:01M7CSFQN8BT5FM58EMRF19GTT":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},"01M7CSFQN8BT5FM58EMRF19GTT","test-scenario-design",null,"Use while deriving cases - Given\u002FWhen\u002FThen and the techniques (partitions, boundaries, decision tables, state transitions) that find the cases the criteria do not state","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\u002Fqa-agent\u002Fskills\u002Ftest-scenario-design\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-scenario-design\ncategory: qa\ndescription: Use while deriving cases - Given\u002FWhen\u002FThen and the techniques (partitions, boundaries, decision tables, state transitions) that find the cases the criteria do not state\n---\n# Test Case Design\n\nWrite each case as Given (preconditions), When (action via the real endpoint or UI), Then (the observable result). The Then is the `expected` field: state it before you run anything, or you will be judging the output against whatever it turns out to be.\n\n## Two sources, in this order\n\n1. **What was asked for.** At least one case per acceptance criterion, linked with `criterion_id`.\n2. **What it implies.** The behaviour a reasonable person expects from the request even though nobody wrote it down. These are the cases with no `criterion_id`, and they are where defects actually live.\n\n## Techniques for finding the implied cases\n\n- **Equivalence partitioning:** group inputs into classes that should behave alike (valid email \u002F invalid-format email \u002F empty), then test one representative per class instead of guessing randomly.\n- **Boundary value analysis, 3-value:** for every limit, test min−1, min, min+1, max−1, max, max+1 — off-by-one errors live exactly at these six points.\n- **Decision table:** when a result depends on several conditions combined (role × state × flag), write the table and test the combinations that differ in outcome, not just each condition alone.\n- **State transition:** model the valid states and the moves between them, then test the invalid moves too — cancel a completed item, edit after archive, submit twice.\n- **Zero-One-Many \u002F Some-None-All:** for anything list-shaped, test zero items, one item, many items; for anything that can apply to a set, test it applying to none, some, all.\n- **Interrupt and repeat:** double-click a submit button, use the back button mid-flow, open the same record in two tabs, refresh mid-flow.\n- **\"Is this actually a bug?\" oracles:** compare the observed behaviour against the product's own history (did it used to work differently), its own other screens (image), comparable products, the explicit claims in the task\u002Fdocs, what a reasonable user would expect, the stated purpose of the feature, and plain consistency with itself — an oddity that fails none of these is a style choice, not a defect.\n\n## Sources of \"what the request implies\"\n\nThe acceptance criteria, the human's comments, the analysis spec (`list_task_documents` — the behaviour statements are oracles, the implementation plan is not), and `list_links` (dependencies the change touches imply side-effect and failure cases).\n\n## Rejecting a case\n\nRejecting a case is a result, not a deletion. When you work one out and decide it does not apply, record it with `status=invalid` and say why in `notes`. The three reasons that recur: it contradicts the stated spec, it is unreachable in this deployment, or it belongs to a different task. A reviewer reading your round has to be able to see that you considered it.\n\n## Worked Example\n\n\"Users can rename a project (1-80 chars, unique per workspace)\":\n\n- Happy path: rename to a new unique 40-char name → 200, name updated (`happy_path`).\n- Boundary: 1 char, 80 chars, 81 chars (`boundary` x3).\n- Negative: empty string, whitespace-only, name already used in this workspace (`negative` x3).\n- Auth: rename another workspace's project → 403 (`auth`).\n- Empty state: rename the only project in an otherwise-empty workspace (`empty_state`).\n- Regression: project list sort order still correct after rename (`regression`).\n- Invalid, rejected: \"rename while another user is renaming the same project\" — `status=invalid`, \"no optimistic-locking requirement in the spec, out of scope\".\n- Invalid, rejected: \"rename via the public API\" — `status=invalid`, \"this endpoint is UI-only per the spec\".\n\nAbout 10-12 cases across categories, two of them `invalid` with reasons.\n\nIf an acceptance criterion cannot be tested as written: when there is a concrete choice between two readings, `ask_user` with the readings as options (qa-verify-before-verdict's blocker triage) and continue testing what you can meanwhile. When it is simply unclear in a way with no concrete reading to offer, reject it via `review_criterion` with \"untestable as written: \u003Cwhy> — needs a sharper criterion\" and let the move to need_revision surface it on the card — a comment asking the PM to sharpen it reaches nobody, since the PM is not subscribed to in_qa.\n","# Test Case Design\n\nWrite each case as Given (preconditions), When (action via the real endpoint or UI), Then (the observable result). The Then is the `expected` field: state it before you run anything, or you will be judging the output against whatever it turns out to be.\n\n## Two sources, in this order\n\n1. **What was asked for.** At least one case per acceptance criterion, linked with `criterion_id`.\n2. **What it implies.** The behaviour a reasonable person expects from the request even though nobody wrote it down. These are the cases with no `criterion_id`, and they are where defects actually live.\n\n## Techniques for finding the implied cases\n\n- **Equivalence partitioning:** group inputs into classes that should behave alike (valid email \u002F invalid-format email \u002F empty), then test one representative per class instead of guessing randomly.\n- **Boundary value analysis, 3-value:** for every limit, test min−1, min, min+1, max−1, max, max+1 — off-by-one errors live exactly at these six points.\n- **Decision table:** when a result depends on several conditions combined (role × state × flag), write the table and test the combinations that differ in outcome, not just each condition alone.\n- **State transition:** model the valid states and the moves between them, then test the invalid moves too — cancel a completed item, edit after archive, submit twice.\n- **Zero-One-Many \u002F Some-None-All:** for anything list-shaped, test zero items, one item, many items; for anything that can apply to a set, test it applying to none, some, all.\n- **Interrupt and repeat:** double-click a submit button, use the back button mid-flow, open the same record in two tabs, refresh mid-flow.\n- **\"Is this actually a bug?\" oracles:** compare the observed behaviour against the product's own history (did it used to work differently), its own other screens (image), comparable products, the explicit claims in the task\u002Fdocs, what a reasonable user would expect, the stated purpose of the feature, and plain consistency with itself — an oddity that fails none of these is a style choice, not a defect.\n\n## Sources of \"what the request implies\"\n\nThe acceptance criteria, the human's comments, the analysis spec (`list_task_documents` — the behaviour statements are oracles, the implementation plan is not), and `list_links` (dependencies the change touches imply side-effect and failure cases).\n\n## Rejecting a case\n\nRejecting a case is a result, not a deletion. When you work one out and decide it does not apply, record it with `status=invalid` and say why in `notes`. The three reasons that recur: it contradicts the stated spec, it is unreachable in this deployment, or it belongs to a different task. A reviewer reading your round has to be able to see that you considered it.\n\n## Worked Example\n\n\"Users can rename a project (1-80 chars, unique per workspace)\":\n\n- Happy path: rename to a new unique 40-char name → 200, name updated (`happy_path`).\n- Boundary: 1 char, 80 chars, 81 chars (`boundary` x3).\n- Negative: empty string, whitespace-only, name already used in this workspace (`negative` x3).\n- Auth: rename another workspace's project → 403 (`auth`).\n- Empty state: rename the only project in an otherwise-empty workspace (`empty_state`).\n- Regression: project list sort order still correct after rename (`regression`).\n- Invalid, rejected: \"rename while another user is renaming the same project\" — `status=invalid`, \"no optimistic-locking requirement in the spec, out of scope\".\n- Invalid, rejected: \"rename via the public API\" — `status=invalid`, \"this endpoint is UI-only per the spec\".\n\nAbout 10-12 cases across categories, two of them `invalid` with reasons.\n\nIf an acceptance criterion cannot be tested as written: when there is a concrete choice between two readings, `ask_user` with the readings as options (qa-verify-before-verdict's blocker triage) and continue testing what you can meanwhile. When it is simply unclear in a way with no concrete reading to offer, reject it via `review_criterion` with \"untestable as written: \u003Cwhy> — needs a sharper criterion\" and let the move to need_revision surface it on the card — a comment asking the PM to sharpen it reaches nobody, since the PM is not subscribed to in_qa.\n",{"name":5,"category":24,"description":7},"qa","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Ftest-scenario-design",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 test-scenario-design",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill test-scenario-design",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill test-scenario-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fqa-agent\u002Fskills\u002Ftest-scenario-design\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",[],[]]