Implement with Test

Turn a task into production code plus tests that fit naturally into the existing codebase.

Hard Rules

• Never code without a task definition. Extract Purpose / Requirements / Approach / Verification first — this kills aimless coding and scope creep.
• Follow project patterns; never impose external ones. Code that looks foreign is a maintenance burden even when technically correct.
• Tests are part of the implementation, not an afterthought. Every Verification item maps to at least one test.
• Never report success while tests fail. Run to green (max 3 fix attempts) or report the failure honestly. Green is the definition of "done".
• Minimal diff. Only files the task needs. No refactors of surrounding code, no drive-by "improvements", no unrelated annotations.

Phase 1 — Resolve the task

Exactly two sources:

1. Argument — a file path (specs/*.md, tasks/*.md, any task .md → Read and parse) or a direct natural-language description (parse in place).
2. No argument — infer from recent conversation turns.