f2s-stock-docs-vs-req-docs

A project rule for separating existing reference documents from requirement and technical-design documents. It defines which `.Knowledge` folders store each kind of document and how source paths should be recorded.

In plain words
What is it for?
Use it when storing, routing, or referencing project documents under `.Knowledge/stock-docs` and `.Knowledge/req-docs`.
Why use it?
It prevents documents from being placed in the wrong folder or linked to the wrong type of source. That keeps project context and implementation requirements distinct.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/double-coding-lab/flow2spec/f2s-stock-docs-vs-req-docs
Clone the repo
git clone --depth 1 https://github.com/double-coding-lab/Flow2Spec

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 379 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00379
Opus 5 $0.00000 $0.00189
Sonnet 5 $0.00000 $0.00076
Haiku 4.5 $0.00000 $0.00038

Measured 2d ago against content hash bb5ff1307ac1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

f2s-stock-docs-vs-req-docs 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 2d 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.

.cursor/rules/f2s-stock-docs-vs-req-docs.mdc · 17 lines

What it actually says

唯一长文:本文件为 f2s-doc-routing 的完整约定。.Knowledge/topics/f2s-stock-docs-vs-req-docs.md 仅为路由摘要;Codex 读取 .codex/topics/f2s-stock-docs-vs-req-docs.md(由 flow2spec init 从本文件自动镜像)作为等效条令。

stock-docs 与 req-docs

  • .Knowledge/stock-docs/:PDF/初稿/终稿/架构说明等存量源文档f2s-kb-buildf2s-doc-finalf2s-doc-archf2s-kb-add 的文档落盘优先在此。sourceDoc 统一写 .Knowledge/stock-docs/<文件名>.md
  • .Knowledge/req-docs/:需求澄清、技术方案(前后端/数据/任务等)、f2s-doc-pdf 输出的「按方案实现」MD;implement-tech-design 的触发范围为 .Knowledge/req-docs/**/*.md

完整约定见本规则与 skills/f2s-doc-routing/SKILL.md.Knowledge/topics/f2s-stock-docs-vs-req-docs.md 为路由摘要。

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. 2d ago First seen · 17 lines · 0 tokens per session scan A bb5ff1307ac1

Subscribe to this mod's changes

f2s-stock-docs-vs-req-docs is a cursor rule published in the GitHub repository double-coding-lab/Flow2Spec (47 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 379 tokens. 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-30.