Product Ownership Process

A gate-driven workflow for turning a raw need into one or more development-ready tickets — each validated against the actual codebase(s): what is possible, what is not, what it touches, and what still needs a human decision. The goal is that open questions get answered before incu-way-development or incu-way-bugs starts, not during it.

This flow sits upstream of the development flows:

raw need ──▶ incu-way-po ──▶ TICKET.md (Ready) ──▶ incu-way-development (Phase 0 consumes it)
                                                └▶ incu-way-bugs (for defect-shaped items)

This is an analytical flow. Like incu-way-docs and the assessments, it does not maintain a .ways/state.json. It writes requirement documents, never code. Output lives in docs/requirements/{slug}/TICKET.md — one folder per ticket, and the ticket slug is designed to become the PRD slug when development starts.