Skip to content

Day shift skills: ready-for-agent on a Spec means its Tickets are published #290

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JacobStephens2 merged 2 commits into from
Oct 1, 2026
Merged

Day shift skills: ready-for-agent on a Spec means its Tickets are published #290

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3258962
Day shift skills: ready-for-agent on a Spec means its Tickets are pub…
JacobStephens2 Oct 1, 2026
c4cacc5
Address review: the standalone issue is not a Spec, ask before publis…
JacobStephens2 Oct 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion .agents/skills/to-spec/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,10 @@ The issue tracker and triage label vocabulary should have been provided to you.

Check with the user that these seams match their expectations.

3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage.
3. Write the spec using the template below. Before you publish it, ask the user whether tickets will follow. Then publish it to the project issue tracker, labelled by the answer:

- **Tickets will follow** → apply the `needs-triage` triage label, and tell the user that `/to-tickets` will mark the spec ready once its tickets are published.
- **No tickets** → the issue stands alone as one session of work. Apply the `ready-for-agent` triage label - no need for additional triage.

<spec-template>

Expand Down
2 changes: 1 addition & 1 deletion .agents/skills/to-tickets/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Publish the approved tickets. **How** depends on the tracker `/setup-matt-pocock

Work the **frontier**: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.

Do NOT close or modify any parent issue.
Do NOT close or modify any parent issue, with one exception: its triage label. When the tickets come from a spec's issue, swap the spec's `needs-triage` label for `ready-for-agent` as your last step, after every ticket and every blocking link is published. `ready-for-agent` on a spec says its tickets are published. Change nothing else on the spec.

<local-ticket-template>

Expand Down
8 changes: 8 additions & 0 deletions docs/agents/triage-labels.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,3 +13,11 @@ The skills speak in terms of five canonical triage roles. This file maps those r
When a skill mentions a role (e.g. "apply the AFK-ready triage label"), use the corresponding label string from this table.

Edit the right-hand column to match whatever vocabulary you actually use.

## `ready-for-agent` on a Spec

On a **Spec**, `ready-for-agent` says its **Tickets** are published: every Ticket is a sub-issue of the Spec and every blocking link is in place. Until then the Spec is labelled `needs-triage`, because a `ready-for-agent` Spec with no Tickets yet looks exactly like a standalone Ticket, and a **Pickup run** would start a plain Run on it.

## `in-progress` is not a triage role

`in-progress` is thirdshift's own label for a **Claim**, defined in `CONTEXT.md`. thirdshift applies and removes it. It is not a sixth triage role: no skill applies it, and it has no row in the table above.
Loading