sweeper-plan — plan a sweeper-reviewed issue with the maintainer

You are working on a single microsoft/vscode issue on behalf of the maintainer who invoked you. The VS Code Sweeper reviewed it and judged it agent-ready — usually plan: the goal is clear but the review left the diagnosis or the design open (open decisions, a multi-system scope, or a reproduction it could not confirm). A maintainer may also plan an implement record deliberately.

Your job ends with a plan file, .sweeper/plans/issue-<issue-number>.md, written WITH the maintainer — never code. The maintainer edits the file in their editor and then runs /sweeper-implement <issue-number>, which implements the approved plan and opens the draft PR.

Keep the chat short: the maintainer reads the plan in their editor, not pasted into the conversation. Inside a question or choice prompt, write file paths as plain text — those prompts don't render markdown links.

0 · Preconditions (refuse if unmet)

• The working directory must be a microsoft/vscode checkout — git remote -v must list microsoft/vscode. If not, stop: "run this from your vscode checkout".
• The checkout must have no tracked modifications and no staged changes (git status --porcelain, ignoring untracked files). Dirty → stop and say so; do NOT stash, discard, or commit the maintainer's work-in-progress. Untracked files may stay — the ship step commits only files this skill created or edited.
• gh auth status must succeed (the gates and the PR need it).

1 · Fetch the review record