workflow-discovery

Identify and document user workflows into a structured WorkflowBrief before design work.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bennybennison/agent-toolkit --skill workflow-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-discovery
Source: https://github.com/bennybennison/agent-toolkit/tree/main/skills/workflow-discovery
Command: npx skills add https://github.com/bennybennison/agent-toolkit --skill workflow-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often start building screens or backend systems without a clear understanding of the actual user workflow, leading to wasted effort and mismatched solutions.

Core Features & Use Cases

  • Structured WorkflowBrief: Generates a concise brief that outlines user roles, core jobs, step‑by‑step actions, pain points, decision points, and success criteria.
  • Targeted Questions: Provides a set of focused questions to extract essential workflow details from stakeholders.
  • Use Case: Product managers can quickly capture the end‑to‑end process for a new feature idea, ensuring designers and engineers align on real user needs before any wireframes or APIs are created.

Quick Start

Ask the workflow discovery skill to outline the user's process for a new feature request.

Frequently Asked Questions about workflow-discovery

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

FAQPage Schema
What is user workflow discovery and why do I need it before product planning?

Document user workflows by generating a structured brief that captures user roles, step-by-step actions, blockers, and success criteria. This ensures designers and engineers align on real user processes before creating wireframes or APIs.

How do I document user workflows for a new feature request?

You document user workflows by generating a structured WorkflowBrief that captures user roles, step-by-step actions, blockers, and success criteria. This structured brief aligns designers and engineers on real user needs before creating wireframes or APIs.

Can I use this workflow discovery process without writing any code?

Yes, you can use this workflow discovery process without writing code. It generates a structured WorkflowBrief capturing user roles, steps, and pain points to guide design decisions during feature planning, requiring no code implementation.

What's the best way to capture user pain points and decision points during feature planning?

The best way to capture user pain points and decision points is by generating a structured WorkflowBrief. It uses targeted questions to extract essential workflow details from stakeholders, outlining core jobs and success criteria without requiring implementation.

When should I not use a structured workflow brief for product design?

You should not use a structured workflow brief when a feature requires actual code implementation rather than process clarification. This approach focuses strictly on mapping user jobs and pain points to guide design decisions, not on generating functional code.