implement

# Test-driven implementation Implement the smallest scope-complete approved slice with tests or proof first. Do not expand scope, silently alter the contract, or claim success without direct evidence. ## Workflow role - role_name: implement - stage: execution - upstream: approved spec, active plan, active test spec plus recorded, approved, current test-spec-review evidence when required, accepted review-resolution finding, bugfix request, or isolated implementation request with clear scope - downstream: code-review - summary: Implement one scope-complete slice, record validation evidence, and hand it to code-review. - must_not_claim: review passed, clean review, branch readiness, PR readiness, final verification, final closeout readiness, or derived artifact currency without owning proof. For planned initiatives, treat the plan and upstream artifacts as read-only. Write implementation, tests, and implementation evidence only; workflow owns milestone and routing state. ## Quick operating guide Use this skill to: - implement one approved milestone or isolated request with proof first. Read first: - change-local state when planned; - the current milestone, governing spec, active test spec, recorded review evidence, relevant code/tests, and validation commands. Produce: - tests or proof, implementation, validation evidence, and a code-review handoff. Stop when: - authority, scope, proof, or validation is missing, contradictory, stale, or failing. Do not claim: - review,...