What problem does it solve? When work is persisted on a ticket or design document, starting implementation without recovering the original approved design leads to building against guesses. This Skill fetches the referenced artefact, walks parent links to find the governing design, checks the current state of the code, and confirms scope with the user before any implementation begins. ## Core Features & Use Cases - Artefact Fetching: Resolves references like PROJ-123, #42, or a file path to the right system (GitHub, Jira, GitLab, Linear, or a Markdown document) and fetches the full ticket content. - Design Recovery Walk: Follows native parent fields and body-text references up to three hops to locate the design, surfacing ambiguity or unresolvable links to the user instead of guessing. - Scope Confirmation: Reads the current codebase for drift since the design was approved, presents the recovered design with acceptance criteria and out-of-scope siblings, and requires explicit confirmation before handing off to implementation. - Use Case: A user says "pick up PROJ-123". The Skill fetches the Jira issue, walks to its parent epic to recover the design, notes that part of the work is already implemented in the current code, presents the reduced scope, and only after confirmation routes the work to an implementation skill. ## Quick Start Ask the assistant to work on a specific ticket or design document, for example by saying "pick up PROJ-123 and start implementing it".
