f2s-kb-build

Generates knowledge routing topics, indexes, and matcher shards from finalized stock documents.

48|6|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/double-coding-lab/Flow2Spec --skill f2s-kb-build-double-coding-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: f2s-kb-build
Source: https://github.com/double-coding-lab/Flow2Spec/tree/main/.cursor/skills/f2s-kb-build
Command: npx skills add https://github.com/double-coding-lab/Flow2Spec --skill f2s-kb-build-double-coding-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents repeatedly rediscover project constraints on every request because there is no maintained, routable project memory. This Skill converts finalized documentation into a structured .Knowledge base so agents load only the relevant topics before editing code. ## Core Features & Use Cases - Topic Generation: Splits finalized stock-docs into focused topic files under .Knowledge/topics with summaries, rules, and boundaries. - Routing Manifest Maintenance: Updates manifest-routing.json with topicPaths, taskToTopicRules, topicDependencies, and topicMetadata, plus keyword matcher shards. - Index Synchronization: Keeps .Knowledge/index.md consistent with one row per topic and clickable related-document links. - Orchestration Rules: Enforces main/sub-agent write boundaries so only the main agent writes the manifest and index. - Use Case: After finalizing an architecture document with f2s-doc-final, run this Skill to produce routable topics and matchers so future sessions match requests like "batchReScore sync or async" directly to the right topic. ## Quick Start Run f2s-kb-build with the path to a finalized document in .Knowledge/stock-docs to generate the corresponding topics, index entries, and routing matchers.

Frequently Asked Questions about f2s-kb-build

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate project context topics from documentation?▼

Run f2s-kb-build with a finalized Markdown document located in .Knowledge/stock-docs. The Skill performs semantic analysis, writes topic files under .Knowledge/topics, updates index.md, and registers routing rules and keyword matchers in manifest-routing.json.

What input does f2s-kb-build accept?▼

It accepts a URL or a local path, but local paths must point to finalized documents inside .Knowledge/stock-docs, typically named with the _终稿 suffix. Draft files produced by f2s-doc-arch are rejected; you must run f2s-doc-final first.

Can I run f2s-kb-build on a draft document?▼

No. If the input path contains _初稿 or the document has not been finalized, the Skill stops and instructs you to run f2s-doc-final on the draft first, then re-invoke f2s-kb-build with the finalized path.

How does f2s-kb-build handle large documents?▼

Documents over 300-500 lines or covering more than three unrelated responsibility domains trigger a split recommendation into multiple focused stock-docs. You can still proceed with one large topic, but the summary notes it should be split later.

Which files can sub-agents write during kb build?▼

Sub-agents may only write their contracted topic or matcher files with non-overlapping paths. The manifest-routing.json and .Knowledge/index.md files are always written by the main agent alone, and configuration roots like rules/skills are never touched.