Verified:GitHub

screen-inventory

Compile screen inventories mapping BC screens to data and actions.

1|Updated Feb 12, 2026

Search Tags:#workflow-design #screen-inventory #read-path #ui-readpath #inbound-commands #aggregate-designer #context-designer

Ready to run

npx skills add https://github.com/dev-goraebap/grimoire --skill screen-inventory-dev-goraebap

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: screen-inventory
Source: https://github.com/dev-goraebap/grimoire/tree/main/ddd-workshop/skills/screen-inventory
Command: npx skills add https://github.com/dev-goraebap/grimoire --skill screen-inventory-dev-goraebap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure that every BC with a UI contribution has an explicit read-path by documenting the screens it exposes, the data it requires, and the actions it enables.

Core Features & Use Cases

Compile a Screen Inventory that lists each BC's contributed screens, the user-facing routes, required data, and available actions.
Cross-check screen definitions with Exposed Queries from aggregate-designer to ensure traceability and completeness.
Align context between Inbound Commands/Queries and screen-level read paths to reduce missed data requirements during design and implementation.

Quick Start

List the BCs with UI presence and enumerate their screens, then map each screen to its data and actions.

Frequently Asked Questions about screen-inventory

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

FAQPage Schema

How do I map UI read-paths for Bounded Context screens?▼

To map UI read-paths for Bounded Context screens, you compile a Screen Inventory detailing each screen's data needs and actions. This aligns Inbound Commands and Exposed Queries to ensure traceable cross-BC data dependencies.

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

A screen inventory lists each Bounded Context's contributed screens, user-facing routes, required data, and available actions. You need it when ensuring UI-bearing BCs have explicit, navigable read paths mapped to Exposed Queries.

How do I align Inbound Commands with screen-level read paths?▼

You align Inbound Commands with screen-level read paths by documenting cross-BC data dependencies and cross-checking screen definitions with Exposed Queries. This reduces missed data requirements during design and implementation.

Can I cross-check screen definitions with Exposed Queries from aggregate-designer?▼

Yes, you can cross-check screen definitions with Exposed Queries from aggregate-designer. This validation ensures that every UI read-path has traceable data requirements and actions mapped to the correct Bounded Context.

What's the best way to document cross-BC data dependencies for UI screens?▼

The best way to document cross-BC data dependencies is enumerating each BC's screens, then mapping each screen to its required data and actions. This exposes navigable read paths and aligns Inbound Queries across contexts.