implement-plus
Implement Plus
Implement the work described by a ticket, a spec, or the conversation — one ticket per session, test-first, verified end to end.
Pipeline position: to-spec-plus (record) → to-tickets-plus (slice) → implement-plus (build).
Process
1. Load and claim the work
Given a ticket reference, fetch its full body and comments, plus the parent spec if it links one (tracker fast path: docs/agents/issue-tracker.md → ## Issue tracker section in AGENTS.md/CLAUDE.md → detect Linear MCP / GitHub gh / local markdown). On a shared tracker, claim it first — assign it to the driving dev — so concurrent sessions skip it. Confirm its blockers are all closed; if not, say so and stop rather than building on sand.
Given only conversation context, restate the scope in two or three lines before starting.
2. Confirm the seams
Tests go at pre-agreed seams — the public boundaries where behavior is observed (see references/tdd-laravel.md for the seam ladder). If the spec already agreed them, use those. If not, propose seams and confirm via AskUserQuestion before writing any test.