evoflow-plan-workflow SKILL.md skillA
evoflow-plan-workflow from evovexai/evoflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add evovexai/evoflow/evoflow-plan-workflow@git:20261028.1756e02Pins git:20261028.1756e02 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- evovexai/evoflow
- Path
skills/public/evoflow-plan-workflow/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261028.1756e02, committed Oct 28, 2026
- First version recorded
- Sep 12, 2026
- Size
- 4,800 bytes
- Repository stars
- 611
- License
- a license file GitHub does not identify
Plan 场景协作流程：需求澄清、写 plan 落库、supervisor 派发与验收、交付规范。用户要规划/拆解任务、scenario(activate, plan)、或用 supervisor/write_todos 时使用。.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<plan_workflow> ## 0 流程（按序） 1. 需求澄清（**§1**，plan 前） 2. 摸清智能体能力 → 结构化提交 plan 落库（**§2**；**plan 成功返回即止，禁止再问执行确认**） 3. 监工话术（**§3**） 4. 派发（**§4**）→ 逐步执行（**§5**）→ 交付（**§6**） --- ## 1 需求澄清（plan 前） - **需求澄清**：三项未齐时 **禁止** `plan`。对用户用 `ask_clarification`；**`list_agents` 查智能体列表可直接调**，但深度能力摸底（工具集/skill 详情）需 **`subagent` 委派只读子任务**。 - **`plan` 落库后禁止再问执行确认**：`plan` 成功返回后界面已自动展示计划及「开始执行」按钮，**禁止** `ask_clarification` 问"是否开始执行"——直接结束本轮回复（简要说明已完成规划即可）。等待用户后续输入或界面按钮触发。 - **可写 Plan 时**：子任务已回报——需求边界清、调研结论清、能力对照表可支撑每步 `assigned_agent`。 --- ## 2 写 Plan **调用 `plan` 前三项须均已成立**（均由 **`subagent` 子任务**取证，主智能体只综合回报）：① 用户需求清晰；② 调研方案清晰（只读摸底子任务已有结论）；③ 各步 `assigned_agent` 与能力匹配（能力盘点子任务已输出对照表）。任一未满足则继续 `ask_clarification` 或派发调研/盘点类 `subagent`，**勿调用 `plan`**。`steps[]` 每步须含完整派发字段（与 `create_subtasks` 对齐）；`plan` 落库后子任务一次性同步，**勿再** `create_subtasks`。字段细则见 **plan 工具说明与 schema**。 **任务分析图**：`flowchart_mermaid` 须为对任务对象的**分析结果**（如代码调用链、模块依赖、数据流、关键路径），便于后续 Step 执行时对照；**不要**画「Step1→Step2」的执行流程图。 --- ## 3 监工 **定位**：`主智能体` 在计划阶段只做拆解、选人派活与验收设计，不亲自写文件、跑命令或上网检索。 …
Read the whole file at its exact version.
How to install
mdr add evovexai/evoflow/evoflow-plan-workflow@sha256:00736bb1d773f40aThe line at the top of this page pins the label git:20261028.1756e02, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_m4mk253t7jddjrdx)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 12, 2026 and Oct 28, 2026, about one every 46 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.1756e02 latest | 2026-10-28 | 1756e02 | 4,800 B | A | view · diff |
| git:20260912.6c490fd | 2026-09-12 | 6c490fd | 4,756 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4800 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
evovexai/evoflow · 611 stars · license a license file GitHub does not identify · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_m4mk253t7jddjrdx GET https://markdownregistry.com/api/v1/resolve?ref=evovexai/evoflow/evoflow-plan-workflow GET https://markdownregistry.com/api/v1/blob/00736bb1d773f40adb4aaf9712013a3309fd2398b93bd77a218067b0da16ba05
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.