← ClaudeAtlas

testcase-artisanlisted

Creates and maintains structured test case specifications (what to test, not test code) for app features, derived from the project's docs. Use when the user asks for test cases, test scenarios, or coverage planning, including phrasing like "write test cases for login", "what should we test in the SSO flow", "what scenarios does this need", "update the test cases, I just added SSO", or "which features have no test cases yet". Do NOT use when the user wants test code written or tests run, even if they say "test" (e.g. "run the smoke tests", "write the UI test for SSO", "make tests for checkout") - that is testrun-forgemaster's job. This skill only produces test case specification documents in markdown.
zhuhrymhd/quality-atelier · ★ 0 · Testing & QA · score 67
Install: claude install-skill zhuhrymhd/quality-atelier
# Testcase Artisan Turns project documentation into structured, maintainable test case specifications. Read this whole file before doing anything - the steps below depend on each other. ## Boundary This skill produces one thing: markdown files describing what should be tested and why, under `docs/test-cases/`. It never writes XCTest/XCUITest/Jest/etc. code, and it never runs a build or a simulator. If the user asks to actually implement or run tests, that's testrun-forgemaster's job. The `Level test` field this skill writes on each test case is the reference that downstream skills follow. testrun-forgemaster implements each test case at the level written here; if it thinks another level fits better, it only records that as a suggestion in its report and never changes these files. So classify `Level test` carefully using the rule in `references/field-format.md` - it is not a loose hint. ## Step 1: Figure out the mode There is no special phrasing for "generate" vs "update" vs "audit" - infer the mode from what's on disk and what the user asked for: - User named a specific feature (or one is obvious from context) → **scoped mode**. Check whether `docs/test-cases/<feature>.md` already exists. - Doesn't exist → **generate**: build the file from scratch (Step 4 onward). - Exists → **update**: read it first, then reconcile against current docs (Step 5). - User asked something like "what's missing", "audit coverage", or gave no specific feature at all → **gap-audit mod