scratchpadlisted

# Scratchpad **Kind** reference · **Used by** every role · **When** writing or reading a handoff file · **Ends with** a file written at an absolute path the next role can find The handoff files roles write to each other during one ticket: plans, work logs, review and QA reports, and the proof artifacts the PR and the ticket carry. The directory is `$TROIKA_SCRATCHPAD` (workspace paths (`#workspace-paths`)); `python3 plugin/resolve.py --ensure` creates it. **Untracked, and never committed.** These files belong to one ticket in one workspace. Every product repo is a sibling of this tree, so they sit outside all of them — but a worktree-relative `git add` can still pull them in, which is why [release-pr](../release-pr/SKILL.md) runs `git status --short` before staging and expects no scratchpad entries and no proofs. **Not configuration.** A host loading this tree reads [`agents/`](../../ROLES.md) and [`skills/`](../README.md) only, and never recurses into the scratchpad. Nothing in it instructs a role; it is the output of one and the input of the next. **Absolute paths only.** Every role runs with its cwd inside a worktree, so the scratchpad is not below it. Resolve the paths once per session and use them verbatim: ```bash eval "$(python3 plugin/resolve.py)" ls "$TROIKA_SCRATCHPAD/plans/<TICKET>.md" ``` A relative path does not error loudly — it writes a file no later role finds, and uploads nothing to the ticket. ## Layout ``` plans/<TICKET>.md the p