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 careerchain-ys/stdd --skill documenting-requirementsgit clone --depth 1 https://github.com/careerchain-ys/stddWrote 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/careerchain-ys/stdd/documenting-requirements)<a href="https://agentmods.dev/skills/careerchain-ys/stdd/documenting-requirements"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/documenting-requirements/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/careerchain-ys/stdd/documenting-requirements"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/documenting-requirements.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.00129 | $0.05121 |
| Opus 5 | $0.00064 | $0.02560 |
| Sonnet 5 | $0.00026 | $0.01024 |
| Haiku 4.5 | $0.00013 | $0.00512 |
Grade A, and why
documenting-requirements 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
要件定義書（REQUIREMENTS.md）の作成
STDD（Spec and Test Driven Development）方法論に従って、REQUIREMENTS.md（feature / common 両階層）を作成・更新します。 要件（What & Why）を確定したら、技術設計は documenting-tech-specs Skill に引き継ぎます。
Quick Start
新機能の要件定義書を作成する場合
-
REQUIREMENTS.md を作成
docs/<app>/<path>/REQUIREMENTS.md- 業務要件 → 機能要件 → 非機能要件 の3層で記述
- 機能要件は コア（2.1 ユースケース＋2.2 業務ルール）＋ 拡張（2.3 指標定義・2.4 UI/UX・2.5 外部IF、該当機能のみ。無ければ章ごと省略）
- 各ユースケースに 見出し直下の トレーサビリティ ID（
**ID**: UC-<feature>-NN）＋ 振る舞い（番号付き手順・主語明示）＋ 受入基準（EARS）を併記し、Priority を付与（ID は名前と分離し、リネームしても不変に保つ。見出しには ID を含めない） - 指標を持つ機能は §2.3 指標定義表を埋める（算出ロジック・データソース・代理注記）
- テンプレート（feature） を参照
-
ワイヤーフレーム（WF）を生成（UI を持つ機能の場合）
docs/<app>/<path>/wireframes/- REQUIREMENTS.md のユースケースから HTML ワイヤーフレームを生成（低忠実度・主要文言は実値）
- generating-wireframes Skill を参照
- 生成後、REQUIREMENTS.md「2.4 UI/UX・画面」から
./wireframes/index.htmlにリンクする
-
技術設計に進む → documenting-tech-specs Skill（TECH_DESIGN.md / TEST_PLAN.md）
既存機能の要件定義書を更新する場合
- 対応する REQUIREMENTS.md を確認
- 変更内容に応じて更新（ユースケース・受入基準・非機能要件）
- 技術設計・テスト戦略に波及する場合は documenting-tech-specs へ引き継ぐ
Spec の 2 階層構造（common / feature）
要件は feature 階層（機能単位）と common 階層（プロジェクト全体）の2層で扱う。
| 階層 | REQUIREMENTS の位置づけ | 配置例 |
|---|---|---|
| common | サービス全体の業務要件・横断業務ルール・非機能要件・用語のSSoT | docs/common/REQUIREMENTS.md |
| feature | 機能単位の業務要件・機能要件・機能固有の非機能要件 | docs/<app>/<feature>/REQUIREMENTS.md |
- feature の REQUIREMENTS は common 階層（サービス目的・アクター・横断業務ルール・非機能要件）を前提とし、参照する。common と矛盾しないこと。
- 非機能要件・横断業務ルール・用語は common に集約し、feature は「common 準拠」で参照する。
- common テンプレート:
requirements-common.md。既存実装からの common 要件作成はreverse-engineering-common-specスキルを参照。 - 技術設計の common 階層（ARCHITECTURE / TABLE_DEFINITION / API_SPEC / DESIGN）は documenting-tech-specs Skill が扱う。
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.
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.
- 9d ago First seen · 284 lines · 129 tokens per session scan A 39c7c2d3be17
documenting-requirements is a skill published in the GitHub repository careerchain-ys/stdd (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 129 tokens to every session and 5,121 once invoked, about $0.0006 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…