extract-flow-scenario_skill

Overview

This skill extracts a concrete sequence of workflow events from a conversation and emits a ready-to-use, structured markdown numbered list in a fenced code block. It surfaces actors, explicit state changes, triggers, and pain points exactly as described — no abstraction or invented steps. Use it to capture a single observed scenario as raw input for downstream synthesis, design, or spec work.

How this skill works

When given a conversational transcript or scenario description, the skill parses the text for specific, named actors, tools, timestamps, and explicit actions. It builds a terse numbered list with inline tags (Trigger:, Actor:, State Change:, Outcome:) and uses nested indents for sub-steps and conditional branches. The skill refuses to invent missing technical steps; instead it pauses and requests clarification if a logical gap is detected. The final output is a fenced markdown code block containing the precise, documented flow.

When to use it

• You need an exact record of an operational incident or user journey from a conversation.
• Preparing raw inputs for UX, engineering specs, or incident postmortems.
• Converting meeting notes or chat logs into a single, verifiable flow artifact.
• Capturing flows that include exact tool names, IDs, or values for reproducibility.
• Documenting a scenario where you must preserve what was actually said, not a generalized process.

Best practices

• Provide the full conversation context or transcript so the skill can extract exact names, values, and timestamps.
• State explicitly if you want an optional metadata/properties block (Trigger, Actors, Outcome).
• Point out any suspected gaps in the conversation before extraction so the skill can ask for clarification rather than guessing.
• Keep requested scope to one scenario per extraction to preserve specificity and traceability.
• Review the generated flow for missing facts and respond with clarifying details if the skill indicates a pause.

Example use cases

• Convert a Slack incident thread about a failed deployment into a step-by-step flow with actors and state changes.
• Turn a customer support chat into a reproducible user-journey artifact noting pain points and where handoffs occurred.
• Document a demo run where specific feature flags, environment names, or IDs were used.
• Capture a multi-step approval process described in a meeting, preserving who approved and when.
• Extract a troubleshooting conversation to isolate the exact symptom sequence and pending next action.