[JacobStephens2]

Summary

ready-for-agent on a Spec now says its Tickets are published, in the Day shift's copies of the two skills (.agents/skills/), not the Factory skills.

 /to-spec, step 3
-  publish the spec, label it ready-for-agent
+  ask the user: will tickets follow?
+    yes → publish, label needs-triage, say /to-tickets will mark it ready
+    no  → the issue stands alone as one session of work: label ready-for-agent

 /to-tickets, step 5
   publish every ticket and every blocking link
-  do NOT close or modify any parent issue
+  do NOT close or modify any parent issue, except its triage label:
+    given a spec, swap its needs-triage for ready-for-agent, last

docs/agents/triage-labels.md
├── (table of the five triage roles, unchanged)
├── `ready-for-agent` on a Spec        # its Tickets are published; needs-triage until then
└── `in-progress` is not a triage role  # thirdshift's label for a Claim, defined in CONTEXT.md

Evidence

Prose only, so nothing new to run; #212 says the Day shift skill edits are not tested.

• Before: /to-spec labels every Spec ready-for-agent on publishing, and /to-tickets never touches the Spec, so a Spec with no Tickets yet looks like a standalone Ticket to a Pickup run.
  After: the Spec waits on needs-triage until /to-tickets has published every Ticket and blocking link.
• The Factory skills and the generated prompts are unchanged: git diff --stat origin/issue-212 HEAD -- skills prompts src is empty.
• Full suite: cargo test exits 0, every test binary ok, 0 failed (the prompts_page test, which compares prompts/ with the prompt module, among them).

Unaddressed findings

Standards

• Possible Duplicated Code: the rule lives in CONTEXT.md, the triage label doc and both skills. Partly addressed: the doc no longer restates what each skill does, and the "looks like a standalone Ticket" reason is only in the doc. The one-sentence rule stays in each skill, because a skill is read on its own and has to say what label to apply.
• Possible Divergent Change: the triage label doc now carries Pickup run and Claim meaning beside the label map, and a re-run of the setup skill could overwrite it. Skipped: Day shift skills: ready-for-agent on a Spec means its Tickets are published #286 asks for exactly this in the triage label doc.
• "parent issue" is on Spec's Avoid list. Skipped: it is the upstream skill's own wording, already there, and the skill's parent need not be a Spec.

Spec

• /to-tickets doesn't say what to do with a Spec that carries no needs-triage. Skipped: Day shift skills: ready-for-agent on a Spec means its Tickets are published #286 and Pickup runs: thirdshift takes ready-for-agent issues on its own #212 are silent too, and either answer (always add ready-for-agent, or leave the labels alone) would be a decision this Ticket doesn't make. Worth a follow-up if it comes up.
• The swap is a paragraph in step 5 of /to-tickets, not a numbered step. Skipped: it replaces the parent-issue rule where that rule stood, and says "as your last step" itself.
• /triage can still move a Spec from needs-triage to ready-for-agent before its Tickets exist. Skipped: out of this Ticket's scope; the triage label doc now says what the label means on a Spec, and the Pickup run's settle time is the second line of defence.

Merge Danger

Door: two-way

Three prose files; reverting the commits restores the old instructions. A Spec already labelled under the new rule keeps its label either way.

Blast Radius: small

Only Day shift sessions in this repository that run /to-spec or /to-tickets. A re-install of the upstream skills would overwrite the two skill edits, since skills-lock.json still records the upstream hashes.

Closes #286

🤖 Generated with Claude Code