check-ticket-implementation

# Check ticket implementation Judge how much of a ticket is already implemented and report it so the user sees at a glance what is done, what isn't, and what still needs attention. ## Gather Input is a ticket URL / bare id — run [fetch-ticket](../fetch-ticket/SKILL.md) on it (it resolves the tracker and planning dir and persists the `.TICKET.md`) — or a path to an already-fetched ticket file or its task dir. Ambiguous input: ask, don't guess. Run the fetch in a **subagent** when the runtime supports one, so its tool traffic stays out of this session's context: it returns the ticket-file path plus any blocker it hit (ambiguous tracker, auth, no planning-dir convention) for you to settle with the user — it never guesses. Without subagent support, invoke fetch-ticket inline. The **ticket text is what gets annotated** — its `.REQUIREMENTS.md` (same dir and `<id>-<slug>` base — a shared dir may hold siblings') may be read as context for intent, never annotated in its place. Inspect downloaded attachments and design frames when they bear on a requirement being judged. **Evidence base**: the current working tree, uncommitted changes included — unless the invocation names something else (a branch, PR, commit range); then judge against that. ## Blocks Turn every requirement-bearing statement into a block: description, acceptance criteria, and comment statements that add or change requirements (attribute those, e.g. "from comment by X"). Drop metadata, related-ticket lists, and...