to-issues: prefer native sub-issues; reference /prototype code explicitly
Two minimal edits to the to-issues skill: - The "What to build" template now points explicitly at the `/prototype` skill's code as the source of an inlined decision snippet, rather than gesturing at "a prototype". - Publishing now prefers the tracker's native sub-issues (parent → slice) and native blocking edges (Blocked by) where supported — mechanics already documented in the issue-tracker doc — keeping the `## Parent` and `## Blocked by` body sections as the fallback. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
66f92b61f5
commit
0172e61e57
2 changed files with 7 additions and 2 deletions
5
.changeset/to-issues-sub-issues-and-prototype.md
Normal file
5
.changeset/to-issues-sub-issues-and-prototype.md
Normal file
|
|
@ -0,0 +1,5 @@
|
|||
---
|
||||
"mattpocock-skills": minor
|
||||
---
|
||||
|
||||
Sharpen how the **`to-issues`** skill records structure. The "What to build" template now adds a context pointer to where the **`/prototype`** skill's code lives, rather than inlining a snippet from it. And publishing now prefers the tracker's **native sub-issues** for parent → slice and **native blocking edges** for `Blocked by` where the tracker supports them (mechanics already live in the issue-tracker doc), keeping the `## Parent` / `## Blocked by` body sections as the fallback.
|
||||
Loading…
Add table
Add a link
Reference in a new issue