Skip to content

konradcinkusz/ticket-delivery

v2.1.0

The per-ticket delivery procedure as phases you invoke: ticket analysis against an analysis document you refine run by run, the generation of a self-contained master prompt from it, the implementation phase itself, the review of a pull request against the ticket, and a feedback phase that lands a correction in the artifact that owns it. Unlike the other plugins, which are rules you consult, these are procedures you run — expressed in the constitution's terms rather than a generic checklist.

session-status

Use when asked where the work stands mid-session, or when picking a session back up, and the answer has to be numbers that were just measured rather than remembered. Reads the default branch's health first, because a red trunk outranks every open item on it and red, green and not-yet-run are three states rather than two. Separates merged from open-and-green from open-and-red from in-flight from not-started, and names what proves each, because "the agent said it was done" is not a state. Classifies what is left by who can do it — an agent now, a human only, blocked on another repository, blocked on an earlier item here, or a decision the owner must take — since a count that mixes a settings click with a code change is a number nobody can act on. Closes with the instruments that return a plausible answer when nothing happened, from a pending status read off the wrong API to a count written in a document. Reports rather than plans, and says in the report what it could not establish.

Read SKILL.md at the source

Pinned to revision 2396c4cb4d89, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.