runbooklisted

# Writing a runbook Fires only after bridging paths have been tried and confirmed not to work. Never the first move. Walk this skill end-to-end whenever the task involves writing instructions for a user to execute UI clicks, key presses, file edits, or any other manual action that automation could not perform. Other surface phrases that should trigger the skill: "you'll need to", "please open", "manually click", "write a runbook", "verification script", "steps for the user", "what should I tell the user to do". The earliest cue is the moment you catch yourself about to write "you'll need to" or "please open" in chat. If you have reached that moment without naming the bridges you tried, stop, try the bridges, then come back. The skill encodes five pieces: required sections (Setup, Steps, What to check, Restore), element-level rules (bold UI elements, expected outcomes, exact strings), fresh-context completeness, the canonical example, and the cues that signal you are violating the rules. Recorded dances (verified multi-step procedures kept beside this skill): - `copilot-review-draft-pr.md`: getting a Copilot code review onto a PR that must stay draft (Copilot skips drafts; the ready window can be seconds). ## Bridges to try before writing a runbook This skill is the fallback. Before reaching it, try at least one of: - `agent-browser` for web UIs; most clicks have a backing HTTP/IPC endpoint or keyboard shortcut. - `nested-wayland-session` for is