write-tests — dev-flow

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.

Does not install test packages. That's module-add test. If vitest isn't in package.json, this skill stops and routes there.
Does not run a full test suite. It runs only the new test in isolation to verify it passes. Full suite runs are CI's job.
Does not fix failing tests. A failing test is a signal, not a problem. Surface it to the user; the user decides whether to fix the test or fix the source.
Does not generate coverage reports. Coverage is a separate concern; the user can wire vitest --coverage themselves once they have enough tests.
Does not write tests for shadcn primitives or third-party libs. Test the project's own logic, not the dependencies.

/plugin install dev-flow@dev-flow      # the whole suite
./install.sh --platform claude        # or drop dist/write-tests.skill into Claude Code