story-repo-scoutlisted

# Story Repo Scout Turn a searchable change request into evidence-backed `Repo Context`. This skill owns that artifact; it does not clarify product intent, design the solution, or implement the change. ## Required Input Accept a story card, ticket, issue, acceptance criteria, or rough request when it provides at least one distinctive search anchor, such as an observable behavior, domain term, route, command, UI label, error, config key, data field, or known symbol. A complete story card is useful but not required. When the input names a path, issue, or URL, treat that source as part of the input rather than relying on its title or excerpt. Read the full accessible, authorized body plus material comments and linked decisions. Record its stable identifier and exposed revision, update time, or commit. If access is partial or unavailable, record the exact gap and its planning consequence. If the intended behavior is too ambiguous to establish a search boundary, use `story-clarifier`. If repository access or every available input lacks a searchable anchor, return a truthful non-ready artifact instead of guessing. ## Workflow 1. **Establish scope.** From the required input, identify the repository, likely workspace or component, requested change, search anchors, and provenance or access gap. 2. **Read governing instructions and decisions.** Inspect the applicable root and nested `AGENTS.md` files or equivalent repository policy before drawing boundaries. As candi