What problem does it solve? When a ticket is routed to a human developer (hitl) instead of an autonomous agent, the developer still needs a concrete plan: which files to touch, in what order, and how to leverage an AI IDE like Cursor or Copilot Chat. This Skill turns a fully specified ticket or spec into a structured implementation guide with copy-paste-ready prompts, so the human can execute narrow, verifiable steps without re-deriving the plan. ## Core Features & Use Cases - Ticket-to-Guide Conversion: Reads a hitl ticket (GitHub/GitLab issue or local markdown tracker), verifies it is unblocked and fully specified, claims and marks it in-progress, then drafts the guide. - Codebase-Grounded Planning: Explores the actual repository to identify exact files to create or update, respecting ADRs and the project glossary rather than guessing from ticket text. - Ready-to-Paste Prompts: Produces small, compilable steps, each with a self-contained prompt that cites existing files to imitate and requests tests first (TDD). - Use Case: A maintainer picks up a hitl ticket from an epic, runs this Skill, and receives a guide in docs/tasks/ with a file map, per-step IDE prompts, verification commands, and a closing checklist covering code review, commit, qa-gate, and PR. ## Quick Start Ask the agent to run /to-guide on a specific hitl ticket number or local issue file to generate its implementation guide.
