autosprint: Skill for Claude Code

Interview the user to produce a concrete destination.md at <target_repo>/autosprint/destination.md. This file is the sole input to autosprint's planning phase — the single fixed point the PIT loop iterates toward.

The interview walks three passes through the canonical concerns. At each section the user picks one of these outcomes:

• Answer it → user dictates the answer; you write it into destination.md.
• Accept the recommended default (only for sections that ship one) → you write the default content as-is.
• Modify the recommended default (only for sections that ship one) → user dictates changes; you write the modified version. If the modification carries non-trivial reasoning, flag that the change deserves an ADR entry recording the rationale.
• Let autosprint decide → you write a destination-shaped sentence with an *(Open — autosprint to decide.)* marker. Autosprint will resolve in a future sprint, recording rationale in adr.md.
• Skip → you don't add the section to destination.md at all. (Allowed only in passes 2 and 3.)

The resulting file contains only the sections the user picked into. Everything else stays out — no empty placeholders, no aspirational sections nobody intends to fill in.

Where things live

destination.md is the destination — the GPS coordinate the PIT loop descends toward. It lives at <target_repo>/autosprint/destination.md and is the load-bearing input the planner reads on every sprint.

Sibling locations under <target_repo>/autosprint/:

• inputs/ — supporting human-authored material the destination may reference. Half-finished data models, domain glossary, project description, design notes. Read on demand, not on every sprint. destination.md is authoritative; if a file in inputs/ contradicts it, the file in inputs/ is wrong and gets updated. Each file in inputs/ is anchored by humans; agents may append to designated AI-append sections (e.g. ## AI-observed inconsistencies) but never modify human content above them. Pattern: destination.md's "Referenced inputs" section names which inputs/ files matter for which kinds of tasks.
• adr.md — append-only history of technical decisions. Read by Plan and Implement on every sprint as context for what's already locked in. Both humans and the implementor agent author entries here. To change a decision, append a new entry that references the old one under **Supersedes:** — old entries stay in the file as history.
• plan.md — loop state authored by the planner. Not an input to the grill skill.
• logs/, cache/ — agent-generated bookkeeping. Never touch by hand.

Plus the standard agent file:

• <target_repo>/CLAUDE.md — agent navigation context (folder layout, conventions, "we use uv not pip"). Loaded on every agent invocation. Not part of this interview, but updated by autosprint as project shape changes.