autosprint: Skill for Claude Code

Build <target_repo>/autosprint/waypoint.md from a GitHub issue. A waypoint is a user-set intermediate target the autosprint loop aims at exclusively until reached; importing one from a tracked issue bridges "we use GitHub issues as backlog" and "we use autosprint to grind toward goals" without manual transcription.

What this skill is NOT

It does not replace the planner. The waypoint defines what state to reach; the autosprint Plan phase decomposes the gap into sprintable tasks. This skill only writes the waypoint — pointing the loop at the issue. Decomposition happens when the user runs autosprint plan or autosprint run.

It does not modify the GitHub issue (no labels, no comments, no close). The issue and the waypoint are linked by reference (the waypoint carries a Tracks: line) but stay independent. The user closes the issue manually after reviewing what the loop produced.

It is single-issue, single-waypoint. A waypoint is by design a focused sub-goal; if the user wants to address multiple issues, they run the skill once per issue (in sequence, after each waypoint reaches and gets reviewed).

Before starting

1. Verify prerequisites.

   • Run gh auth status. If not authenticated, stop and tell the user to run gh auth login first.
   • Confirm we are inside an autosprint-initialised repo: check that <target_repo>/autosprint/config.toml exists. If not, stop and recommend autosprint init first.
   • Check whether autosprint/waypoint.md already exists. If yes, ask: replace it, abort, or rename existing to waypoint.md.paused before writing the new one? Default to abort on EOF.

2. Confirm the repo context. Run gh repo view --json nameWithOwner,url to confirm which GitHub repo gh resolves to from the current directory. If the user expected a different repo, stop and let them cd first or pass --repo owner/name to gh calls below.

Pick the issue

Two flows, depending on how the skill is invoked:

• Direct (/grill-waypoint-from-issue 42 or with a URL like …/issues/42): parse the number, skip to "Fetch the issue".
• No argument: list open issues so the user can pick:

  gh issue list --state open --limit 20 --json number,title,labels --template '{{range .}}#{{.number}} — {{.title}} {{range .labels}}[{{.name}}] {{end}}\n{{end}}'
  

  Display the list, ask the user for the number. Accept just the integer or #42. Refuse closed issues with a soft warning — closed issues usually mean done, and importing them into a waypoint is rarely what the user wants. If the user insists, proceed.