implement

Implement the work described by the user in the spec or tickets.

If the user passes a ticket reference, fetch it from the issue tracker and state its title before starting. If the reference is ambiguous, ask.

Call the Skill tool with "meldom:tdd" where possible, at pre-agreed seams.

Run typechecking regularly, single test files regularly, and the full test suite once at the end.

Once done, call the Skill tool with "meldom:code-review" to review the work.

Commit your work to the current branch.

On Meldom

• Review the whole run, then commit. Capture git rev-parse HEAD before building. After all tickets supplied to this run are implemented, run the final checks and call meldom:code-review against that captured commit, covering every ticket together. Fix findings, rerun affected checks and review until there are no findings. Then commit through meldom:ship.
• Claim before building. Move the ticket you are about to build, and its parent spec, to in_progress with mcp__meldom__ticket_batch_update, keyed by each ticket's ULID (the id field), never its KEY-42 key. Work on one child ticket at a time; its parent stays in_progress through final review.
• Report progress. On the first pass, send one plan with exactly one step per ticket, each its ticket's key and sized S, M or L: mcp__meldom__progress({ "goal": "<spec title>", "plan": ["KEY-42:M"] }). Moving a ticket to done marks its step done, so send no done for it. Send { "add": ["KEY-43:S"] } for each ticket added later, and { "finish": true } with the run's last tool call. If the tool is not there after one search, skip every progress call silently.
• Mark each ticket done as it passes. The moment a ticket's acceptance criteria pass, mcp__meldom__ticket_update it to done with a reason, then claim the next one.
• Build what you file. Work the build surfaces beyond the tickets is a follow-up: file it at once with mcp__meldom__ticket_create, parent_id set to the spec or the ticket's own parent, and build it in this session. Before you finish, read mcp__meldom__conversation_status; while any ticket this session created is open, build it. The one exception is a step only a human can take: hand it over through meldom:wizard or a question.
• Record the final review per ticket. For each ticket the review's Spec axis confirms, set mcp__meldom__ticket_outcome({ "id": <ulid>, "outcome": "verified" }). A ticket it contradicts gets "failed", goes back to open, and is built again.
• Close the parent. Parent status never rolls up on its own: after final checks and review pass and every child is done or closed, move the parent to done with reason: "All children done: <summary>", then check its own parent the same way.