f2s-kb-upgrade

Aligns a project's .Knowledge knowledge base with the latest Flow2Spec package template.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When the Flow2Spec package releases a new knowledge base template, existing projects fall out of sync: routing manifests, matcher shards, topic metadata, and index files drift from the package version. This Skill runs the full upgrade workflow so the agent aligns the project's .Knowledge/ directory with the current package template instead of leaving stale routing facts in place. ## Core Features & Use Cases - Version precheck and branching: Runs flow2spec version and flow2spec update --check, then branches on CLI/Core/Template state and verifies project-side alignment before stopping. - Fast path vs full flow: Compares the project's projectRev against the package's pkgRev in manifest-routing.json to skip topic-layer work when nothing changed, or run the full cleanup, metadata audit, and index fusion when it did. - Template fusion and audit: Cleans legacy topic files, audits topicMetadata, backfills topic frontmatter and summaries via flow2spec kb build --fix-topics and kb check --strict, and fuses .Knowledge/index.md with the package template while preserving the project-maintained topic list. - Use Case: After upgrading the Flow2Spec npm package, ask the agent to run f2s-kb-upgrade; it re-runs flow2spec init, detects whether topic-layer changes exist, audits and repairs topic metadata, and writes back the aligned projectRev with a validation summary. ## Quick Start Ask the agent to run f2s-kb-upgrade to align this project's knowledge base with the latest Flow2Spec template.

Frequently Asked Questions about f2s-kb-upgrade

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

FAQPage Schema
How do I upgrade a Flow2Spec knowledge base template?▼

Invoke the f2s-kb-upgrade skill, which runs flow2spec init incrementally, compares the project's projectRev with the package's pkgRev, and then performs cleanup, metadata audit, and index fusion only when topic-layer changes exist.

What is the difference between flow2spec init and f2s-kb-upgrade?▼

flow2spec init is the CLI initialization command that writes template files to disk. f2s-kb-upgrade is the full upgrade skill that runs init plus version prechecks, topic cleanup, metadata audits, index fusion, and validation summaries.

When does f2s-kb-upgrade take the fast path?▼

It takes the fast path when the project's projectRev equals the package's pkgRev in .Knowledge/manifest-routing.json, meaning no topic-layer changes exist. It then skips cleanup, metadata audit, and index fusion, going straight to lightweight validation.

Can f2s-kb-upgrade migrate old V1 knowledge base layouts?▼

No. V1 layout migration support was removed with f2s-kb-migrate. The skill stops on V1 signals and instructs users to either use a historical package version (3.4.x or earlier) for one-time migration or manually move content into the .Knowledge structure.

Does f2s-kb-upgrade reset my existing knowledge base content?▼

No, it runs flow2spec init in incremental mode by default and never passes --reset-knowledge without explicit user confirmation. The project-maintained topic list section of index.md is preserved during template fusion.