f2s-kb-add

Aggregates implemented capabilities from multiple source files into knowledge base drafts and routing topics.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a capability is already implemented in code but its knowledge is scattered across multiple files, AI coding agents cannot retrieve it later. This Skill consolidates those dispersed sources into structured draft and final documents inside the .Knowledge/ knowledge base, then synchronizes topics, index, and routing manifests so future sessions can find the facts. ## Core Features & Use Cases - Multi-file aggregation: Parses one or more source files (code, config, docs) into a draft (<方案名>_初稿.md) and a finalized document (<方案名>_终稿.md) under .Knowledge/stock-docs/. - Multi-module detection: When input paths span two or more functional directories, it pauses and asks the user whether to generate per-module documents or a merged one. - Sub-agent orchestration: For large inputs (5+ paths, 3000+ line files, or 10000+ total lines), it can split read-only scanning across parallel sub-agents using B-mode or C-mode strategies while the main agent retains write control. - Routing synchronization: Updates .Knowledge/topics/, .Knowledge/index.md, and manifest-routing.json via the f2s-kb-build conventions after finalization. - Use Case: After shipping a payment feature spread across src/payment/checkout.ts, config, and docs, run this Skill to produce a finalized knowledge document and register its topic so future agent sessions route to it directly. ## Quick Start Ask the agent to run f2s-kb-add on the implemented feature files, for example: add src/auth/login.ts and src/auth/session.ts into the knowledge base as the auth capability.

Frequently Asked Questions about f2s-kb-add

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

FAQPage Schema
How do I add implemented code capabilities to a project knowledge base?▼

Provide one or more source file paths to the f2s-kb-add skill. It parses the files, generates a draft then a final document under .Knowledge/stock-docs/, and synchronizes topics, index, and the routing manifest so agents can retrieve the knowledge later.

What is the difference between f2s-kb-add and f2s-doc-arch?▼

f2s-doc-arch produces architecture drafts for planned designs, while f2s-kb-add handles capabilities already implemented in code, aggregating multiple files into finalized knowledge documents and updating the knowledge routing layer.

What happens when input files span multiple modules?▼

When input paths belong to two or more top-level functional directories, the skill pauses and shows the grouping. You choose between generating separate per-module knowledge documents or merging everything into one combined draft.

When does f2s-kb-add split work across sub-agents?▼

Sub-agent splitting occurs only when subAgent is enabled and thresholds are met: five or more input paths, a single source over roughly 3000 lines, or over 10000 total lines. Sub-agents only read and report; the main agent writes all manifests.

Can f2s-kb-add handle unreadable or invalid file paths?▼

Yes. It continues processing readable files and explicitly lists unreadable paths and gaps in the draft rather than aborting. If no valid paths exist at all, it stops and asks you to supply correct paths.