f2s-kb-migrate

Migrate legacy knowledge bases to the .Knowledge format with cleanup and reporting.

40|4|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Lands-1203/Flow2Spec --skill f2s-kb-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: f2s-kb-migrate
Source: https://github.com/Lands-1203/Flow2Spec/tree/main/.cursor/skills/f2s-kb-migrate
Command: npx skills add https://github.com/Lands-1203/Flow2Spec --skill f2s-kb-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill migrates legacy knowledge bases from old structures to the new .Knowledge format, ensuring AI has a comprehensive and structured project memory.

Core Features & Use Cases

  • Legacy Knowledge Base Migration: Moves old knowledge base entries to the new .Knowledge structure.
  • Unified Entry Point: Utilizes a unified entry point for rules and skills, simplifying AI interactions.
  • Documentation Migration: Transfers stock and requirement documents to the .Knowledge directory.
  • Cleanup and Reporting: Ensures proper cleanup and generates a migration report for review.
  • Use Case: For a project that still uses the old knowledge base structure, this Skill will facilitate a smooth transition to the new .Knowledge format, enhancing AI's ability to remember project context across sessions.

Quick Start

Migrate the legacy knowledge base by running the 'f2s-kb-migrate' skill.

Frequently Asked Questions about f2s-kb-migrate

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

FAQPage Schema
How do I migrate a legacy knowledge base to the new .Knowledge format for AI project memory?

Migrating a legacy knowledge base to the .Knowledge format involves moving old entries to the new structure, enabling structured AI project memory across sessions.

What is the .Knowledge format and when do I need it for AI context?

The .Knowledge format is a structured project memory directory that provides a unified entry point for rules and skills. You need it when upgrading legacy structures to enhance AI context retention.

How do I transfer stock and requirement documents during a knowledge base migration?

Transferring stock and requirement documents during a knowledge base migration moves them directly to the .Knowledge directory. This ensures proper documentation transfer alongside structural migrations.

Does knowledge base migration support both automated and manual workflows?

Knowledge base migration supports both automated and manual workflows. It requires coordination with various project files and directories to handle structural and document-level transitions properly.

What is the best way to clean up and report on a legacy knowledge base migration?

The best way to clean up a legacy knowledge base migration is to use a process that ensures proper cleanup and generates a migration report. This allows you to review the transferred project memory.