issue-creator

# Vague user request → actionable GitHub issue Preserve the user's voice, identify the underlying problem, add only grounded repository context, and create the smallest honest issue that moves the work forward. Never turn missing information into confident requirements. ## Workflow ### 1. Normalize the raw input Handle all three input modes: - **Pasted text:** preserve the most useful original sentence verbatim. - **Screenshot:** inspect both visible text and UI context. Transcribe only what is legible and mark uncertainty. Keep the original image for `Evidence`. - **Mixed:** treat the pasted explanation as context and the screenshot as primary evidence unless they conflict; surface any conflict. Build a private scratch intake before drafting: | Field | Extract | |---|---| | Actor | Who experiences this? | | Situation | When and where does it happen? | | Friction | What is hard, broken, or missing now? | | Desired outcome | What should the user be able to achieve? | | Impact | Why does it matter? | | Explicit constraints | What did the user actually require? | | Unknowns | What remains unclear? | Do not force the request into “As a user, I want…” language. Preserve a direct quote when it expresses the pain better than a summary. If the message is phrased as a question, identify the latent need but first check whether existing behavior or documentation already answers it. Do not file a feature request for something the product already supports. ### 2. Resolve rep...