docs(agents): label every spec issue with spec #56

Merged
piscis merged 1 commit from piscis/spec-label into main 2026-10-10 14:52:24 +00:00
Owner

Summary

New spec label for spec issues (Problem Statement, Solution, User Stories, …), as opposed to their tickets. The existing spec, #45, is already labelled.

 docs/agents/issue-tracker.md  ## When a skill says "publish to the issue tracker"
   Create a Forgejo issue with `fj issue create`.
+  A spec … also gets the `spec` label, next to its triage label. Its tickets don't.
 CLAUDE.md
-  Issues live on …
+  Issues and specs live on …
 .forgejo/ISSUE_TEMPLATE/
+└── spec.md   # "Spec" in the web UI's new-issue picker, labels: ["spec"]

Evidence

  • Before: no spec label; the only spec issue, #45, carried just ready-for-agent.
  • After: label spec exists and #45 carries ready-for-agent, spec. Agents publishing a spec (to-spec) reach the rule through CLAUDE.md → docs/agents/issue-tracker.md; a spec opened in the web UI from the "Spec" template gets the label from the template.

Merge Danger

Door: two-way

Blast Radius: none

Docs and an issue template only; the agents scope keeps it out of Release notes.

## Summary New `spec` label for spec issues (Problem Statement, Solution, User Stories, …), as opposed to their tickets. The existing spec, #45, is already labelled. ```diff docs/agents/issue-tracker.md ## When a skill says "publish to the issue tracker" Create a Forgejo issue with `fj issue create`. + A spec … also gets the `spec` label, next to its triage label. Its tickets don't. CLAUDE.md - Issues live on … + Issues and specs live on … .forgejo/ISSUE_TEMPLATE/ +└── spec.md # "Spec" in the web UI's new-issue picker, labels: ["spec"] ``` ## Evidence - **Before:** no `spec` label; the only spec issue, #45, carried just `ready-for-agent`. - **After:** label `spec` exists and #45 carries `ready-for-agent, spec`. Agents publishing a spec (`to-spec`) reach the rule through CLAUDE.md → `docs/agents/issue-tracker.md`; a spec opened in the web UI from the "Spec" template gets the label from the template. ## Merge Danger **Door:** two-way **Blast Radius:** none Docs and an issue template only; the `agents` scope keeps it out of Release notes.
docs(agents): label every spec issue with spec
All checks were successful
ci / build (pull_request) Successful in 54s
540f595444
piscis merged commit bac7ce6f75 into main 2026-10-10 14:52:24 +00:00
piscis deleted branch piscis/spec-label 2026-10-10 14:52:24 +00:00
Sign in to join this conversation.
No description provided.