scene-list

To structure ambiguous product requirements, you decompose the project into independent viewpoints and generate a view-by-view table that maps scenes with deterministic numbering. This enforces production-grade scoping by explicitly defining views, stable scene IDs, and priority levels.

Assigning immutable scene IDs involves generating standardized identifiers mapped to specific views and devices during the requirements scoping phase. These stable IDs ensure consistent references across downstream artifacts like PRDs, interaction maps, and test cases without changing after confirmation.

Prioritizing scenes for multi-end product requirements involves marking each decomposed view with P0, P1, or P2 priority levels. This process standardizes device mapping across App, Web, and Backend, guiding delivery sequencing and simplifying planning for ambiguous requirements.

Yes, you can scope new requirements across multiple product ends by generating a scene-list that defines views, scenes, and priorities. It handles ambiguous requirements by producing a standardized markdown table per view, covering App, Web, and Backend environments.

You need to generate a scene-list when decomposing complex product work into clearly defined views and explicit priorities for downstream artifacts. It is required for standardizing requirements referencing in PRDs, architecture diagrams, and behavior specs across multiple product ends.

A limitation of using a scene-list for project scoping is that it relies on immutable scene IDs that should not be changed after confirmation, requiring accurate upfront device mapping. Any later changes to views or priorities will disrupt downstream PRD and behavior spec references.