f2s-kb-sync

Synchronizes implemented capabilities into the .Knowledge topic base after outline confirmation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents lose track of which capabilities have been implemented, causing project knowledge bases to drift out of sync with the actual codebase. This Skill keeps the .Knowledge/ directory (topics, index, routing manifest, matchers, stock-docs) aligned with verified implemented features through a controlled, confirmation-gated workflow. ## Core Features & Use Cases - Outline-first sync: Always produces a structured update outline (what enters the KB, what is excluded, and why) and waits for explicit user confirmation before writing any files. - Automated merge protocol: Converts confirmed outlines into kb-delta drafts and runs flow2spec kb plan/apply/build/check itself, stopping on revision conflicts for semantic merge instead of blind overwrites. - Stock-doc finalization: Triggers f2s-doc-final to沉淀 finalized stock-docs before topics reference them, and writes a .last-sync.json timestamp consumed by f2s-git-commit. - Use Case: After shipping a new feature, invoke the sync with zero input; the agent infers capabilities from git diff and context, proposes an outline, and on your "y" updates topics, index, and routing manifest automatically. ## Quick Start Ask the agent to run f2s-kb-sync to synchronize the recently implemented capabilities into the knowledge base and confirm the proposed outline.

Frequently Asked Questions about f2s-kb-sync

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

FAQPage Schema
How do I sync implemented features into the Flow2Spec knowledge base?▼

Invoke f2s-kb-sync with an explicit capability list or no input at all. The agent collects evidence, outputs an update outline, and only writes to .Knowledge/topics, index.md, and manifest-routing.json after you reply y.

What happens if I run f2s-kb-sync with no input?▼

The agent infers one or two capability domains from git diff and directory scans, states its inference basis, and still produces an outline for confirmation. Nothing is written to the knowledge base until you approve the outline.

Does f2s-kb-sync modify rules or skills configuration directories?▼

No. The skill only maintains the .Knowledge directory and explicitly forbids changes to the configuration roots rules/ and skills/. Its self-check list verifies no such files were touched.

What happens when a topic revision conflict occurs during sync?▼

The agent runs flow2spec kb plan before writing; if topic revisions mismatch, automatic writing stops and the process switches to a semantic merge explanation. You see a conflict notice rather than a silent overwrite.

Why does f2s-kb-sync write a .last-sync.json file?▼

The timestamp file is read by f2s-git-commit before its default coverage check; if the sync happened within the last 30 minutes, the redundant coverage check is skipped. It is only written when actual knowledge base files changed.