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>
526 B
526 B
| 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.