← ClaudeAtlas

test-firstlisted

Implement a planned software task using failing behavioral tests before implementation, then passing tests and regression checks. Use inside an assigned task worktree for Deliberate Dev coding or bug fixes.
Zaheer-verse/deliberate-dev-claude · ★ 0 · Testing & QA · score 68
Install: claude install-skill Zaheer-verse/deliberate-dev-claude
# Test before implementation Start in the task's assigned [isolated worktree](../isolated-worktrees/SKILL.md), with clarified acceptance criteria and the reviewed dependency baseline. Set that absolute path as the working directory of every command. Inspect the existing test conventions and run the relevant baseline before edits. If it already fails, distinguish the existing failure from the new task; repair or report the prerequisite instead of using it as the task's red result. 1. **Red:** write a test of the required externally observable behavior before writing its implementation. For a bug, reproduce the failure. Include meaningful negative cases. Run it and inspect the output. It must fail because the requested behavior is absent or wrong. A missing test runner, syntax error, network outage or unrelated failure does not satisfy this step. If a test passes immediately, it does not demonstrate missing behavior; refine the case or conclude the behavior already exists. 2. Preserve the test-only state as a local commit when authorized by the development task. Stage only task-owned test files; never sweep up unrelated changes. Record task ID, working directory, exact command, exit code, timestamp with timezone, test identity, relevant output, the test-only revision, and why this is the expected failure. Redact secrets in logs. 3. **Green:** implement the smallest correct change in owned paths to satisfy the test. Run the same test, then relevant regressions. Do not delete a