backlog-scannerlisted

# Backlog Scanner Identify, classify and format backlog candidates from any source material: meeting transcripts, chat history, documents, side conversations, user feedback. The output is a file someone can act on: candidates written as user stories, and everything that did not qualify listed with where it should go instead. Nothing raised in the source is silently dropped. --- ## Trigger Activated when the user: - Says "backlog scan", "scan for backlog", "extract backlog items", "find backlog opportunities" - Provides a transcript or document and asks for backlog extraction - Asks to consolidate backlog items across several sources ## Workflow ### Step 0: establish the context Ask before scanning, in one message, and keep the answers for the rest of the session. Skip any question the user has already answered in their request. 1. **What is this product or programme called?** Used in the output filename and its heading. 2. **Who are the users, by role?** Their real job titles, not "user". An analyst, a site foreman, a claims handler, a teacher: the specific role is what makes a user story arguable. 3. **Is there an existing backlog to check against?** If yes, what are its reference prefixes and where can it be read. 4. **Who decides what enters the backlog?** The candidates file is addressed to that person, and saying so changes how it is written. If the user does not answer, proceed with generic defaults and say so once at the top of the output