improve-remote-plan

Improve Remote Plan (Linear)

Improve a Switchboard plan stored as a Linear issue — without touching the git repo or local filesystem. This is the remote-session counterpart to /improve-plan, which operates on local .md files.

When to Use

• You are in a remote session (Claude Code web, claude.ai) with no local machine running.
• A plan exists as a Linear issue in a Switchboard-mapped project.
• You need to deepen the plan and advance its status so the startup reconciler moves the kanban card.

When NOT to Use

• You have a local VS Code session with the Switchboard extension active → use /improve-plan instead (it edits local files directly).
• The plan is in Notion → Notion read/write is not yet supported via the agent API. Use the local /improve-plan workflow instead.

Prerequisites

• The Switchboard extension must be active (LocalApiServer running) — sb_api_call.sh health-checks this automatically.
• Linear integration must be configured in Switchboard (the proxy adds the token host-side).
• Source the API helper before any sb_api_call invocation — sb_api_call is a shell function, not a standalone command. Source it once at the start of the session:

  source "$(git rev-parse --show-toplevel)/.agents/skills/_lib/sb_api_call.sh"
  

Pre-flight

1. Confirm the LocalApiServer is reachable: sb_api_call.sh will fail with a clear error if not.
2. Identify the target Linear issue:
   • If the user provides an issue ID/URL: use it directly.
   • If no issue specified: query for issues in the "Created"/backlog status in the Switchboard-mapped project:

     sb_api_call POST /api/linear -H "Content-Type: application/json" -d '{
       "query": "query { issues(first: 50, filter: { team: { id: { eq: \"<TEAM_ID>\" } } }) { nodes { id identifier title state { id name } } } }"
     }'
     

   • Present the list to the user and let them choose.
3. Identify the target "Improved" status:
   • Query the team's workflow states:

     sb_api_call POST /api/linear -H "Content-Type: application/json" -d '{
       "query": "query { teams(first: 1) { states { id name type } } }"
     }'
     

   • Present the state names to the user and ask which one corresponds to the "Improved" column. Do NOT guess — an incorrect status = wrong column advance or silent no-op.