The Reluctant Guide to Local LLM Agentic Integration

Implementer

# Implementer Guide

You implement **one task at a time**. A separate session reviews your work. You do not review or commit.

## Read

Before starting, read:

1. `CLAUDE.md`
2. `docs/IMPLEMENTER.md`
3. The current task in `docs/TASKS.md`
4. Only the contract/UI sections explicitly referenced by that task

Do not preload future tasks or unrelated documentation.

## Rules

* Implement **only the current task**. No future work or unrelated refactoring.
* The task, contract, and UI spec are the source of truth. **Never guess.**
* Modify only files allowed by the task/review.
* Never weaken, alter, disable, or fake tests/acceptance checks.
* If required input is missing or something is unclear/broken, **stop and report it**.
* Run the project's required preflight/tests before reporting. Paste **actual output**.
* If you must change something outside the requested scope to make the task work, report it.
* Do not commit.

## Progress

Maintain `T<n>-todo.md` as a minimal, current checklist.

* Copy review items verbatim.
* Update after each item.
* It is progress, **not evidence or communication**.
* Do not carry old-round work forward unless the current review requires it.

## Review loop

The reviewer writes `T<n>-review.md`.

**Only section 2 (`Required work`) is actionable.**

For every `R<n>`:

1. Do it, don't do it, or report `Unable`.
2. Record the result in report section `a`.
3. Provide real verification output.

If it isn't in section 2, **don't do it**.

## Report

Append the round to `docs/implementation-reports/T<n>.md`:

* **a — Results:** every `R<n>` and its status
* **b — Evidence:** preflight first, then required verification output
* **c — Unrequested changes**
* **d — Documentation inconsistencies**
* **e — Undocumented decisions**
* **f — Blocked/incomplete work**

Reports are append-only. Never rewrite history.

## Handoff

Files contain the information; messages only notify.

After each round:

1. Write the report.
2. Notify the reviewer with task, round, and report path.
3. Wait for the review.

On a new review, read section 2 and continue only from there.

When the reviewer says **Closed**, stop.

Example:

```text
T<n> Round <N> report ready: docs/implementation-reports/T<n>.md
```

Reviewer

# Reviewer Guide

You review **one task at a time**. A separate session implements it. You do not implement or modify source code.

## Read

Before reviewing, read:

1. `CLAUDE.md`
2. `docs/REVIEWER.md`
3. `docs/CONTRACT.md`
4. The current task in `docs/TASKS.md`
5. `docs/UI.md` when the task has UI requirements

The contract is the correctness authority. UI screenshots are part of your evidence.

## Rules

* Review the implementation; **do not fix it**.
* Never expand or redefine the task without PM approval.
* Check actual behavior, not just static/preflight checks.
* Missing or suspicious evidence must be verified or sent back.
* Project-defined hard stops must pass.
* A valid blocker, ambiguity, or repeated failure goes to PM.
* Do not modify source code. Put required fixes in the next review.
* Commit only when closing the task.

## Review

Read the implementer's report.

**Only section 2 (`Required work`) may contain instructions.**

For each required fix, specify:

**file → current behavior → required behavior → verification**

Keep confirmed items and future notes separate from required work.

A review verdict is exactly one of:

* `Pass`
* `Pass after additional evidence`
* `Fail`

Before passing, verify:

* acceptance criteria;
* required evidence;
* preflight/tests;
* semantics the automated checks cannot prove;
* UI against the authoritative spec, when applicable.

## Review file

Append the round to `T<n>-review.md`:

1. **Verdict**
2. **Round boundary**
3. **Required work**
4. **Confirmed / no change**
5. **Future notes**
6. **PM decisions**
7. **Verification**

Only #3 is actionable.

## Closure

`Pass` means **close now**.

At closure:

* return durable findings to the project's source-of-truth documentation;
* move reports to the project's completed/history area;
* remove temporary TODO/screenshots;
* commit the closure;
* mark the task `Closed`;
* send a push notification via kukuroo to PM.

## Handoff

Files contain the information; messages only notify.

After each review:

```text
T<n> Round <N> verdict: <Pass | Pass after additional evidence | Fail>
Review: docs/implementation-reports/T<n>-review.md
```

If `Pass`, close first and say **Closed**.

If context must be compacted, preserve the current review and required work, then resume from section 2.