skills.rest
MohamedSayedK
MohamedSayedKCOMMUNITY
Explore all skills by this author →
GitHub

extract-features

Generate a feature inventory documenting what to preserve before a codebase rewrite or migration.

Updated Jun 2, 2026
Search Tags:#onboarding#migration#legacy code#artifact generation#stack detection#code rewrite#feature inventory
One-click install
npx skills add https://github.com/MohamedSayedK/omnigrid --skill extract-features-mohamedsayedk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extract-features
Source: https://github.com/MohamedSayedK/omnigrid/tree/main/assets/core/skills/extract-features
Command: npx skills add https://github.com/MohamedSayedK/omnigrid --skill extract-features-mohamedsayedk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before rewriting or migrating a legacy codebase, teams need a clear record of which user-facing capabilities must survive the change. This Skill produces a footer-signed feature inventory with the detected stack and harnessability auto-filled, so nothing critical is lost during a rewrite. ## Core Features & Use Cases - Automatic stack detection: Reuses the Ecosystem-probe registry detector to fill the detected-stack and harnessability sections without hardcoded frameworks. - Regeneration-safe artifacts: On re-run it archives the previous inventory to a dated copy and writes the fresh one to the canonical path, honoring the artifact regeneration contract; hand-owned files are never overwritten. - Use Case: Before migrating a legacy application to a new framework, run the inventory to capture the current stack, then fill the "What to preserve" table with one row per user-facing capability that must survive the migration. ## Quick Start Run omnigrid extract-features in the project to generate a feature inventory under omnigrid/artifacts/features/ and then fill in the features to preserve.

Frequently Asked Questions about extract-features

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

FAQPage Schema
How do I create a feature inventory before a code migration?▼

Run omnigrid extract-features in the project root. It auto-fills the detected stack and harnessability using the Ecosystem-probe detector, then writes a feature inventory to omnigrid/artifacts/features/feature-inventory.md for you to complete with the capabilities to preserve.

What does the extract-features command detect automatically?▼

It detects the project's stack and harnessability score using the same Ecosystem-probe registry detector that onboarding uses, with no hardcoded frameworks. The actual feature list is not detected; the consumer fills in the What to preserve table manually.

What happens when I re-run the feature inventory generation?▼

On re-run, the previous feature-inventory.md is archived to a dated copy like feature-inventory-YYYY-MM-DD.md, and the fresh inventory is written to the canonical path. The --force flag overwrites in place instead.

Will extract-features overwrite my hand-edited inventory file?▼

No. A feature-inventory.md without the generated footer is treated as hand-owned and is never overwritten, even with --force. You must delete it manually to regenerate the file.

When should I run a feature inventory in a project?▼

Run it at onboarding time, especially before a rewrite or migration of a legacy codebase. It captures the what-to-preserve snapshot, and you can then run feature-diagram to slice a single feature into a per-feature diagram.

Related Skills

Explore More Software Engineering Skills→
AAbdulghanyAAbdulghany

handover

Generate a handover assessment and harnessability score for external repositories.

Community
Advanced
me2reshme2resh
489

feature-diagram

Generate per-feature Mermaid flowcharts linking routes, models, jobs, and screens.

Community
Advanced
EnigmaWUEnigmaWU
1

document-architectural-decisions

Write structured 12-field Architectural Decision Records using Kruchten's decision ontology.

Community
Advanced
russosalvrussosalv
5

vscode-config-generator

Generate VS Code tasks.json and launch.json for detected Node, .NET, and Python stacks.

Community
Intermediate