generate-tests

# Generate Tests Skill Generate high-quality, behavior-driven test files from acceptance criteria or existing source code. This skill auto-detects the project's test framework, loads framework-specific patterns, and spawns test-writer agents to produce runnable test files that follow project conventions. **CRITICAL: Complete ALL 6 phases.** The workflow is not complete until Phase 6: Report is finished. After completing each phase, immediately proceed to the next phase without waiting for user prompts. ## Core Principles 1. **Tests before implementation** -- Generated tests should initially fail (RED state) when no implementation exists, confirming they test real behavior. 2. **Behavior over implementation** -- Test what the code does, not how it does it. Tests should survive refactoring. 3. **Follow project conventions** -- Match the project's existing test framework, file naming, directory structure, and assertion patterns. 4. **Standalone operation** -- This skill works independently. It does not require the SDD pipeline, `tdd-cycle`, or any other skill to function. ## AskUserQuestion is MANDATORY **IMPORTANT**: You MUST use the `AskUserQuestion` tool for ALL questions to the user. Never ask questions through regular text output. - Framework selection questions -> AskUserQuestion - Clarifying questions about scope -> AskUserQuestion - Confirmation questions -> AskUserQuestion Text output should only be used for presenting information, summaries, and progress update...