design-inventory

To generate a screen inventory from user stories, this skill consumes requirements documentation and automatically infers the complete list of application screens. It outputs a structured screen_list.md file to your design folder, automating manual scoping during Wave A planning.

Yes, you can create Mermaid-compatible screen transition diagrams directly from requirements. The skill processes user stories to map user journeys and navigation flows, outputting a screen_transition.md file containing the Mermaid-compatible transition maps.

A screen inventory is a comprehensive list of all application screens inferred from project requirements. You need it during Wave A design flow to scope navigation planning, map user journeys, and align screen design with parallel architecture and database workstreams.

Yes, screen flow generation depends on parallel Wave A inputs such as architecture-skeleton and database workstreams. The skill aligns its screen inventory and transition diagram outputs with these parallel inputs to ensure structural consistency across the design.

You automate screen flow documentation for Wave A by running this skill against your docs/requirements folder. It automatically generates both screen_list.md and screen_transition.md in the docs/06_screen_design directory, eliminating manual diagramming and scoping effort.

A key limitation is that the transition diagrams rely entirely on the completeness of user stories in the requirements documentation. If the requirements lack detailed navigation paths or user journey steps, the generated Mermaid transition maps will reflect those gaps and require manual refinement.