← ClaudeAtlas

routemark-setuplisted

Use when `routemark discover` shows no suitable delegate, or the user wants to try something new, a harness Routemark has never met included; and before a delegation, to say what the task needs and what the machine has.
routemark/routemark · ★ 0 · Code & Development · score 72
Install: claude install-skill routemark/routemark
# Setting up a delegate This skill is for the Controller: the powerful model holding the work, with the user beside it. It is not for a delegate. If you are a delegate reading this, stop -- it is not your work. ## What a delegate is, and why A delegate is another harness and model Routemark can hand execution work to -- a coding-agent CLI running under its own login, doing the parts of a task that are execution rather than strategy. Handing that work off frees premium usage for the decisions, review and hard coding that only the Controller should do. The user may have nothing but Claude Code or Codex on this machine yet: that is the normal starting point, not a problem to explain away. ## Start from what the machine already has ``` routemark discover ``` This asks every harness adapter what is on the machine, and separately checks whether what worked here before is still there. Read its output before recommending anything (charter principle 4: the machine is the source of truth). Two cases: - **Something is there and still works.** Use it. There is nothing to set up. - **Nothing suitable is there**, or the user wants to try something new. Move on to the steps below. ## Before a delegation: what the task needs, what the machine has Before every `routemark delegate`, on an open, sandboxed or image project alike, read what this task and this project need and what this machine has, and say it to the user as evidence, in one short block: each thing the task needs, "foun