fix(to-tickets): remove stray </content> tag from skill and docs

The final line of to-tickets/SKILL.md carried a stray `</content>`
closing tag with no matching opening tag — a packaging/serialization
artifact from the planning-skills refactor (386d4ff), not valid skill
content. The same stray tag had leaked into the generated landing
docs for to-tickets and to-spec. Strip it from all three.

Fixes #495

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock
2026-07-10 09:45:20 +01:00
co-authored by Claude Opus 4.8
parent e4722b8e65
commit 19c50d50fd
3 changed files with 0 additions and 3 deletions
-1
View File
@@ -105,4 +105,3 @@ The end-to-end behaviour this ticket makes work, from the user's perspective —
In either form, avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
Work the frontier one ticket at a time with `/implement`, clearing context between tickets.
</content>