to-tickets: "Do NOT close or modify any parent issue" reads as forbidding the sub-issue link it asks for

### Skill to-tickets ### Harness and version Claude Code 2.1.300 ### Model and effort Fable 5.5, high effort ### What happened Ran `/to-tickets` against a spec published as a GitHub issue. The agent created the six tickets with native `blocked_by` dependencies but did **not** link them as sub-issues of the spec. Asked why, it pointed at two sentences in step 5 of the skill that pull in opposite directions: - *"Use the platform's native blocking / sub-issue relationship where it has one"* - *"Do NOT close or modify any parent issue."* Adding a sub-issue is a `POST` on the **parent's** `sub_issues` endpoint, so the agent classified it as modifying the parent and skipped it. The tickets ended up with correct blocking edges but no parent/child relationship visible from the spec. The generated `docs/agents/issue-tracker.md` for GitHub may have reinforced this: it describes the sub-issue API only under "Wayfinding operations" (the map / child ticket section), so nothing in the `to-tickets` path says sub-issues are for it too. ### What you expected Each ticket linked to the spec as a sub-issue, with the blocking edges on top. "Do NOT close or modify any parent issue" should protect the spec's body and state (don't close, relabel or rewrite it), not forbid the relationship the same step asks for.