onboardlisted
Install: claude install-skill real-case/marvin-toolkit
# Onboard
A first session with marvin, in this project. Read the repository, disclose what marvin writes
locally, propose real starter tasks, and run at most two commands that change anything — each
behind an explicit yes.
Work through the seven steps in order, one at a time, and do not summarise the whole walkthrough
up front. Steps 2, 4, 5 and 6 end with a question, and the answer decides what the next step
does: do not batch them and do not run ahead of an answer. Steps 1, 3 and 7 report their result
and move on without asking anything. Step 2 takes two turns when its offer is accepted — the
offer, then the exact lines before they are written — because showing a write before making it is
a consent requirement, not a formality.
## Hard rules
- **Nothing is written without an explicit yes in the same turn.** A hedged, ambiguous or absent
answer is a no.
- **Declining a step continues the walkthrough at the next step.** A no is never a reason to
abort, to apologise, or to ask again.
- **No branches, no pushes.** No step runs `git checkout -b`, `git switch -c`, `git push`, or
`/marvin:track-start` — which creates a branch, and is deliberately absent from this flow.
- **Delegate the two writing commands.** The board card is `/marvin:track-new`; the commit is
`/marvin:commit`. Never substitute a direct `git add` or `git commit` — the commit skill's
sensitive-file screening is why the delegation exists.
- **Read only what a step needs.** Steps 1 and 4 read repositor