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 agentmods add skills/double-coding-lab/flow2spec/f2s-req-plannpx skills add double-coding-lab/Flow2Spec --skill f2s-req-plangit clone --depth 1 https://github.com/double-coding-lab/Flow2SpecWhat 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 | $0.00064 | $0.02724 |
| Opus 5 | $0.00032 | $0.01362 |
| Sonnet 5 | $0.00013 | $0.00545 |
| Haiku 4.5 | $0.00006 | $0.00272 |
Grade A, and why
f2s-req-plan 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
任务路径：凡
.task/落盘与续作，**必须以rules/f2s-task解析的TASK_ROOT为准（.task或.task/<developerId>；config → git → legacy）。下文若仍出现.task/todo.json/.task/active/，均视为TASK_ROOT/...的简写。
需求任务规划与实现（f2s-req-plan）
从需求/技术方案出发，完整覆盖「规划 → 实现」链路。不依赖 changeTracking.*，但 .task/ 全生命周期必须以 f2s-task 为唯一真值源（目录、格式、续作、打钩、归档、user-todos）。知识库同步由用户后续按需调用 f2s-kb-feat / f2s-kb-sync。
与 f2s-task 的关系（硬约束）
| 项 | 说明 |
|---|---|
| 真值源 | 配置根 rules/f2s-task.*（alwaysApply: true）；Codex 读 .codex/topics/f2s-task.md（init 镜像，与 rules 同源） |
| 本技能职责 | 规划草稿、实现代码、子 agent 编排；不得自定 .task/ 结构或弱化打钩/归档 |
| 与 changeTracking | f2s-req-plan 不受 changeTracking.feat/fix/implement 约束，始终走任务清单；见 f2s-task「生效条件」 |
所有已为项目初始化的客户端都必须读取 f2s-task 全文（步骤 0 必做，先于下文任何步骤）。请从当前客户端生成的 rules、AGENTS.md 或 topics 入口读取，不得用本技能摘要代替全文。
编排（主 / 子 agent）
subAgent/switchAgentVerification以统一入口为唯一事实源：Cursor/Claude →rules/f2s-flow2spec-unified-entry.*；Codex →.codex/topics/f2s-flow2spec-unified-entry.md。- 步骤 1（续作分诊 + 解析）：主 agent 必做
f2s-task「任务开始」1–2；解析文档可拆子 agent（只读）。 - 步骤 2（草稿确认）：必须主 agent；未确认前禁止创建
.task/或写业务代码。 - 步骤 3（落盘）：按
f2s-task「任务开始」3.a–3.f；todo.json仅主 agent；task.md/context.md/user-todos.md初稿可子 agent，user-todos.md执行中追加由主 agent 合并。 - 步骤 4（实现）：子 agent 只写业务代码；禁止子 agent 写
todo.json、改task.mdcheckbox；打钩由主 agent 在合并后当步完成。 - 步骤 5（归档）：主 agent；仅满足
f2s-task「任务完成」归档门禁后执行。 - worktree 卫生见
f2s-flow2spec-unified-entry；中断/结束见f2s-task「中断与会话结束」。
输入（任选其一）
- 技术方案路径（
.Knowledge/req-docs/*.md或 PDF） - 需求 / 变更描述（自由文本）
步骤
步骤 0：前置（强制，任何步骤之前）
Read("flow2spec.config.json")（项目根；缺失字段视为false）。Read当前客户端生成入口中的f2s-task全文（不得跳过；不得仅用本 SKILL 摘要代替）。- 按读到的
subAgent/switchAgentVerification决定下文是否拆子 agent、是否交叉校验。
步骤 1：续作分诊 + 解析输入
1a. 续作分诊（f2s-task「任务开始」1–2，主 agent）
- 若存在
.task/todo.json，Read并将用户本条输入与各条目keywords匹配。 - 命中 1 个 →
Read对应task.md、context.md；若存在则Readuser-todos.md；向用户展示剩余 checklist 与未勾用户代办；询问是否续作该任务。- 用户确认续作 → 加载本 SKILL 全文（
linkedSkill应为f2s-req-plan），从task.md首个[ ]继续；禁止新建重复active/目录；跳至步骤 4（若仍需补充规划，先在「## 备注」记录后再实现）。 - 用户明确要新任务 → 进入 1b。
- 用户确认续作 → 加载本 SKILL 全文（
- 命中多个 → 列出候选，让用户选择续作哪一个或新建。
- 无命中 → 检查孤儿
active/（f2s-task）：若有未归档且含[ ]的task.md，提示是否续作或恢复todo.json；否则进入 1b。 - 无
todo.json→ 进入 1b。
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.
- 2d ago First seen · 151 lines · 64 tokens per session scan A 93f8c7020347
f2s-req-plan is a skill published in the GitHub repository double-coding-lab/Flow2Spec (47 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 2,724 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-30.
Other skills, from other repositories
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
github-labels-query
List GitHub repository labels with perpage pagination and name filtering support.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.