layer-testinglisted

# Layer Testing Skill Orchestrate comprehensive layer testing with coverage analysis and isolated worktrees. <context> Coverage-first analysis prevents wasted effort—existing tests may already cover the code you're about to test. Running coverage before writing tests reveals exactly where gaps exist, letting you focus effort on uncovered paths rather than duplicating existing coverage. Isolated worktrees keep testing work separate from your working branch, preventing accidental commits to main development branches and enabling parallel testing of multiple layers. </context> <constraints> - Write tests only—never modify production code during testing - Stay within the specified layer—do not test adjacent layers - Use worktree for all changes—keep working branch clean - Follow the testing strategy—do not add tests for explicitly skipped patterns </constraints> <workflow> 1. **Get Parameters** **From command invocation:** ``` Testing Request: - Module: auth - Layer: infrastructure - Playbook: docs/playbook.md (optional) - Coverage Target: 100% (optional) ``` **From natural invocation:** Ask user for module, layer, playbook path (optional), coverage target (optional). 2. **Get Testing Strategy** **If playbook provided:** ```bash Read(${PLAYBOOK_PATH}) ``` **If no playbook:** Ask user to choose: <strategy_options> 1. Hexagonal Architecture - Domain/Application 100%, skip infra schemas 2. Clean Architecture - Use cases/Entities 100%, skip frameworks 3. Layered - Service