docs(delivery): GitHub Issues as spec and queue — kind:state labels, issue forms, spec templates - #136
Merged
Conversation
V3RON
added this pull request to stack #139
September 9, 2026 23:31
V3RON
marked this pull request as ready for review
September 10, 2026 01:36
…issue forms, spec templates, DELIVERY.md, handoffs
V3RON
force-pushed
the
delivery/model
branch
from
September 10, 2026 01:40
02970a6 to
347bc0b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Makes GitHub Issues the spec and the queue for agentic delivery. First of three stacked PRs; this one is usable entirely by hand.
docs/internal/agent-rules/delivery.md— the binding rule. Every issue carries exactly one<kind>:<state>label; agents act only onbug:triage,bug:ready,feature:ready,task:ready; the assignee is the claim; the body is the spec and comments are discussion; every spec session reconciles comments posted since the body'slastEditedAt; reporters' issues are never rewritten; feature specs describe outcomes, tasks carry business scope plus technical spec; triage produces a report, not a fix; done is defined per kind; ADR status follows the feature.bug:new) and a feature request (request:new). Both reporter-facing and short. Blank issues stay enabled because feature and task specs are authored from templates, not forms.docs/internal/templates/feature.md,docs/internal/templates/task.md— the bodies a spec session writes. The task template carries the approval checkbox the automation in the third PR reads..github/labels.json+labels.yml— the ten state labels declared in the repo and synced withgh label create --forceon push to main. Create and update only; deletions are manual.docs/internal/DELIVERY.md— the maintainer's manual: the model in five sentences, the three walkthroughs (bug, single-PR feature, split feature), handoffs, what is automated, where ADRs fit.<n>happens on<kind>/<n>, nothing appended;bug/<n>-reprofor reproductions. Issue names branch, branch names issue.## Handoffcomment (Done, Not done, Findings, Blocked on) and unassigns. State, never spec; no progress logs.AGENTS.md,docs/internal/adr/README.md— link the rule; tie ADR status to feature state.After merge (manual, once)
Relabel the open issues and retire the default labels. Proposed mapping, please correct before running:
feature:plannedtask:draftfeature:specbug:newbug:newThen delete
enhancement,bug,duplicate,invalid,question,wontfix,good first issue,help wanted.documentation,dependencies,github_actionsstay because Dependabot uses them.Stack
spec-session,triage-bug,deliverissue-state.ymlautomation