extract-flow-scenario

Extract workflow events from conversations into structured markdown lists.

7|Updated Dec 17, 2025

Search Tags:#workflow #markdown #conversation #structured-output #design-data #scenario-documentation #flow-documentation

Ready to run

npx skills add https://github.com/nweii/agent-stuff --skill extract-flow-scenario

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: extract-flow-scenario
Source: https://github.com/nweii/agent-stuff/tree/main/skills/extract-flow-scenario
Command: npx skills add https://github.com/nweii/agent-stuff --skill extract-flow-scenario

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documenting complex operational flows from conversations is labor-intensive and error-prone; this skill outputs a concrete, structured markdown flow capturing actors, state changes, and pain points for downstream synthesis and planning.

Core Features & Use Cases

Generates a numbered, structured markdown block that captures a real conversation workflow with a concise title.
Highlights key elements like Trigger, Actor, Outcome, and State Change, using bold inline tags for easy extraction.
Supports optional metadata and nested steps, with clear guidance on handling conditional branches and pending states to avoid guessing gaps.

Quick Start

Provide a real conversation snippet and ask to document the workflow.

Frequently Asked Questions about extract-flow-scenario

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

FAQPage Schema

How do I document a workflow from a conversation into a structured format?▼

Extracting a workflow from a conversation involves generating a numbered markdown block that captures real operational flows, highlighting triggers, actors, outcomes, and state changes for design planning.

What is the best way to capture real operational flows from chat logs for design planning?▼

Capturing real operational flows from chat logs is best done by extracting events into a deterministic, labeled markdown block that serves as raw data for synthesis or downstream design tools.

Can I use structured markdown to track state changes and pain points in user journeys?▼

Yes, you can use structured markdown to track user journeys by generating a numbered list that highlights key elements like Trigger, Actor, Outcome, and State Change using bold inline tags for easy extraction.

Does this workflow documentation method handle conditional branches and pending states?▼

This workflow documentation method handles conditional branches and pending states by providing clear guidance to avoid guessing gaps, ensuring the structured output remains deterministic and accurately reflects the conversation.

What context do I need to provide to extract a scenario flow from a chat?▼

To extract a scenario flow from a chat, you need to provide a clear conversation snippet so the process can document the exact events, participants, and outcomes into a structured markdown block.

When should I avoid using conversation extraction for scenario documentation?▼

You should avoid using conversation extraction for scenario documentation when the provided chat lacks clear context, as the output requires deterministic data capture and explicitly avoids guessing gaps in the workflow.