From 19c50d50fd1f1fd73cffc4de61a1aabee4cf8728 Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Fri, 10 Jul 2026 09:45:20 +0100 Subject: [PATCH] fix(to-tickets): remove stray tag from skill and docs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The final line of to-tickets/SKILL.md carried a stray `` 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) --- docs/engineering/to-spec.md | 1 - docs/engineering/to-tickets.md | 1 - skills/engineering/to-tickets/SKILL.md | 1 - 3 files changed, 3 deletions(-) diff --git a/docs/engineering/to-spec.md b/docs/engineering/to-spec.md index 8494b7a..2e3c99d 100644 --- a/docs/engineering/to-spec.md +++ b/docs/engineering/to-spec.md @@ -57,4 +57,3 @@ grill-with-docs → to-spec → to-tickets → implement → code-review ``` Reach for it after the plan and domain language are resolved, and before you break the work into implementation tickets. Its key neighbours are [grill-with-docs](https://aihero.dev/skills-grill-with-docs), which sharpens the context so the spec is precise, and [to-tickets](https://aihero.dev/skills-to-tickets), which turns the spec into a set of tickets for [implement](https://aihero.dev/skills-implement) to build. When you're unsure which skill or flow fits, [ask-matt](https://aihero.dev/skills-ask-matt) routes you. - diff --git a/docs/engineering/to-tickets.md b/docs/engineering/to-tickets.md index f061b02..1e4dca7 100644 --- a/docs/engineering/to-tickets.md +++ b/docs/engineering/to-tickets.md @@ -54,4 +54,3 @@ grill-with-docs → to-spec → to-tickets → implement → code-review ``` It sits between [to-spec](https://aihero.dev/skills-to-spec), which hands it a settled spec with user stories to slice against, and [implement](https://aihero.dev/skills-implement), which builds each ticket, driving [tdd](https://aihero.dev/skills-tdd) internally to write the tests test-first, before its [code-review](https://aihero.dev/skills-code-review) pass. Work the frontier one ticket per fresh context, clearing between them. When you're unsure which skill or flow fits, [ask-matt](https://aihero.dev/skills-ask-matt) routes you. - diff --git a/skills/engineering/to-tickets/SKILL.md b/skills/engineering/to-tickets/SKILL.md index 3b91c92..23140c5 100644 --- a/skills/engineering/to-tickets/SKILL.md +++ b/skills/engineering/to-tickets/SKILL.md @@ -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. -