issue-triage

## Project Context - CLAUDE.md: !`find . -maxdepth 1 -name "CLAUDE.md" -type f` - project-discovery.md: !`find . -maxdepth 3 -name "project-discovery.md" -type f` ## Triage Approach - Work only from what the reporter wrote. Do not infer facts that are not stated. This is the single most important constraint in this skill. - Classify the issue type before doing anything else. The type drives what counts as missing information. - Severity and reproducibility are estimates based on what is known. Mark them Unknown when not inferable from the report. - The recommended next step is the single most appropriate han skill (or "clarify with reporter") to run after triage completes. - Project context (CLAUDE.md, project-discovery.md) is read only to identify Suspected Areas. Never use it to supply information the reporter omitted. # Issue Triage ## Step 0: Resolve the Issue Text Determine the issue text from the argument: - If the argument is a path to an existing file, read that file; its contents are the issue text. - Otherwise the argument text itself is the issue text. - If no argument was given and no issue text is present in the conversation, ask the reporter to paste the issue or bug report, then stop until they provide it. ## Step 1: Classify the Issue Determine the issue type from the report text. Choose exactly one: - **Bug** — something is broken or behaving unexpectedly - **Feature Request** — something new is being asked for - **Performance** — the system is too ...