extract-features

Catalog routes, models, jobs, tests, UI screens, and documented capabilities into a feature matrix.

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill extract-features-me2resh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extract-features
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/extract-features
Command: npx skills add https://github.com/me2resh/apexyard --skill extract-features-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you avoid expensive trial-and-error when rewriting an unfamiliar project by producing a single, granular inventory of what the existing system actually exposes and must preserve.

Core Features & Use Cases

  • Six-axis feature discovery: scans routes/entry points, data models, async jobs, test names, UI screens, and documented features to identify the full behavioral surface.
  • Greenfield rewrite “what we must preserve” spec: outputs a consolidated feature matrix that can be handed directly to the rewrite team as requirements input.
  • Optional UI mockups: with an opt-in flag, emits AI-inferred ASCII wireframes for discovered UI screens, each labeled with a strict source disclaimer for trust and verification.
  • Per-feature diagram linkage (via related skill): integrates with the per-feature diagram flow so the inventory can spawn route/model/job/screen diagrams for a specific feature.

Quick Start

Run /extract-features billing-api --with-mockups to generate feature-inventory.md plus an AI-inferred screens section for each discovered UI screen in the billing-api project.

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 for a greenfield rewrite?▼

A feature inventory for a greenfield rewrite catalogs routes, data models, jobs, tests, and UI screens into a consolidated matrix. This documents the exact behavioral surface that must be preserved during replatforming or migration.

What is the best way to document API routes and database models before a framework migration?▼

Documenting API routes and database models before a framework migration involves scanning the existing codebase to extract entry points and schemas. This identifies the full behavioral surface, ensuring no existing capabilities are lost during the transition.

How do I generate UI mockups from an existing codebase for system documentation?▼

Generating UI mockups from an existing codebase involves scanning for UI screens and emitting AI-inferred ASCII wireframes. These mockups include strict source disclaimers for trust and verification during system documentation.

Can I extract a feature matrix from an inherited repository without breaking existing behavior?▼

Yes, extracting a feature matrix from an inherited repository catalogs routes, models, and documented capabilities. This preserves exact behavior by producing a requirements spec for the rewrite team without modifying the original code.

Does the feature inventory include async jobs and test names?▼

Yes, the feature inventory includes async jobs and test names as part of its six-axis discovery process. Cataloging these elements ensures background tasks and existing test coverage are preserved during replatforming or language migration.