v2.15.0 - Craft Picks Up Where the Issue Left Off

What's changed

Craft can now start from a tracker issue and respect how far the issue's newest Go says the work may go. Give it an issue key or link and it reads the issue and its whole discussion, plans from what was decided there, and tells you the stage first. A Go can also let craft answer its own routine questions up to that stage, and a later pickup reads only what changed. An issue with no Go works exactly as before. This release also covers 2.11.1 to 2.14.0, which shipped without release entries.

How to use a Go

A Go is a comment on the tracker issue that says how far the work may go. Craft reads it when you pick the issue up.

• Where it goes: a new top-level comment on the issue. The newest Go, by the tracker's own timestamp, is the one that counts, and older Gos stay as history. The issue's status never grants permission on its own.
• How to write one: with Wright, say "hand it off" or "send it to Claude", or say "build it" or "just plan it" while Wright is already on that issue. Wright drafts the Go and posts it only when you say yes. You can also write one by hand. Its first line must read exactly ## Go - <stage> (<name>, <Month D, YYYY>), for example ## Go - build (Darin, November 1, 2026).
• The four stages:
  • plan: research, alignment and a plan. Nothing is built for merging.
  • build: code on a branch, with tests and review. No pull request.
  • build and open the PR: everything in build, plus a pull request. Merging stays with you.
  • hold: start nothing new until a newer Go.
• Two optional lines craft acts on:
  • Workflow prompts: answer them yourself. lets craft answer its own routine questions up to the stage. It still stops for real product decisions. Without this line, or with Workflow prompts: bring them to me., every question comes to you.
  • Questions and decisions: comments on this issue sends craft's product questions to the issue as comments instead of the terminal.
• Pick it up: in a Craft project, say "pick up DRO-21" or run /craft:cycle-design DRO-21. The first line craft prints is the stage. Picking the same issue up again later reads only what changed and re-checks the newest Go.

A build Go that lets craft answer its own questions:

## Go - build (Darin, November 1, 2026)

Stage: build - code on a branch, with tests and review. No pull request.

Scope: this issue as written

Questions and decisions: comments on this issue

Workflow prompts: answer them yourself.

2.15.0

• Added picking an issue up again. Craft finds the cycle the issue already has instead of starting a second one, reads the issue again, and keeps a dated copy of only what changed. Earlier copies are never touched, and each story points at every copy of the discussion, not only the newest. The first line says whether the stage moved, for example "Stage changed: plan to build, per Go from Darin on Nov 2."
• Added a check of the newest Go at the start of every story. A hold posted while a run is going stops the next story, and a newer build Go lifts a plan stop. If the issue can't be reached, craft says so and goes on the stage it has on record.
• Added questions on the issue. When the Go says questions go there, a real product decision is posted as a comment with named options and a recommendation. Craft keeps going on its recommendation if the decision can wait, and stops if it can't. On the next pickup, craft lists which questions now have answers.

2.14.0

• Added a Go that answers Craft's prompts. When the issue's newest Go says to answer them yourself, craft shows a short brief, then answers its own routine questions up to the stage the Go allows. It stops and asks you only for real product decisions.
• Added stopping at the Go's limit. A Go that allows planning only, or says to hold, still stops before implementation, and a build Go lets it continue.
• Kept an issue with no Go working as before. Craft asks you every question and you decide when to build.

2.13.0

• Added starting a cycle from a tracker issue. Give craft an issue key or link and it reads the issue and its whole discussion, keeps a verbatim copy with the cycle, and plans from what was decided there. The first line it prints tells you how far you may go.
• Added stopping before implementation when the issue's latest Go only allows planning, or says to hold. A build Go lets implementation start, and the issue's status never grants permission on its own.

2.12.1

• Fixed planning flagging a UI story as incomplete for having no binding table. The table is optional, so a story that skipped the visual riff now goes straight to triage instead of a false failure card.
• Added self-update. Craft now checks for its own new version once a day, shortly after a session starts, and installs it in the background, so you stop running the update by hand. The new version loads in your next session. Set CRAFT_AUTO_UPDATE=0 to turn it off.
• Fixed the last stretch of creating a story. The five design sections are now shown to you together once all of them are written, with the one question under them, instead of trickling through the terminal one at a time with the question stuck under the last one.
• Fixed starting a story asking you twice. Once you pick a story to start, from the craft menu, at the end of planning, or by naming it, implementation now begins without a second "Start with Chunk 1?" question.

2.12.0

• Changed the questions that need real thought. Craft now asks them as a card in the conversation: the question, the options with the reasoning for each, and its recommendation. You answer by typing a letter, or "yes" to take the recommendation, instead of squinting at a picker that hides the reasoning.
• Kept the picker for questions with fixed answers, where a click is all it takes.
• Improved how answers are kept: each answer is saved as you give it, so nothing is lost if a session stops partway through a set of questions.
• Fixed batch planning skipping decisions the planner had flagged for you. When planning several stories at once, every call the planner marked as yours to make is now asked, and every call it made on your behalf is listed, whatever its confidence.
• Changed the last stretch of creating a story. After the codebase check, the five design sections (acceptance, scope, what to preserve, the hardest constraint, dependencies) arrive one at a time, each written into the story as it is drafted, and craft asks you once at the end instead of after every section.

2.11.1

• Fixed the end-of-story check for planning notes left in code comments (like "Chunk 3") failing your story over old comments it never wrote. It now looks only at the lines your story added.
• Fixed that same check sometimes passing, or being skipped, without checking anything. It now checks every file your story touched and tells you when it can't read one.

Full Changelog: v2.11.0...v2.15.0