What problem does it solve? Raw ideas, bug reports, and feature asks often enter a development pipeline as vague, untestable tickets that stall developers or bounce back and forth. This Skill enforces a seven-point Definition of Ready so every GitHub issue handed to a Developer Agent is specific, measurable, and scoped before work begins. ## Core Features & Use Cases - DoR-gated issue creation: Drafts issues with title area prefixes, problem/value statement, explicit IN/OUT scope, measurable acceptance criteria, affected containers from architecture_manifest.yaml, proof targets, and flagged assumptions, then applies the flow:ready-dev label via gh. - Autonomous reject re-sharpening: Reads Developer Agent rejection comments on flow:rejected issues, fixes the named gap, increments the reject cycle count, and re-labels, escalating to flow:needs-human after three rejections. - Optional work-list queueing: Appends ready issues to an explicitly named Gateway work list via POST /lists/{name}/items so the queue runner drains them in order, without ever creating lists itself. - Use Case: A user says "make this ready for dev: the cockpit dashboard loses WebSocket connection after idle." The Skill classifies it as a bug, drafts a DoR-compliant issue with testable criteria, self-checks all seven points, creates it with flow:ready-dev, and reports the link. ## Quick Start Ask the product agent to turn your raw feature request or bug report into a dev-ready GitHub issue, for example by saying "product agent: write a work item for adding dark mode to the cockpit dashboard."
