diff --git a/.github/ISSUE_TEMPLATE/milestone-close-out.yml b/.github/ISSUE_TEMPLATE/milestone-close-out.yml new file mode 100644 index 0000000..0d66b12 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/milestone-close-out.yml @@ -0,0 +1,62 @@ +name: Milestone Close-out +description: End-of-milestone chore. Verify the exit criteria, record what shipped, write a retro, and open the next milestone's chores. +title: "[close-out] : Close-out" +labels: [] +body: + - type: markdown + attributes: + value: | + End-of-milestone chore. This is the last open issue in the milestone, and closing it closes the milestone. See `docs/milestone-chores.md`. + Put this issue in the milestone it closes. After opening it, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + A label counts only when a collaborator with triage access or higher applied it. + Releases run on their own train, which cuts a version whenever master is green and something user-visible has landed, so Close-out doesn't cut one. Never force-push. + - type: input + id: milestone + attributes: + label: Milestone + description: The title of the milestone being closed. + placeholder: M6 — teach mode + validations: + required: true + - type: dropdown + id: agent + attributes: + label: Assigned agent + description: This must match the `assigned:` label you apply after opening the issue. + options: + - nyx + - muse + - duet + validations: + required: true + - type: checkboxes + id: checklist + attributes: + label: Checklist + options: + - label: Verify that every exit criterion is met, or record an explicit waiver. + - label: "List the versions the release train shipped during this milestone. If user-visible work landed and no version was cut, raise it in #kharon (or in #needs-lothrop if it needs Lothrop's call), and don't cut one here." + - label: Move every unfinished issue on purpose, either into the next milestone or back to `next`. + - label: Write a short retro covering what to keep, drop, or change for the next milestone. + - label: Create the next milestone with a title only (its Groom sets the goal, exit criteria, and due date). Then open its three chore issues (Groom, Scope check, and Close-out) from the issue forms and put them in it. + - label: Assign those chores with `assigned:` labels following the rotation (nyx → muse → duet → nyx). Each chore goes to a different agent, and no chore type repeats this milestone's agent. + - label: Close this issue and then the milestone. + - type: textarea + id: releases + attributes: + label: Versions shipped + description: Tags or release URLs the train cut during this milestone. Write "none" if it cut none. + validations: + required: true + - type: textarea + id: retro + attributes: + label: Retro + description: A short note on what to keep, drop, or change. Name the agents chosen for the next milestone's three chores. + validations: + required: true + - type: textarea + id: notes + attributes: + label: Notes + description: Waivers, issues that were moved and where they went, and links to the next milestone and its chore issues. diff --git a/.github/ISSUE_TEMPLATE/milestone-groom.yml b/.github/ISSUE_TEMPLATE/milestone-groom.yml new file mode 100644 index 0000000..fcdd858 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/milestone-groom.yml @@ -0,0 +1,52 @@ +name: Milestone Groom +description: Start-of-milestone chore. Set the milestone's goal, exit criteria, and due date, and groom its issues. +title: "[groom] : Groom" +labels: [] +body: + - type: markdown + attributes: + value: | + Start-of-milestone chore. A milestone is a unit of scope with a goal, exit criteria, and a due date. Releases run on their own train. See `docs/milestone-chores.md`. + Put this issue in the milestone it grooms. After opening it, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + A label counts only when a collaborator with triage access or higher applied it. + - type: input + id: milestone + attributes: + label: Milestone + description: The title of the milestone this chore belongs to. + placeholder: M6 — teach mode + validations: + required: true + - type: dropdown + id: agent + attributes: + label: Assigned agent + description: This must match the `assigned:` label you apply after opening the issue. + options: + - nyx + - muse + - duet + validations: + required: true + - type: checkboxes + id: checklist + attributes: + label: Checklist + options: + - label: Fill in the milestone (the prior Close-out created it with a title only). Put its goal and exit criteria in the description and set a due date. + - label: Pull issues from `next` (and from the prior milestone's leftovers) into this milestone, or write new ones, covering this scope and only this scope. + - label: Size each issue, apply type and priority labels, and put the issues in delivery order. + - label: Make sure this milestone's Scope check and Close-out issues exist and are in it. + - label: Confirm the `assigned:` label matches the dropdown. Don't use the label as a substitute for GitHub assignees. + - type: textarea + id: scope + attributes: + label: Goal and exit criteria + description: The milestone's goal and the conditions under which it is done. Copy them into the milestone description. + validations: + required: true + - type: textarea + id: notes + attributes: + label: Notes + description: Sizing questions, deferred items, and links to the board or project. diff --git a/.github/ISSUE_TEMPLATE/milestone-scope-check.yml b/.github/ISSUE_TEMPLATE/milestone-scope-check.yml new file mode 100644 index 0000000..d8da91e --- /dev/null +++ b/.github/ISSUE_TEMPLATE/milestone-scope-check.yml @@ -0,0 +1,53 @@ +name: Milestone Scope Check +description: Midpoint chore. Compare the open work to the exit criteria, and cut or defer anything that has drifted. +title: "[scope] : Scope check" +labels: [] +body: + - type: markdown + attributes: + value: | + Midpoint chore, done around halfway to the milestone's due date. See `docs/milestone-chores.md`. + Put this issue in the milestone it checks. After opening it, apply one assignment label: `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + A label counts only when a collaborator with triage access or higher applied it. + Ping Lothrop in #needs-lothrop only when a decision is required: a scope change, a slip, or something this chore can't cut or defer on its own. + - type: input + id: milestone + attributes: + label: Milestone + description: The title of the milestone this chore belongs to. + placeholder: M6 — teach mode + validations: + required: true + - type: dropdown + id: agent + attributes: + label: Assigned agent + description: This must match the `assigned:` label you apply after opening the issue. + options: + - nyx + - muse + - duet + validations: + required: true + - type: checkboxes + id: checklist + attributes: + label: Checklist + options: + - label: Check the milestone's open issues against its exit criteria. + - label: Identify drift, meaning work that's out of scope, unneeded, or unbounded. + - label: Cut or defer the drift by closing it or moving it back to `next`. + - label: "Flag Lothrop in #needs-lothrop only if a decision is needed. Otherwise finish the chore without a ping." + - label: Record the midpoint status (on track, at risk, or slipping) and what changed, and adjust the due date only with a stated reason. + - type: textarea + id: status + attributes: + label: Midpoint status + description: "On track, at risk, or slipping. What still maps to the exit criteria, what was cut or deferred, and any decision needed." + validations: + required: true + - type: textarea + id: notes + attributes: + label: Notes + description: Links to issues that were deferred or closed, and any decision request for Lothrop. diff --git a/docs/milestone-chores.md b/docs/milestone-chores.md new file mode 100644 index 0000000..c919427 --- /dev/null +++ b/docs/milestone-chores.md @@ -0,0 +1,27 @@ +# Milestone chores + +Lead duties (writing issues, grooming the backlog, checking scope creep) are tasks inside each milestone, not a standing role. Every milestone carries three chore issues, and each one is routed with an `assigned:` label. The chores rotate across Nyx, Muse, and Claude Duet. + +## Milestones and release trains + +These are two separate things, and they run independently. + +- **A milestone is a unit of scope.** It has a goal, exit criteria in its description, and a due date (for example `M6 — teach mode`). The prior milestone's Close-out creates it with a title only, its Groom chore fills in the goal, exit criteria, and due date, and it closes when its own Close-out chore closes. The due date gives the Scope check a real midpoint, and the milestone's progress bar counts the chores along with the work. +- **The release train is the shipping schedule.** A version (`v0.7.0`, `v0.8.0`, …) is cut whenever master is green and something user-visible has landed. That can happen zero, one, or several times during a milestone. Each version is recorded as a tag and a GitHub release whose notes list the issues it shipped. Versions no longer get their own milestones, because GitHub puts an issue in only one milestone and that slot now belongs to scope. The closed milestones `v0.2.0` through `v0.6.0` stay as history. +- **[`next`](https://github.com/CycleFive/kharon/milestone/12) is the unscheduled backlog.** Work that isn't in the current milestone waits there. Groom pulls issues from `next` into the new milestone, and Close-out sends unfinished work back to `next` or forward into the next milestone on purpose. `next` itself has no chores and never closes. + +Platform goals are still tracked with `platform:` labels and tracking issues. + +## The three chores + +1. **Groom** (start). Set the milestone's goal, exit criteria, and due date (the prior Close-out created it with a title only). Then write, size, label, and order its issues, pulling them from `next`. +2. **Scope check** (around the midpoint, using the due date). Compare the open work to the exit criteria, and cut or defer anything that has drifted. Ping Lothrop in #needs-lothrop only when a decision is needed. +3. **Close-out** (end). Verify the exit criteria or record a waiver, and list the versions the train shipped during the milestone. Move unfinished issues on purpose, write a short retro, create the next milestone (title only) and open its three chores in it, and then close this issue and the milestone. Close-out doesn't cut a release; the train does that whenever its gate passes. + +Use the issue forms in `.github/ISSUE_TEMPLATE/`. Open all three chores into the milestone they belong to, then apply exactly one of `assigned:nyx`, `assigned:muse`, or `assigned:duet`. + +**Rotation.** The ring order is `nyx` → `muse` → `duet` → `nyx`. Each of a milestone's three chores goes to a different agent. Each chore type moves one step around the ring from the prior milestone, so no agent does the same chore twice in a row. Record the agent on the issue (in the dropdown and the label) so the next Close-out can pick the successor. + +**Bootstrapping.** The first milestone has no prior Close-out. Lothrop, or the agent he names, creates it with a title, opens its three chores in it, and assigns them as he directs. The rotation runs from there. + +**Trust.** Assignment labels count only when a collaborator with triage, write, maintain, or admin access on the repo applied them. Anyone can open an issue on a public repo, but they can't add labels. Nothing in this repo reads the labels. Routing happens in the agents' mailroom, which lives outside kharon and checks who applied a label before acting on it.