design-inventory

Generate screen inventories and Mermaid transition diagrams from user stories in docs/requirements.

Updated Feb 6, 2026

Search Tags:#automation #design #screen_flow #transition_diagrams #screen_inventory #wave-a

Ready to run

npx skills add https://github.com/sizukutamago/blueprint-plugin --skill design-inventory

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-inventory
Source: https://github.com/sizukutamago/blueprint-plugin/tree/main/skills/design-inventory
Command: npx skills add https://github.com/sizukutamago/blueprint-plugin --skill design-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This design-inventory skill automates the creation of screen inventories and transition diagrams for Wave A, reducing manual scoping and documentation time.

Core Features & Use Cases

Screen inventory generation: lists all screens inferred from user stories and requirements.
Transition diagrams: creates Mermaid-compatible screen transition maps.
Wave A readiness: aligns with architecture-skeleton and database workstreams.

Quick Start

Use the design-inventory skill to generate the initial screen list and transition map from the current user stories in docs/requirements.

Frequently Asked Questions about design-inventory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a screen inventory from user stories?▼

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.

Can I create screen transition diagrams in Mermaid format from requirements?▼

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.

What is a screen inventory and when do I need it in the design flow?▼

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.

Does the screen flow generation depend on architecture or database inputs?▼

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.

How do I automate screen flow documentation for Wave A 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.

What are the limitations of automating transition diagrams from user stories?▼

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.