docs(agents): label every spec issue with spec #56
No reviewers
Labels
No labels
bug
enhancement
needs-info
needs-triage
ready-for-agent
ready-for-human
spec
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
vicoli-oss/docker-forgejo-mcp!56
Loading…
Reference in a new issue
No description provided.
Delete branch "piscis/spec-label"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
New
speclabel for spec issues (Problem Statement, Solution, User Stories, …), as opposed to their tickets. The existing spec, #45, is already labelled.Evidence
speclabel; the only spec issue, #45, carried justready-for-agent.specexists and #45 carriesready-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
agentsscope keeps it out of Release notes.