Loading...
Loading...
Found 71 Skills
Documents edge cases, error states, boundary conditions, and recovery paths for a feature. Use during specification to ensure comprehensive coverage, or during QA planning to identify test scenarios.
Cross-phase audit of all outstanding UAT and verification items
Generate test and suite specifications in the strict FinalRun YAML format. Handles automated test planning, folder grouping by feature, repo app configuration, environment-specific overrides in .finalrun/env/*.yaml, and validation via finalrun check.
Create system-level or epic-level test plans. Use when the user says "lets design test plan" or "I want to create test strategy"
Turn a defined feature or refactor into a bounded, implementation-ready plan without changing code.
Suggest tests worth writing for a feature using the ZOMBIES heuristic (Zero, One, Many, Boundaries, Interface, Exceptions, Simple scenarios). Pass a free-text feature description, or omit args to use the current branch's diff. Outputs only the categories that apply — not a full ZOMBIES checklist.
Clicks through every flow of an app clone and tests it for bugs: a test plan generated from the recon flows with happy paths and edge cases, Playwright end-to-end tests where possible, a browser click-through where not, and bug reports in a fixed format with severity, steps and evidence. Use when the user says "test my clone", "find bugs", "QA this", "click through everything", "write e2e tests", "does it work", or after /replica-build or /replica-backend.
Use when discovering possible regressions from a pinned change and its callers before reproduction.
Proves or disproves claims, or the test plan of a PR, by trying to falsify each and rating the strongest evidence reached (PROVEN, PARTIAL, DISPROVEN, UNPROVEN). Changes nothing. Use when the user says "prove it", or when asked to prove, verify, or fact-check claims or a PR test plan with evidence.
Manually link existing TestRail Cases or Plans/Runs back to CawPlan mappings after QA hand-imported or hand-created TestRail artifacts. Link matches requirement_id + test_point_id in refs only (no hash validation). Use when: linking CSV-imported cases by refs; binding hand-made TestPlan/TestRun to CawPlan tickets; 用例回链、refs 映射、Plan Run 绑定、手工导入后 link. Ideal path after A3 CSV import: auto Suite → AutoScan → one confirm. NOT for: creating TestRail cases (use `cawplan-testcase-import`); creating Plans/Runs (use `cawplan-testplan-layout`); generating/exporting cases (use `cawplan-testcase-generate`); execution progress or defect filing.
Execute Tests - walks through test cases from the test plan, collects results, and updates the plan. Use when verifying a feature implementation.