What problem does it solve? When a human spots a defect in a story that is being built or reviewed, there is no sanctioned way to record it in the Archflow release file without risking inconsistent state, misrouted scope, or invalid YAML. This Skill gives humans the same structured entry point into a story's issues[] array that reviewing agents use, while enforcing routing, severity, and lifecycle rules. ## Core Features & Use Cases - List issues: Show every open, fixed, or deferred issue in the active release, grouped by story and ordered by severity, ending with the blocking-issue count that gates the release. - Record a defect: Append a structured issue (id, summary, severity, location, status) to a story's issues[] array, with routing checks that redirect non-defects to the backlog via /archflow-feature. - Defer minor issues: Move a minor finding to the backlog by writing the backlog stub first, then marking the issue deferred with a pointer, keeping the release file valid. - Use Case: During manual testing you find that saved cards render empty on a 204 response. Run /archflow-issue S7-20 with the finding, answer the severity prompt as blocking, and the defect is recorded against the story so it cannot be marked done until fixed or deferred. ## Quick Start Ask the agent to run /archflow-issue followed by a story id and a quoted description of the defect you found, for example to record a checkout bug against story S7-20.
