run-test-phase

Run Vitest tests for a specific phase by invoking the skill with a phase identifier. It reads your test-plan.md, resolves the mapped test files for that phase, and executes Vitest with a JSON report to speed up multi-phase feedback loops.

Phase-based testing organizes a test suite into distinct stages mapped to specific features. A test-plan.md file defines these mappings, allowing test runners to resolve and execute only the test files relevant to a chosen phase rather than the full suite.

Generate a JSON test report by running Vitest with JSON output enabled. The skill writes this output to test.result.json and automatically triggers qa-specialist analysis on any detected failures to provide diagnostic insights.

Yes, you can run phase-specific tests without a manual identifier. If no phase is provided, the skill reads test-plan.md and uses AskUserQuestion to prompt you interactively to select the desired phase for testing.

Yes, a test-plan.md file is required. The skill relies on this file to identify available phases and map specific features to their corresponding test files before resolving and executing the targeted Vitest tests.

Multi-phase test suites take long because they run all tests globally. Speed up feedback by using phase-based testing to execute only the Vitest tests mapped to your active development phase, bypassing the full suite.