extract-features

Inventory codebase features across six discovery axes into a feature-inventory.md artifact.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill extract-features-aabdulghany
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extract-features
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/extract-features
Command: npx skills add https://github.com/AAbdulghany/fms --skill extract-features-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The six-axis feature inventory consolidates a codebase's capabilities into a single reference to guide greenfield rewrites and architectural decisions.

Core Features & Use Cases

  • Discovers features across HTTP routes, data models, async jobs, tests, UI screens, and documentation.
  • Produces a unified feature-inventory artifact for planning, handover, or code rewrites.
  • Supports mono- and multi-repo projects to surface cross-cutting features.

Quick Start

Analyze a repository and generate the feature inventory for the target project in one run.

Frequently Asked Questions about extract-features

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

FAQPage Schema
How do I inventory features across a codebase before a greenfield rewrite?▼

A six-axis feature inventory consolidates codebase capabilities into a single reference artifact by discovering routes, models, jobs, tests, UI screens, and documentation, then deduplicating findings to guide architectural decisions and rewrites.

Can I analyze features across multiple repositories or monorepos?▼

Feature inventory supports mono- and multi-repo projects, collecting routes, models, jobs, tests, UI screens, and documentation to surface cross-cutting features for greenfield rewrites.

How do I generate a feature inventory artifact for my project?▼

Run the feature inventory analysis across your codebase to collect and deduplicate findings from six discovery axes, producing a unified markdown artifact at projects/<name>/feature-inventory.md.

What's the best way to deduplicate features discovered through static codebase analysis?▼

Deduplicate features by collecting capabilities across six discovery axes—routes, models, jobs, tests, UI screens, and documentation—and consolidating overlapping findings into a single feature inventory artifact.

Does the feature inventory validate discovered signatures against the actual codebase?▼

The feature inventory validates discovered signatures using grep-based rules and optional mockups to ensure collected routes, models, jobs, tests, and UI screens accurately reflect the codebase.

When should I use a six-axis feature inventory instead of manual codebase documentation?▼

Use a six-axis feature inventory when planning greenfield rewrites or architectural decisions across multi-repo or monorepo projects, where manual documentation would miss cross-cutting capabilities and lack deduplicated feature tracking.