and-implement
AND Implement
Implement the complete claimed delivery unit from its GitHub Package Contract. Work in one isolated worktree and finish with a committed, verified, reviewed diff plus durable implementation evidence.
Runtime Contracts
Use and-workflow-contract for the delivery unit, ownership, relationships, blockers, receipts, and Read Deployment Handoff. Read deployment-handoff.md before finalizing the reviewed implementation handoff. Route incomplete setup or a missing contract to setup-and.
Real tdd and code-review skills are required. If either is unavailable, name the missing skill and stop with the documented installation route. Give tdd the Package Contract's agreed seam as confirmed input where test-first work is practical. Use code-review against the retained fixed point with the complete Package Contract and every acceptance-bearing PRD child supplied as the Spec.
Preconditions
Begin only when the current actor owns or is delegated the complete open ready-for-agent delivery unit and no external blocker remains. A PRD claim covers its parent and every child.
Route an unready or unowned unit to the smallest upstream AND skill. If the current head already has clean implementation evidence and an authoritative Deployment disposition, plus a complete Deployment Manifest when that disposition is custom, route to and-finish. If implementation and review are clean but the disposition or required custom Manifest is missing or stale, resume at deployment classification and handoff; route a linked non-authoritative finish proposal to and-finish before implementation resumes.