workflow-trellis
Represent messy work as durable obligations, workflow building blocks, fragments, AI/automation insertion points, and exception queues. Use this whenever the user wants to analyze interviews, messy notes, customer research, operational workflows, PM workflows, vertical SaaS opportunities, AI insertion points, automation opportunities, "durable obligations", fragmented work, hated execution burden, or where AI should fit into an existing workflow. This skill is primarily a thinking and workflow-mapping tool, not a startup idea generator.
gnurio · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add gnurio/nurijanian-skills --skill workflow-trellis技能说明
name: workflow-trellis description: > Represent messy work as durable obligations, workflow building blocks, fragments, AI/automation insertion points, and exception queues. Use this whenever the user wants to analyze interviews, messy notes, customer research, operational workflows, PM workflows, vertical SaaS opportunities, AI insertion points, automation opportunities, "durable obligations", fragmented work, hated execution burden, or where AI should fit into an existing workflow. This skill is primarily a thinking and workflow-mapping tool, not a startup idea generator.
Workflow Trellis
Use this skill to turn messy workflow evidence into a clear representation of how the work actually functions, what obligation forces it to exist, where the representation is fragmented, and where AI can be inserted safely.
The central thesis: do not start with "AI can automate X." Start by representing the work. Once the obligation, entities, states, deadlines, dependencies, evidence, fragments, and human judgment points are visible, the AI opportunities become obvious and less hand-wavy.
The output should make the workflow visible as an object. Tables are not decoration here; they force the analysis to separate the parts of the work that get blurred in prose. Every deep workflow model must include the required tables, a workflow diagram, an Intuition Gained section, and a Product Implications section.
When Starting
If the user provides interviews, transcripts, notes, support tickets, customer research, or a domain description, treat that material as evidence. Extract workflows from it rather than brainstorming from scratch.
Ask at most three clarifying questions only when the answer materially changes the representation:
- Which workflow or user segment should be modeled first?
- Is the goal product strategy, AI feature design, customer discovery, or startup exploration?
- Should the output favor breadth across many workflows or depth on one workflow?
If the user sounds like they want momentum, skip questions and state assumptions.
Core Lens
Analyze workflows through three gates:
- Durable obligation: The work must exist because law, money, customers, operations, professional standards, auditability, or accountability demand it.
- Fragmented representation: The truth of the work must be split across spreadsheets, emails, PDFs, bank portals, desktop apps, messages, forms, humans, vendors, customers, or legacy systems.
- Hated execution burden: The recurring work must be tedious, anxiety-producing, deadline-bound, error-prone, or socially annoying enough that users already complain about it.
Do not discard weak workflows immediately. Label them:
- Strong workflow candidate: all three gates are present.
- Partial workflow candidate: one gate is weak or unclear.
- Weak candidate: the pain is optional, one-off, or mostly high-judgment with no repeatable representation.
Workflow Model Layers
For every important workflow, map the building blocks through these layers.
Layer 1: Capture the obligation
Ask:
- What must exist because law, money, customers, operations, or accountability demand it?
- Who is accountable if it is late, wrong, missing, or unreconciled?
- What external event forces the work to happen repeatedly?
Look for filings, payments, reconciliations, reports, renewals, certifications, approvals, customer commitments, safety checks, billing events, audits, handoffs, inspections, and status updates.
Output the obligation as a concise statement:
[Actor] must [produce/verify/decide/submit/reconcile/respond] [artifact/outcome] by [deadline/trigger] because [external force/consequence].
Layer 2: Represent the workflow
Ask:
- What entities define the work?
- What states can each entity move through?
- What deadlines, dependencies, permissions, and evidence are required?
- What does "done correctly" mean?
Represent the workflow before proposing AI. This layer is the workbench for intuition.
Use this structure:
- Actors: people or organizations involved.
- Entities: customers, accounts, documents, tasks, risks, decisions, vendors, claims, cases, assets.
- States: draft, waiting, submitted, blocked, approved, rejected, reconciled, expired, escalated.
- Transitions: events or actions that move entities between states.
- Deadlines: explicit dates, SLAs, renewal cycles, meeting dates, billing cutoffs, regulatory windows.
- Permissions: who can view, edit, approve, submit, override, or be accountable.
- Dependencies: inputs, approvals, evidence, data feeds, other teams, external portals.
- Evidence: documents, messages, logs, signatures, receipts, metrics, screenshots, decisions.
- Definition of done: what proves the workflow is complete and acceptable.
Layer 3: Connect the fragments
Ask:
- Where does the truth currently live?
- Which systems do users manually compare, copy from, or reconcile?
- Which humans act as routers between fragmented tools?
Common fragments: spreadsheets, inboxes, PDFs, portals, accounting systems, CRMs, ERPs, bank feeds, desktop software, government sites, customer forms, SMS/WhatsApp, vendors, accountants, field workers, and shared drives.
Create a fragment map. This table is required for every deep workflow model because it shows where the current representation is broken:
| Fragment | Contains | Owner | Update frequency | Failure mode |
|---|---|---|---|---|
Layer 3.5: Identify the action kernel and friction kernel
Before proposing automation, decompose each workflow step into the human action it contains.
Do not jump from "workflow step" to "AI mechanism." First ask:
- What type of action is the human performing?
- Which part of that action creates friction?
- What information, evidence, confidence, language, timing, or authority would let them move forward?
- Which part can be prepared by softw