tdd

<!-- rig-generated --> # tdd+ — Disciplined Implementation Wraps `superpowers:test-driven-development`. Requires superpowers to be installed. **This skill activates tdd+ phase in the enforcement layer.** During this phase: - Full test suite runs are redirected (use scoped tests only) - Stale test warnings fire when source edits lack test updates - Active enforcement rules from session context are enforced (see session-start output; real dependencies in stack/E2E (integration-layer) tests by default) ## Procedure ### Phase A: Setup 1. Announce phase entry: ``` Now using tdd+ skill. Enforcement layer active: - Test scope: scoped runs only (full suite reserved for verify+) - Stale tests: warnings when source edited without test updates - Zero-defect: every failure must be fixed before proceeding ``` 2. Load the plan from `docs/plans/`. 3. Identify the task(s) to implement. 4. If branch discipline is active (see session-start output) and you are on a protected branch, create an isolated workspace before implementing — a worktree (`superpowers:using-git-worktrees`) when the plan is multi-task or the working tree is dirty, a plain feature branch otherwise. ### Phase B: Implement Each Task (delegate to superpowers:test-driven-development) 1. For each task in the plan, follow RED-GREEN-REFACTOR: **RED — Write the failing test first:** - Write a test that captures the task's requirement - Use full-loop assertions where applicable: ...