pipefy-process-design

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Pipefy Process Design

Pipefy 流程设计

This skill activates when the user wants consulting help to design a process — not when they want you to build one. If the user already knows what they want (gave you phases, fields, a spec, or a clear use case), do not use this skill. Execute directly.

当用户需要咨询帮助来设计流程时，激活此技能——而非用户要求构建流程时。如果用户已经明确需求（提供了阶段、字段、规格或清晰的用例），请勿使用此技能，直接执行即可。

When to use vs when to execute

使用场景 vs 直接执行场景

Signal	Response
"Help me design a process for X"	Use this skill — consulting mode.
"What's the best structure for Y?"	Use this skill — architecture guidance.
"Create a pipe for X"	Skip this skill — execute with `pipes-and-cards` .
User provides phases, fields, or a spec	Skip this skill — the spec IS the plan. Build it.

信号	响应
“帮我设计一个针对X的流程”	使用此技能——咨询模式。
“Y的最佳结构是什么？”	使用此技能——架构指导。
“为X创建一个管道”	跳过此技能——使用 `pipes-and-cards` 执行。
用户提供阶段、字段或规格	跳过此技能——规格即为方案，直接构建。

Prerequisites

前提条件

Understand the user's industry and use case before advising structure.
Always search for existing pipes in the org before recommending a new one (
```
search_pipes
```
).

在建议流程结构前，先了解用户所在行业及用例。
在推荐新管道前，务必先搜索组织内已有的管道（使用
```
search_pipes
```
）。

Discovery phase

探索阶段

Research existing org structure:
MCP:
```
search_pipes name=""
```
(empty search returns all visible pipes) MCP:
```
get_organization organization_id=<id>
```
Understand the process intent:
- What triggers a new case? (form submission, email, manual)
- Who are the actors? (submitter, approver, ops team)
- What are the key decision points? (approve/reject, escalate, auto-close)
- What data needs to be tracked? (fields per phase)
- Are there related processes that should be connected? (use relations)

Identify the right Pipefy components:

Need	Component
Workflow stages	Pipe + Phases
Structured data per stage	Phase fields
Reference/lookup data	Database table
Cross-process linkage	Pipe relation
Automatic actions	Automation rule
AI-driven processing	AI automation or AI agent

调研现有组织架构：
MCP:
```
search_pipes name=""
```
（空搜索返回所有可见管道） MCP:
```
get_organization organization_id=<id>
```
明确流程目标：
- 新案例的触发条件是什么？（表单提交、邮件、手动创建）
- 涉及哪些角色？（提交者、审批者、运营团队）
- 关键决策节点有哪些？（批准/驳回、升级、自动关闭）
- 需要跟踪哪些数据？（各阶段的字段）
- 是否有需要关联的相关流程？（使用关联功能）

选择合适的Pipefy组件：

需求	组件
工作流阶段	Pipe + Phases
各阶段结构化数据	Phase fields
参考/查找数据	Database table
跨流程关联	Pipe relation
自动操作	Automation rule
AI驱动处理	AI automation 或 AI agent

Design principles

设计原则

Start with the outcome. What does "done" look like for this process?
Name phases for states, not actions. "Under Review" not "Review It".
Keep the start form minimal. Only ask for data the requester can provide on day 1.
Use required fields sparingly. Every required field is a blocker.
Design for the exception. Add a "Blocked" or "On Hold" phase for edge cases.
Automate the obvious. If a transition always happens under the same condition, it should be an automation, not a manual step.

从结果出发。该流程的“完成状态”是什么样的？
阶段命名以状态为准，而非动作。例如命名为“审核中”而非“进行审核”。
初始表单尽量简洁。仅要求提交者在第一天就能提供的数据。
谨慎使用必填字段。每个必填字段都是一个潜在障碍。
为异常情况设计。添加“阻塞”或“暂停”阶段以处理边缘案例。
自动化常规操作。如果某个转换始终在相同条件下发生，应设置为自动化，而非手动步骤。

Common patterns

常见模式

Linear approval flow

线性审批流程

Submission → Under Review → Approved / Rejected → Done

Start form: requester fills details.
"Under Review" phase: approver field + due date.
Automation: notify approver on card creation.

提交 → 审核中 → 批准/驳回 → 完成

初始表单：提交者填写详细信息。
“审核中”阶段：包含审批者字段 + 截止日期。
自动化：卡片创建时通知审批者。

Multi-stage pipeline

多阶段流水线

Intake → Triage → In Progress → Testing → Deployed

Each phase has role-specific fields.
Automations advance cards on condition.
SLA fields track time-in-phase.

接收 → 分类 → 进行中 → 测试 → 已部署

每个阶段包含角色专属字段。
满足条件时，自动化推进卡片。
SLA字段跟踪各阶段耗时。

Hub-and-spoke (related processes)

中心辐射式（关联流程）

Central "intake" pipe connected via pipe relation to domain-specific pipes.
Child cards created automatically via automation when parent moves to "Escalated".

中心“接收”管道通过pipe relation连接到特定领域的管道。
父卡片进入“升级”阶段时，自动创建子卡片。

Output format

输出格式

After the design consultation, produce a concise summary:

Process: <Name>
Phases: [list]
Start form fields: [list with types]
Key automations: [list]
Related processes: [list or "none"]
Next step: [execute with pipes-and-cards skill? or more questions?]

完成设计咨询后，生成简洁的总结：

流程：<名称>
阶段：[列表]
初始表单字段：[带类型的列表]
关键自动化：[列表]
相关流程：[列表或“无”]
下一步：[使用pipes-and-cards技能执行？或进一步提问？]

Success criteria

成功标准

User has clarity on phases, fields, and automation triggers before execution starts.
No duplicate pipes created (checked via
```
search_pipes
```
).
The design is buildable with available MCP tools (no features promised that don't exist).

用户在执行开始前，已明确阶段、字段和自动化触发条件。
未创建重复管道（已通过
```
search_pipes
```
检查）。
设计可通过现有MCP工具实现（未承诺不存在的功能）。

另请参阅

```
skills/pipes-and-cards/
```
— execute the design once finalized.
```
skills/automations/
```
— add automation rules to the new pipe.
```
skills/process-intelligence/
```
— analyze an existing process for improvement (distinct from designing new).

```
skills/pipes-and-cards/
```
—— 设计定稿后执行构建。
```
skills/automations/
```
—— 为新管道添加自动化规则。
```
skills/process-intelligence/
```
—— 分析现有流程以优化（与设计新流程不同）。