What problem does it solve? Projects using the legacy knowledge organization (docs-index.md, rules/main.md, scattered business skills, and stock-docs/req-docs folders) need a controlled, one-time migration into the new .Knowledge architecture without losing files or leaving dual entry points behind. ## Core Features & Use Cases - Full Inventory and Mapping: Reads docs-index.md and rules entry files to build topic, business rule, business skill, and document migration queues, excluding f2s-* package skills. - Staged Migration with State Recovery: Migrates topics, stock-docs, and req-docs one item at a time with user confirmation, tracked in .Knowledge/.migrate-state.json for pause and resume. - Mandatory Report and Cleanup: Writes .Knowledge/migration-report.md with a migration mapping table and deletion checklist, then deletes confirmed legacy rules, skills, and index files while preserving baseline f2s-* rules. - Use Case: A team upgrading an old Flow2Spec project runs this skill to move all legacy rules and docs into .Knowledge, review the deletion checklist, and finish with a clean single-entry knowledge base. ## Quick Start Ask the agent to migrate the legacy knowledge base to .Knowledge by running the f2s-kb-migrate skill on this repository.
