advance-work

Executes one bounded, evidenced unit of work in the focused roadmap workstream.

1|Updated Aug 15, 2026
One-click install
npx skills add https://github.com/AlrikOlson/think-and-ship --skill advance-work-alrikolson
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: advance-work
Source: https://github.com/AlrikOlson/think-and-ship/tree/main/crates/think-and-ship/skills/advance-work
Command: npx skills add https://github.com/AlrikOlson/think-and-ship --skill advance-work-alrikolson

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve? AI coding sessions tend to drift: they batch multiple tasks, wander into unrelated workstreams, or declare work done without running real checks. This Skill enforces a strict one-unit-per-invocation discipline, so every piece of work is executed, verified against the project's real gates, recorded, and reviewable as a single auditable receipt. ## Core Features & Use Cases - One bounded unit per run: Selects exactly one eligible unit from the focused workstream β€” a planning decision (shape), a ready roadmap chunk behind real quality gates (build), or one stakeholder signal (listen) β€” then stops. - Evidence-backed receipts: Every invocation ends with a structured receipt naming the unit, the checks run with real exit codes, cross-referenced think/ship/roadmap/signal records, discoveries, and the next candidate. - Honest stopping conditions: Emits explicit receipts for no focus set, no ready work, failed required checks, or decisions that belong to a human β€” never fabricates progress. - Spec Kit integration: Automatically uses .specify/ artifacts (specs, acceptance scenarios, task lists, constitution) as the source of requirements and definition of done when present. - Use Case: A developer says "do the next unit" mid-project; the agent loads the current focus, picks the frontier's next chunk, implements it, runs cargo test and clippy with real exit codes, records the trace, and stops with a reviewable receipt. ## Quick Start Ask the agent to advance the current work by doing the next single unit in the focused workstream and report the receipt.

Frequently Asked Questions about advance-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI agent do one task at a time instead of batching?β–Ό

Invoke advance-work for each unit: it selects exactly one eligible item from the focused workstream, executes and verifies it, then stops with a receipt. To continue, invoke it again β€” batching multiple units in one run is explicitly refused.

How does the agent verify work before marking a roadmap chunk complete?β–Ό

In build mode it runs the project's real gate commands (the same ones CI runs) and records actual exit codes via the ship check tools. A failed, skipped, or unrun required check means the chunk stays in progress and a blocked receipt is emitted.

What happens when there is no ready work in the current workstream?β–Ό

The skill emits a no-ready-work receipt describing the frontier state (for example, ready 0, blocked 4) and stops. It never falls through to another workstream or manufactures work by promoting backlog items.

Does advance-work work with GitHub Spec Kit projects?β–Ό

Yes. When a .specify directory exists, the adapter reads its configuration and uses specs, acceptance scenarios, task lists, and the constitution as requirements and definition of done. It never creates or initializes Spec Kit on its own.

What is the difference between shape, build, and listen modes?β–Ό

Shape completes one planning or research decision without touching implementation source. Build implements one ready roadmap chunk behind real gates. Listen grounds and dispositions one stakeholder signal. The mode comes from the focus set by switch-work.

When should I not use advance-work?β–Ό

Do not use it to switch workstreams (use switch-work), to run every remaining chunk in a batch, for board-style reporting, or for unrelated one-off fixes. It only advances the already-focused workstream by one unit.