triagelisted

# Triage Analyze requirements for completeness. Explore code + docs, surface gaps, ask clarifying questions, write a report. Tracker-agnostic and storage-agnostic: fetching a ticket and choosing where the report lands are both pluggable (see `references/sources.md`). ## Arguments `$ARGUMENTS` is a space-separated string. Parse optional flags first, then treat the remainder as the input. | Flag | Meaning | | ---------------- | ------------------------------------------------ | | `--ticket <id>` | Ticket / work-item id (label + fetch hint). | | `--name <title>` | Override inferred report title. | | `--out <path>` | Write report to this path; skip the save prompt. | | `--print` | Print report to stdout; skip the save prompt. | Wrappers may pre-pin any of these — user-passed flags WIN. ## Input Detection After flags are stripped, the remainder selects the requirement source: | Form | Source | | ----------------------------- | ------------------------------- | | empty | prompt user to paste / describe | | path ending `.md` | local markdown spec file | | bare id (`12345`, `PROJ-42`) | tracker ticket → see below | | URL pointing at an issue/item | tracker ticket → see below | | anything else | treat as pasted text | Ambiguous → ask. Do NOT guess. ## Workflo