refine

To convert unvetted PRD items into user stories, you run a compressed planning interview to clarify intent and edge cases, assess architectural impact, and update the PRD and spec incrementally after confirming each change.

Spec-impact assessment in product planning identifies architectural implications and affected spec sections before making document changes, ensuring the living spec remains consistent when refining PRD items into user stories.

You prepare unvetted proposed work for sprint planning by reading project state and guard-rail references, conducting a compressed interview per item, and moving items from Unvetted/Proposed to vetted locations with clear acceptance criteria.

Yes, you can update AGENTS.md and CLAUDE.md when refining PRD items. The process performs incremental, confirmed document updates to the PRD, spec, and any necessary project coordination documents in the required dependency order.

Yes, refining user stories requires updating the living spec simultaneously. It selectively loads affected spec sections and performs incremental confirmed updates to both PRD and spec to keep related documents consistent.

A key limitation of automated PRD spec updates during sprint preparation is that changes are not applied automatically. The process requires explicit user confirmation for each proposed change before updating the PRD, spec, or project coordination documents.