screen-inventory

Extract screens and UI moments from use cases into an actor-grouped inventory table.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/bflandev/threadline-ai --skill screen-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: screen-inventory
Source: https://github.com/bflandev/threadline-ai/tree/main/skills/screen-inventory
Command: npx skills add https://github.com/bflandev/threadline-ai --skill screen-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Screen inventories extract and classify every user-facing screen and UI moment from a set of use cases to guide design work and ensure traceability without ambiguity.

Core Features & Use Cases

  • Extracts and maps each main success scenario step to a screen or state.
  • Generates a structured inventory table that links screens to use-case steps and actors.
  • Handles preconditions, extensions, and multi-actor views to support comprehensive UI planning.

Quick Start

Provide your set of use cases and run the Screen Inventory skill to generate a structured screen inventory for design handoff.

Frequently Asked Questions about screen-inventory

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

FAQPage Schema
How do I extract UI screens from use cases for design handoff?

To extract UI screens from use cases for design handoff, you provide your use cases to generate a structured, actor-grouped screen inventory. This maps every main success scenario step, precondition, and extension to specific screens and states for designers.

What is a screen inventory in product design and UI architecture?

A screen inventory in UI architecture is a structured table that extracts and classifies every user-facing screen and UI moment from use cases. It links screens to actors and steps to ensure design traceability and guide UI planning without ambiguity.

Can I map multi-actor views and preconditions into a single UI design inventory?

Yes, you can map multi-actor views and preconditions into a single UI design inventory. The process handles steps, extensions, and preconditions across multiple actors to produce a consistent, actor-grouped screen table suitable for comprehensive UI planning.

How do I generate a structured screen table from use case extensions and steps?

You generate a structured screen table from use case extensions and steps by applying rule-based mappings to the text. This extracts every UI moment and outputs a consistent, design-ready inventory linking each extension and step to its corresponding screen.

Does generating a screen inventory work without external dependencies or components?

Yes, generating a screen inventory works without external dependencies or components. You only need to provide your set of use cases as input, and the rule-based mapping will output the structured inventory directly for your design workflow.