cartographer: Skill for Claude Code

cartographer-develop-live — a running instance, the user's feedback, one PR

The other way to land a change. cartographer-propose-plan → cartographer-implement-plan separates the design from the implementation and hands it over in an issue; a live session keeps them together, because the user decides by seeing the result, and always ends in one PR that lands in the release changelog (§The record). The rules of the repository do not change: main is protected, one PR, make gate, docs and decision in the same PR (AGENTS.md, CONTRIBUTING.md §Pull requests).

Choose it when the result can only be judged on the instance. If the change can be written down completely before it is built, write a plan instead.

Role

Before anything else, find your role (D955; CONTRIBUTING.md §Working with an agent client):

gh repo view "$(scripts/upstream-repo.sh)" --json viewerPermission --jq .viewerPermission

ADMIN, MAINTAIN or WRITE is maintainer mode; TRIAGE, READ, or any failure to read it, is contributor mode. State the mode to the user in one line.

In contributor mode the session stops at an open PR (§3 step 5 up to gh pr ready): no gh pr merge, no force-push you were not asked for; the branch is pushed to origin, your fork, and worktrees branch from upstream/main (make worktree-add). In maintainer mode nothing changes.

Roles

• Coordinator — the session talking with the user. It owns the conversation, the worktree, the live instance, every git operation and the decision record. It turns feedback into changes and reads every diff before the user sees it.
• cartographer-live-implementer — a coding subagent on a cheaper model, pinned in its definition (.claude/agents/), spawned with Agent, subagent_type: cartographer-live-implementer, run_in_background: true (act on the completion notification), for the closing pass only (§3). It works in the coordinator's worktree and stops: it never commits, never runs make dev, never touches a file outside its mandate.
• cartographer-contract-reviewer — read-only, on a cheaper model, spawned once at closing (§3) on the draft PR, at most three rounds (cartographer-review-pr §5).
• cartographer-security-reviewer — read-only, spawned in parallel with the contract reviewer when the PR is full tier (cartographer-review-pr §1).
• cartographer-source-reader — read-only, on a cheaper model, spawned when a check of the session's PR is red: it reads the failed log and returns the failed jobs, test names and first error lines, so the log never enters the conversation.
• Explore (or the client's context-gathering subagent) — answers "where is X" for an area the coordinator does not know, so the files are not read into the conversation.