requirements-flowchart

requirements-flowchart is a skill for Claude Code, Codex from ChenyCHENYU/wl-skills-design. It costs 67 tokens per session (530 once invoked), scanned A, original, Apache-2.0.

A tool for creating and checking draw.io business swimlane flowcharts. Swimlanes separate the people or teams involved, while the chart shows activities, decisions, and how work moves between them.

In plain words
What is it for?
Use it to create, review, validate, or repair draw.io process diagrams for business workflows. It is not intended for code execution flows, CI workflows, or algorithm diagrams.
Why use it?
It makes responsibilities and business steps easier to follow and checks that the diagram's links, identifiers, and references are valid. It also connects activities back to the requirements document.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create, review, validate, or repair draw.io process diagrams for business workflows. It is not intended for code execution flows, CI workflows, or algorithm diagrams.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chenychenyu/wl-skills-design/requirements-flowchart
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ChenyCHENYU/wl-skills-design --skill requirements-flowchart
Clone the repo
git clone --depth 1 https://github.com/ChenyCHENYU/wl-skills-design

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for requirements-flowchart

README.md
[![agentmods](https://agentmods.dev/badge/skills/chenychenyu/wl-skills-design/requirements-flowchart/github.svg)](https://agentmods.dev/skills/chenychenyu/wl-skills-design/requirements-flowchart)
Your own site
<a href="https://agentmods.dev/skills/chenychenyu/wl-skills-design/requirements-flowchart"><img src="https://agentmods.dev/badge/skills/chenychenyu/wl-skills-design/requirements-flowchart/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for requirements-flowchart

Your own site · 80×15
<a href="https://agentmods.dev/skills/chenychenyu/wl-skills-design/requirements-flowchart"><img src="https://agentmods.dev/badge/skills/chenychenyu/wl-skills-design/requirements-flowchart.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 530 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.00530
Opus 5 $0.00034 $0.00265
Sonnet 5 $0.00013 $0.00106
Haiku 4.5 $0.00007 $0.00053

Measured 10d ago against content hash b2632f5403d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

requirements-flowchart scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

files/.github/skills/requirements-flowchart/SKILL.md · 32 lines

What it actually says

业务流程图

先确定模式

  • create:生成流程图,并仅对本轮新产物执行修复闭环。
  • validate:只读检查现有文件,未经明确授权不得修改。
  • review:与 validate 相同,只读给出评审结论,不默认保存报告。
  • repair:用户明确要求后,先给出问题和差异,再修改并复验。

至少确认流程名称或目标。角色、范围、起止条件和节点可从上下文推断;无法推断时只追问最关键的一项。

执行流程

  1. 读取唯一规则源:流程图标准
  2. 新建文件时读取 draw.io 骨架;需要版式参考时读取 匿名样例说明
  3. 使用标准活动编码 [流程编码]-[操作类型]-[NN],例如 ORD-A-01-E-01
  4. 生成可被 draw.io 打开的 XML,不得只输出 Mermaid、ASCII 或图片。
  5. 执行标准第十五章 20 项验证:先运行 wl-skills-design verify flowchart --file {产物路径} 获取 [M] 项机械结论(CLI 不可用时由 Agent 代执行),再判 [J] 项;缺少 spec 时将 FC-01~FC-05 标为 Pending,不得伪造通过。
  6. 检查 XML 可解析、ID 唯一、引用存在、连接线落在节点上,并尽可能完成渲染检查。

交付约束

  • 默认写入 docs/flowchart/{流程编码}-{流程名称}.drawio
  • 报告逐项给出规则 ID、结果、证据位置和建议。
  • 创建模式可修复本轮生成文件;验证模式只报告,除非用户明确要求修复。
  • 最终说明 Skill、标准、产物路径、20 项结果和 Pending 项。
Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 32 lines · 67 tokens per session scan A b2632f5403d9

Subscribe to this mod's changes

requirements-flowchart is a skill published in the GitHub repository ChenyCHENYU/wl-skills-design (5 stars, last pushed 26d ago), licensed Apache-2.0. It adds 67 tokens to every session and 530 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens