Context
The ticket-create workflow contained roadmap-placement guidance inside the issue-creation skill. The operator corrected the boundary on 2026-06-25: roadmap placement is planning work, not ticket creation. During #14011 creation, stale placement guidance caused an incorrect extra action that had to be undone.
Live latest-open sweep: checked the latest 20 open issues and the A2A in-flight mailbox before filing; no equivalent correction ticket was found.
The Problem
ticket-create should govern issue substance: duplicate sweep, title hygiene, labels, Fat Ticket shape, lifecycle follow-ups, and authorship discipline. It should not encode roadmap placement policy. Keeping that policy in the skill makes the rule stale whenever roadmap planning changes.
The Architectural Reality
.agents/skills/ticket-create/SKILL.md is the lightweight router and should stay unchanged.
.agents/skills/ticket-create/references/ticket-create-workflow.md owns the issue-creation payload.
- Roadmap placement belongs to the planning/release workflow, not this skill.
The Fix
Remove roadmap-placement guidance from the ticket-create payload instead of replacing it with another planning rule.
Contract Ledger Matrix
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback |
Docs |
Evidence |
ticket-create workflow payload |
.agents/skills/ticket-create/references/ticket-create-workflow.md |
Issue creation no longer governs roadmap placement |
planning workflow decides placement separately |
same payload |
source diff and grep proof |
Decision Record impact
none.
Acceptance Criteria
Out of Scope
- Choosing or documenting any roadmap planning artifact.
- Changing the
create_issue tool schema.
- Editing historical issue/discussion content.
Related
#14011
#13999
Origin Session ID: 9280140f-8b54-4462-9342-49cca7e226f4
Retrieval Hint: ticket-create remove roadmap placement guidance skill payload
Context
The ticket-create workflow contained roadmap-placement guidance inside the issue-creation skill. The operator corrected the boundary on 2026-06-25: roadmap placement is planning work, not ticket creation. During #14011 creation, stale placement guidance caused an incorrect extra action that had to be undone.
Live latest-open sweep: checked the latest 20 open issues and the A2A in-flight mailbox before filing; no equivalent correction ticket was found.
The Problem
ticket-createshould govern issue substance: duplicate sweep, title hygiene, labels, Fat Ticket shape, lifecycle follow-ups, and authorship discipline. It should not encode roadmap placement policy. Keeping that policy in the skill makes the rule stale whenever roadmap planning changes.The Architectural Reality
.agents/skills/ticket-create/SKILL.mdis the lightweight router and should stay unchanged..agents/skills/ticket-create/references/ticket-create-workflow.mdowns the issue-creation payload.The Fix
Remove roadmap-placement guidance from the ticket-create payload instead of replacing it with another planning rule.
Contract Ledger Matrix
ticket-createworkflow payload.agents/skills/ticket-create/references/ticket-create-workflow.mdDecision Record impact
none.
Acceptance Criteria
ticket-createpayload no longer contains roadmap-placement guidance.ticket-createrouter remains unchanged.Out of Scope
create_issuetool schema.Related
#14011 #13999
Origin Session ID: 9280140f-8b54-4462-9342-49cca7e226f4
Retrieval Hint:
ticket-create remove roadmap placement guidance skill payload