pm-reverse-extract

Name: pm-reverse-extract
Availability: InStock
Author: ljucask

Extract product capabilities into structured feature inventories and migration-ready documentation.

1|Updated May 28, 2026

Search Tags:#code analysis #feature extraction #fdd #product migration #feature cards #product inventory

Ready to run

npx skills add https://github.com/ljucask/pureinn-product-development --skill pm-reverse-extract

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-reverse-extract
Source: https://github.com/ljucask/pureinn-product-development/tree/main/skills/pm-reverse-extract
Command: npx skills add https://github.com/ljucask/pureinn-product-development --skill pm-reverse-extract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of migrating existing products into a structured product development framework by extracting real feature inventory from codebases, documents, and existing specifications.

Core Features & Use Cases

Feature Inventory Extraction: Reads product documentation, code references, API specifications, and existing Feature Cards to build a structured FDD feature register.
Migration Workflow Support: Creates Feature Cards, assigns delivery stripes, identifies missing JIT design work, and prepares product teams for continued development.
Use Case: A team inheriting an existing application can use this Skill to discover implemented capabilities, reconcile product knowledge with code reality, and organize future delivery priorities.

Quick Start

Use the pm-reverse-extract skill to analyze my existing product codebase and documents and generate a complete feature inventory with Feature Cards.

Frequently Asked Questions about pm-reverse-extract

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

FAQPage Schema

How do I extract a feature inventory from an existing product codebase?▼

To extract a feature inventory from an existing product, analyze product artifacts, code references, and API specifications to build a structured FDD feature register. This process reconciles code evidence with product documentation to map real application capabilities.

What is the best way to migrate legacy applications into feature-driven development?▼

Migrating legacy applications into feature-driven development involves reading existing specifications to generate Feature Cards and assign delivery stripes. This identifies missing JIT design work and prepares teams for structured transition workflows.

How do I generate Feature Cards from existing product documentation and code evidence?▼

Generating Feature Cards from product documentation and code evidence requires analyzing domain registers and feature identifiers. This creates migration-ready product documentation that synchronizes implemented capabilities into structured formats.

Can I reconcile product knowledge with code reality during product onboarding?▼

You can reconcile product knowledge with code reality during product onboarding by extracting actual feature inventory from codebases and existing specifications. This discovers implemented capabilities and organizes future delivery priorities accurately.

Does feature extraction work without existing Feature Cards or domain registers?▼

Feature extraction works by analyzing available product artifacts and code references, but having existing Feature Cards and domain registers enhances the output. It builds a structured FDD feature register using whatever evidence exists.

When should I use reverse feature extraction for product synchronization?▼

Use reverse feature extraction for product synchronization when inheriting existing applications or migrating to feature-driven workflows. It discovers implemented capabilities and organizes delivery priorities by analyzing codebases and documents.