Flow Documentation Wizard

An interactive, conversational skill that guides users through documenting business flows in EventCatalog — step by step, section by section — while cross-referencing their existing catalog resources.

Instructions

Step 1: Locate the User's Catalog

Before anything else, you need to find the user's EventCatalog project so you can cross-reference existing resources.

Ask: "Do you have an EventCatalog project I can look at? If so, where is it?"

• If they provide a path, verify it's an EventCatalog project by checking for eventcatalog.config.js or known directories (services/, events/, domains/, flows/).
• If they have the EventCatalog MCP server connected, use getResources to discover what's in the catalog.
• If they don't have one, that's fine — you'll document steps as plain text descriptions without resource references. Let them know they can still create a useful flow and add resource links later.

Once located, scan the catalog to build an inventory of existing resources:

• Read existing services, events, commands, queries, domains, channels, and flows
• Note their IDs, names, and versions — you'll use these to suggest matches as the user walks through their flow