switch-work

Sets a per-caller workstream and mode focus using roadmap MCP tools.

1|Updated Aug 15, 2026
One-click install
npx skills add https://github.com/AlrikOlson/think-and-ship --skill switch-work-alrikolson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: switch-work
Source: https://github.com/AlrikOlson/think-and-ship/tree/main/crates/think-and-ship/skills/switch-work
Command: npx skills add https://github.com/AlrikOlson/think-and-ship --skill switch-work-alrikolson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents working across multiple workstreams lose track of which area of a roadmap they are focused on, and parallel agents in different worktrees can overwrite each other's context. This Skill records a durable, per-caller focus of workstream plus mode (shape, build, or listen) so subsequent work happens in the right place. ## Core Features & Use Cases - Per-caller focus state: Stores a {lane, workstream, mode} tuple via the roadmap_focus_set and roadmap_focus_get MCP tools, keyed by a stable lane such as the worktree root path. - Fuzzy workstream resolution: Accepts exact names, case-insensitive matches, or unambiguous fragments, and returns server-side candidate lists when a name is unknown or ambiguous. - Frontier reporting: Always reports ready and blocked chunk counts plus the next chunk id for the selected workstream, including honest empty or fully blocked states. - Use Case: A user says "switch to authentication in build mode"; the agent sets the focus for its lane and reports that Authentication has 3 ready chunks with auth-session-rotation next, without touching any code or chunk status. ## Quick Start Ask the agent to switch to a named workstream in shape, build, or listen mode, or ask which workstream it is currently focused on.

Frequently Asked Questions about switch-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch an AI agent to a specific workstream?▼

Tell the agent to switch to the workstream name and a mode, for example "switch to authentication in build mode". The agent calls roadmap_focus_set with its lane, the workstream, and the mode, then reports the ready and blocked chunk counts.

What modes does workstream focus support?▼

Three modes exist: shape for one planning or research decision, build for one ready roadmap chunk gated on real checks, and listen for one stakeholder signal. No synonyms like implement or plan are accepted; if the mode is missing the agent asks.

Can two agents work in different workstreams at the same time?▼

Yes, focus is stored per-caller using a lane identifier, preferably the absolute worktree root path. Two agents in different worktrees hold independent focus states and never overwrite each other.

What happens if the workstream name is ambiguous or unknown?▼

Nothing changes. The server returns the exact matching candidates, the agent relays them verbatim, and the focus stays unchanged. The agent never retries with a guessed name or invents a new workstream.

Does switching focus start or complete roadmap chunks?▼

No, switching focus is selection only. It never writes code, starts or completes chunks, reorders the plan, or processes signals; actual work is delegated to the separate advance-work skill.