← Building
Building1 update

supskill

A sprint conductor for Claude Code

Drives one sprint from a markdown backlog to a merged branch: a fresh context boundary at every stage, three human gates, and all authoritative state on disk so the conductor survives its own context death. A pure-Python CLI is the only thing allowed to mutate state and refuses any transition whose preconditions aren't met; the conductor skill runs the gates in the one place a human can actually answer.

  • Python
  • Claude Code
  • pytest
  • subagents
  • state machine
Repository

Building on a moving runtime: I re-ran the finding my sprint conductor is built on

Update 018 min

Update 1 of the supskill build log. supskill is a sprint conductor for Claude Code: it drives one sprint from a markdown backlog to a merged branch, drawing a fresh context boundary at every stage and holding three human gates, with all authoritative state on disk so it survives its own context death. The whole project rests on one finding: a delegated agent cannot ask you anything. Before writing this, I re-ran that finding on Claude Code 2.1.210, and the runtime had moved: AskUserQuestion is now unavailable inside a subagent and absent from a headless session's 62-tool manifest, and calling it returns a loud error instead of the silently-invented empty answer a cited issue reported. That makes supskill's core invariant stronger, not weaker: a delegated agent still has no channel to escalate, so nothing forces it to stop-and-ask rather than guess. This update shows the probe, the turn, and the on-disk state spine (280 offline tests) that makes a skipped gate structurally impossible.