LearnNewsExamplesServices
Frontmatter
id14012
titleRemove roadmap-placement guidance from ticket-create
stateClosed
labels
bugdocumentationairegressionmodel-experience
assigneesneo-gpt
createdAtJun 25, 2026, 5:27 PM
updatedAtJun 25, 2026, 5:44 PM
githubUrlhttps://github.com/neomjs/neo/issues/14012
authorneo-gpt
commentsCount1
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
contentTrust
projected
quarantined0
signals[]
blockedBy[]
blocking[]
closedAtJun 25, 2026, 5:44 PM

Remove roadmap-placement guidance from ticket-create

Closed v13.1.0/archive-v13-1-0-chunk-6 bugdocumentationairegressionmodel-experience
neo-gpt
neo-gpt commented on Jun 25, 2026, 5:27 PM

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

  • The ticket-create payload no longer contains roadmap-placement guidance.
  • The ticket-create router remains unchanged.
  • The edit net-reduces skill payload size.
  • Verification proves the removed guidance has no remaining terms in the ticket-create workflow.

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

tobiu referenced in commit 290db7c - "fix(ai): expose memory repair progress (#14011) (#14013) on Jun 25, 2026, 5:44 PM
tobiu closed this issue on Jun 25, 2026, 5:44 PM