What problem does it solve? Hand-editing markdown ticket files in a Spile-based tracker (tracking/) is error-prone: IDs can collide across git worktrees, statuses drift out of sync with the generated view doc, and front matter formatting gets inconsistent. This Skill mechanizes the pure-mechanics slice of ticket tracking so no one burns context hand-writing tickets or the view file. ## Core Features & Use Cases - Ticket Minting: Create a new DH-NNNN ticket with correct front matter, a slugified filename, and an auto-incremented counter — with a guard that refuses to mint from a linked git worktree to prevent ID collisions. - Status Transitions: Move tickets through draft/refining/ready/implementing/verifying/closed, enforce that closing requires a resolution, and set or clear blocked_by and owner fields. - Slug Renaming & View Regeneration: Rename a stale ticket filename slug via git mv, and rebuild tracking/views/dark-harness-view.md (Needs Attention, Board, Recently Closed) from all ticket front matter. - Use Case: When asked to file a bug ticket, run new_ticket.py with title, type, and summary; the script writes the skeleton, bumps the counter, and refreshes the tracker view automatically. ## Quick Start Ask the assistant to create a new draft ticket titled "Fix login timeout" of type bug using the spile-ops scripts, then transition it to ready when the details are filled in.
