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.
npx skills add ChenyCHENYU/wl-skills-design --skill requirements-spec-docgit clone --depth 1 https://github.com/ChenyCHENYU/wl-skills-designWrote 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.
[](https://agentmods.dev/skills/chenychenyu/wl-skills-design/requirements-spec-doc)<a href="https://agentmods.dev/skills/chenychenyu/wl-skills-design/requirements-spec-doc"><img src="https://agentmods.dev/badge/skills/chenychenyu/wl-skills-design/requirements-spec-doc/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.
<a href="https://agentmods.dev/skills/chenychenyu/wl-skills-design/requirements-spec-doc"><img src="https://agentmods.dev/badge/skills/chenychenyu/wl-skills-design/requirements-spec-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00080 | $0.00679 |
| Opus 5 | $0.00040 | $0.00340 |
| Sonnet 5 | $0.00016 | $0.00136 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade A, and why
requirements-spec-doc 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 11d 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.
What it actually says
需求设计说明书
模式与文件边界
create：生成指定章节并验证本轮产物。validate：只读执行 43 项检查。review：与validate相同，只读给出评审结论，不默认保存报告。repair：用户明确授权后修改既有说明书。
只允许写入模板定义的五类文件，不得创建 PLAN007-ipo.md、flow-xxx.md 等任意命名文件。先读取 文档骨架 确认目标位置。
执行流程
- 读取唯一规则源：需求说明书标准。
- 按章节选择资源：
- 仅在需要结构对照时读取
examples/下的匿名合成样例；命令按钮处理逻辑达不到步骤级要素时，对照 IPO 颗粒度样例 补齐。 - 命令按钮的 Process 必须满足标准 §5.1 按钮级覆盖和 §5.2 GB 颗粒度基线；执行类活动与命令按钮一一对应。
- 保持流程编码、活动编码、功能编码、页面、权限岗位和字段集合可追溯。
- 记录
deliveryFormat：Markdown 阶段为markdown-source，装配并渲染后的 Word 为final-word。 - 执行标准第十一章 43 项验证：先运行
wl-skills-design verify spec获取 [M] 项机械结论（CLI 不可用时由 Agent 代执行），再逐项判定 [J] 项，合并为同一编号的报告。markdown-source的 P01–P05 标记 Pending，不得判失败；缺业务事实使用【待补充：说明】并标记 Pending。
交付约束
- 流程部分和 IPO 部分写入同一子模块文件。
- 验证报告给出规则 ID、文件位置和差异集合，不能只写“已检查”。
- 验证模式不修改既有文件；创建模式只修复本轮新内容。
- 最终说明 Skill、章节路径、43 项结果和跨文档差异。
What ships with it
11 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.
- examples/00-doc-outline.md 1.1 KB
- examples/01-flow-desc.md 1.6 KB
- examples/02-function-ipo.md 2.0 KB
- examples/03-flow-screen-map.md 957 B
- examples/04-api.md 1.3 KB
- examples/05-ipo-granularity.md 4.1 KB
- sub/01-overview.md 1.9 KB
- sub/02-module-flow.md 3.5 KB
- sub/03-function-ipo.md 4.2 KB
- sub/04-data-report.md 2.1 KB
- templates/doc-skeleton.md 3.2 KB
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.
- 11d ago First seen · 37 lines · 80 tokens per session scan A 86b74b579468
requirements-spec-doc is a skill published in the GitHub repository ChenyCHENYU/wl-skills-design (5 stars, last pushed 27d ago), licensed Apache-2.0. It adds 80 tokens to every session and 679 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…