triagelisted

Decide whether planning is needed at all. Half the value of this plugin is here — the other half is spent by people who skipped it. ## 0a. What came with the command **The first line is the invocation — the issue number or URL, and `--label`. Everything after it, in the same message, is prior context.** It goes into `## Prior context` of `issue.md`, and it goes there **verbatim**. That is the whole rule, and it needs no parsing because it is a line boundary. Verbatim rather than summarised, for the reason section 4 reads the `[inferred]` list back: a summary is this plugin's reading of what somebody told it, and a wrong reading does not stay where it was made — it reaches the plan, the tasks and the audit as a record everything downstream trusts. What it is for is the thing that has no other home: work already related to this issue, an approach to repeat or to avoid, a trap the last attempt hit, pull requests worth reading before the code. Typed into a chat message that dies with the session, none of it reaches `/pd:plan` three days later — which is the whole argument for this plugin keeping state on disk at all. A requirement drawn from it is tagged `[operator]` in section 4. Not `[issue]`: that tag means a maintainer can be pointed at the line that says it. Nothing came with the command? Then `## Prior context` says `none given`. Most triages will, and it is an answer — an empty section reads as forgotten. ## 0. No issue number? Then the question is which one Skip