agent-product-discovery

Product discovery frames early ideas by generating staged vision and requirements proposals into docs/overview/_proposed/, ensuring canonical files in docs/overview/ remain untouched until an operator promotes them.

The best way to scope features during discovery is to frame the WHAT and WHY of an idea, which produces staged vision and requirements drafts for operator review without modifying canonical documentation.

Staging product requirements works by automatically generating vision and requirements drafts into a proposed directory, leaving canonical docs untouched until the operator explicitly promotes them, preventing unauthorized scope changes.

Yes, you can generate PRD drafts without affecting current documentation because the process stages all vision and requirements proposals in docs/overview/_proposed/, leaving the canonical docs/overview/ directory completely untouched.

You need a product discovery process when teams stall during idea intake due to a lack of clear WHAT and WHY, requiring staged vision and requirements proposals to guide stakeholder framing and scoping conversations.