write-testslisted

# write-tests — generate tests for one file at a time This skill writes the test file that should sit next to a piece of source code. One invocation = one source file → one test file. It does **not** install test infrastructure (that's `module-add test`), does **not** debug failing tests (that's `superpowers:systematic-debugging`), and does **not** run an HTTP-based QA pass (that's `qa`). The unit of work is **deliberately small** because tests rot when they're auto-generated in bulk. A single file at a time forces the user to read what was written and accept it before moving to the next. ## When this skill applies - The user names a source file: "scrivi i test per `lib/server/clienti.ts`", "test per `app/checkout/page.tsx`", "e2e per /scadenze". - The orchestrator routes here from `module_added` (test infrastructure exists) when the user wants per-feature coverage. - The project has a wired test stack — `meta.json#stack.test` is set, OR `vitest.config.ts` + `playwright.config.ts` exist at the root. ## Contract This skill follows the dev-flow contract — see `references/contracts.md`. Key facts: - Reads `<root>/.workflow/meta.json#stack.test` to confirm the test framework is wired. - Reads the project's existing `vitest.setup.ts`, `vitest.config.ts`, `playwright.config.ts`, and any sibling test files to learn the mocking style — **does not re-prescribe** patterns from scratch. - Writes a single test file alongside the source (`__tests__/<name>.test.ts` for unit, `e2e/<na