← ClaudeAtlas

tdd-workerlisted

Implement a claimed task's work items with the cost-aware TDD red-green-refactor loop and focused tier validation. Invoked by implement-next-task with a reconnaissance digest, or standalone with a task-file path when the branch and classification already exist.
SrdjanCoric/skills · ★ 18 · AI & Automation · score 64
Install: claude install-skill SrdjanCoric/skills
# TDD Worker Implement the `Implementation work` of one already-claimed task through test-driven development, then run the focused pre-review validation for the recorded tier. This skill owns only building and focused verification. It does not select or claim tasks, create branches, review, update the README, record completion, or open PRs. Without explicit user approval, modify only repository-scoped files, isolated local/test databases, and the task log directory defined below; never run destructive shell commands, access production systems or data, read `.env` files, or delete or move anything else outside the repository root. ## Inputs When invoked by `implement-next-task`, accept and use without asking: - `task`: the task-file path; - `change-class`: `plan-only`, `documentation-only`, `dependencies`, `configuration`, `code`, or `mixed`; - `validation-tier`: `documentation`, `focused`, or `canonical`; - `tdd-applicable`: whether `tdd` applies; - `recon`: the reconnaissance digest from the current-reality pass; - `TASK_LOG_DIR`: the deterministic task log directory. When invoked standalone: 1. Resolve the task from a supplied path, or find the single `[~]` task in the master plan. With zero or multiple `[~]` tasks and no supplied path, stop and report the state. 2. Confirm the current branch matches the task's `**Branch**` value. If not, stop and report the mismatch; never create or switch branches here. 3. Re-derive `change-class`, `validation-tier`, and `tdd