Author the two missing role atoms — documentation-engineer and mcp-engineer — so every accountability agent has a knowledge/roles/ atom
task-missing-role-atoms-doc-mcp-engineer
Author the two missing role atoms — documentation-engineer and mcp-engineer
While authoring Principal SvelteKit Engineer (closing the identical gap for the new SvelteKit app-surface agent), an audit of .claude/agents/ vs. knowledge/roles/ surfaced that two other agents have executable definitions but no durable accountability atom: documentation-engineer and mcp-engineer. Every other build/operate agent has a knowledge/roles/ atom; these two are the remaining gap.
Why a task, not a fix-in-place
Authoring a role atom is not mechanical hygiene — it requires reading each agent file and framing the role's accountability, decision rights, and seams accurately (the same judgment the Principal Knowledge-Format Architect applied to the existing roster). It also needs the correct function-defining decision id verified per role. That is owner judgment, so it is filed as durable, trackable work rather than guessed at in place. confidence: inferred (agent-surfaced from a directory diff, not human-curated).
Scope notes
- In scope:
documentation-engineer,mcp-engineerrole atoms + theirrelates_toedges + index wiring. - Out of scope:
log-auditor— it is the recorder/auditor agent, intentionally not part of theowner/assigneeaccountability roster; do not author a role atom for it. - Mirror, do not invent: match
knowledge/roles/starlight-engineer.md/ux-engineer.md/ the newsveltekit-engineer.mdfield-for-field; verify every[[id]]resolves before committing.
Board globbed before filing — no open task covered the missing role atoms (no task file references documentation-engineer or mcp-engineer).