scenario-plan-first
Use at the start of every QA round - recording the case matrix with record_test_cases (categories, criterion links, rejected cases) before touching the app, then executing all of it
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 122
- Forks
- 18
01 前言 Front Matter
- name
- scenario-plan-first
- category
- qa
- description
- Use at the start of every QA round - recording the case matrix with record_test_cases (categories, criterion links, rejected cases) before touching the app, then executing all of it
03 SKILL.md 正文
Case Matrix First
Before you boot anything or call anything, derive the cases — from the task description and its acceptance criteria, never from the code or the diff (techniques and sources: test-scenario-design) — and write them onto the task with record_test_cases (status=planned). Never post the plan as a comment; the card is where it lives.
The criteria are the floor, not the ceiling. They summarise the request in a few lines, so start from them and then ask what the person asking would expect to be true once this is built:
- One or more cases per acceptance criterion (happy path), linked with
criterion_id. - The implied cases nobody wrote down, with
criterion_idempty (boundary-negative-testing for the data catalogue). - Backend: the worker/async cases the request implies (worker-job-testing).
- Frontend: the visual cases at all four widths, empty/loading/error states (frontend-manual-testing).
- UI built from an approved design (your context carries "## The approved design this task builds"): the
design:cases per state and width (design-conformance). - A regression case for the adjacent behaviour this change could break (regression-checklist).
- The cases you considered and REJECTED, as
status=invalidwith the reason innotes.
Then execute the matrix in this same run and record every verdict (set_test_case_result): passed, failed with what you actually observed, or skipped with what blocked it. A case still planned when you try to hand the task on refuses the move.
Category mapping
The category enum has no accessibility/performance/security/contract value of its own — map them: a11y → visual + title prefix a11y:; performance → other + perf:; authz/security → auth; contract/compatibility → negative or happy_path depending on the case; concurrency/duplicate submission → negative; worker/async → async.
Title convention
<surface>: <action> -> <expected>, e.g. settings: rename to 81 chars -> 422. Titles are the case's identity across rounds — keep them stable so a re-test (retest-after-revision) matches the right history.
An untestable criterion
Is not a case you invent a proxy for. When there is a concrete choice between two readings, ask_user with the readings as options and leave it unapproved meanwhile. When it is unclear with no concrete reading to offer, reject it via review_criterion ("untestable as written: <why> — needs a sharper criterion") so the move to need_revision puts it in front of the human — a comment asking the PM to sharpen it reaches nobody, since the PM does not subscribe to in_qa.
04 同仓库更多 Skills
visual-craft
暂无简介
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
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
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.
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
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