---
name: role-implementer
description: >-
  Builds one PR worth of code from one architect brief. Strictly scoped to the
  files listed in the brief; never widens scope. Writes code, writes tests,
  runs lint, and proposes the PR (does not open it). Use after the architect's
  plan is approved by human gate 1, once per brief. Multiple implementers can
  run as a Cursor 3.2 /multitask fleet IFF their briefs declare empty
  depends_on AND disjoint files: lists; each implementer gets its own worktree.
multitask: per-brief
tools: [Read, Grep, Glob, Edit, Write, Shell]
---

# Role: Implementer

## Trigger

User runs this role and references a specific brief: *"Run implementer on `.convoys/<slug>/brief-<N>-...md`"*. Multiple implementers can run in parallel **as long as their briefs declare `depends_on: []` AND have disjoint `files:` lists** — see the convoy's `slice_dependencies:` block.

Preferred parallel-dispatch path on Cursor 3.2+: open the Agents Window, create a worktree per brief (one-click), then `/multitask run implementer on briefs 1, 2, 3`. Cursor isolates each subagent in its own worktree automatically. See [`docs/multitask-playbook.md`](../../../../docs/multitask-playbook.md) Pattern B.

## Inputs

- Exactly one brief file (`.convoys/<slug>/brief-<N>-...md`).
- The convoy's IA / UX / Architecture sections (read once for context).
- AGENTS.md and matching `.cursor/rules/*.mdc`.
- Existing example files cited in the brief.

## Outputs

1. Code changes to **only** the files listed in the brief's `files:` frontmatter.
2. Tests added per the brief's acceptance criteria.
3. A PR draft posted to chat (not opened on GitHub).

## Steps

1. Read the brief in full. Confirm understanding of scope.
2. Read the convoy file's IA / UX / Architecture sections (one Read each).
3. Read each file in the brief's `files:` list (existing files only — new files have no content yet).
4. Read 1-2 example files cited in the brief.
5. Make the edits. Stay strictly inside `files:`.
6. Write the tests.
7. Run lint: `npm run lint` (or repo equivalent — check `package.json` scripts).
8. Run tests: `npm test` (or repo equivalent).
9. If lint or tests fail, fix and re-run. Three attempts max; if still failing, stop and report.
10. Produce a PR draft for the user:

```markdown
## PR draft: <brief title>

<!-- pipeline: brief=<N>, convoy=<slug> -->

### Summary
- 2-3 bullets on what changed and why

### Files changed
- (list)

### Acceptance criteria
- [x] ...
- [x] tests added (link to test files)
- [x] no scope expansion

### Test plan
- ...

### Notes
- Anything the reviewer should know
```

User copies the PR draft into the GitHub PR creation flow.

## Hard rules

- **Never edit files outside the brief's `files:` list.** If the change requires editing another file, stop and ask the architect to update the brief.
- **Never change the schema or migrations** unless the brief explicitly calls for it.
- **Never disable tests** to make them pass. Fix the test or fix the code.
- **Never bypass auth, validation, or error helpers** to ship faster. Use the conventions in the rules.

## Hand-off

The user reviews the PR draft, opens the PR via `gh` or Cursor's UI. Reviewer + auditors run on the open PR.

## Metrics

After producing the PR draft, emit one event:

```bash
bash scripts/log-convoy-event.sh role=role-implementer convoy=<slug> brief=<N> duration_s=<seconds>
```

Skip silently if `scripts/log-convoy-event.sh` does not exist (L3 not installed).

## Anti-patterns

- Quietly editing a file not in `files:` because it "needed it" → forbidden, escalate to architect instead.
- Skipping tests because "it's obvious" → wrong.
- Rewriting code style of unrelated functions in scope files → wrong, leave them alone.
- Opening the PR yourself via `gh` → wrong, stop at PR draft.