archflow-issuelisted

> Arguments are the text after the skill name. # /archflow-issue — Review findings a human found `qa-engineer`, `pm-reviewer` and the `story_review` agents write their findings into a story's `issues[]` themselves. This command is the human's way into the same array — and the only sanctioned way to defer one, which no agent may ever do. ## Usage ``` /archflow-issue → every open issue in the active release, by story /archflow-issue S7-20 → that story's issues, open ones first /archflow-issue S7-20 "cards render empty on a 204" → record a defect against that story /archflow-issue defer S7-20 I-2 → move a minor finding to the backlog and close it ``` ## What an issue is, and is not An issue is **a defect in a story that is currently being built or reviewed.** It is born inside that story's build loop and dies before the story is `done` — fixed, or deferred into the backlog. It has no assignee, no comments, no age, and three states. It is **not** the place for anything else that is wrong with the project. New scope, a bug in shipped code, a refactor you want, an idea — all of those are `/archflow-feature`, which puts them in the backlog where they can be prioritized. A release file that accumulates findings stops being readable, which is the failure mode this command is most likely to cause if it routes carelessly. **Routing is this command's first job, not an aft