generate-screen-inventory

To generate a screen inventory, map success and failure scenarios into concrete UX screens with enumerated states. This process translates scope and research inputs into downstream-ready Markdown artifacts, writing one file per screen with YAML frontmatter and ordered sections.

State modeling for UX screens derives primary and supporting screens from business rules, ensuring each includes at least three meaningful states including an error-adjacent state. You need it when translating scope and research inputs into deterministic, wireframe-ready design artifacts.

Create deterministic screen specs by resolving required input paths against product_base and mapping capabilities into Markdown files with ordered sections. This enforces minimum state counts per screen without padding and records all inferred decisions into a decision-manifest.yaml for review.

Yes, scenario mapping can derive screen inventories automatically by enforcing minimum state counts per screen without padding. It maps success and failure scenarios into structured Markdown files with YAML frontmatter, ensuring downstream wireframing and compilation proceed deterministically.

Deterministic screen generation requires designer-provided contract paths including scope, enriched capabilities, epics, personas, product research, schema, and a screens directory. These inputs are resolved against product_base to produce screen inventory Markdown files plus a decision-manifest.yaml.

Screen inventory generation requires an error-adjacent state to ensure each screen includes at least three meaningful states derived from failure scenarios. This prevents incomplete UX coverage and guarantees downstream wireframing and compilation address both successful and failed user interactions.