skills.rest
microsoft
microsoftOFFICIAL
Explore all skills by this author →
Website𝕏@OpenAtMicrosoftGitHub

feature-inventory

Catalog codebase features into structured specs with REQ-XXX IDs.

35|8|Updated Feb 6, 2026
Search Tags:#codebase#requirements#traceability#inventory#acceptance-criteria#feature-spec#user-scenarios
One-click install
npx skills add https://github.com/microsoft/github-copilot-modernization --skill feature-inventory-microsoft
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-inventory
Source: https://github.com/microsoft/github-copilot-modernization/tree/main/plugins/github-copilot-modernization/skills/feature-inventory
Command: npx skills add https://github.com/microsoft/github-copilot-modernization --skill feature-inventory-microsoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Catalogs existing features from a codebase (APIs, user flows, UI screens, observable behaviors) and generates structured feature specs with REQ-XXX IDs, user scenarios, and success criteria.

Core Features & Use Cases

  • Catalog existing features from codebase (APIs, user flows, UI screens, observable behaviors)
  • Generate feature specs with REQ-XXX IDs, user scenarios, and success criteria
  • Produce a spec document ready for planning

Quick Start

Describe the feature you want analyzed, and I will generate a complete feature spec.

Frequently Asked Questions about feature-inventory

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

FAQPage Schema
How do I extract existing feature specs from a codebase?▼

Feature specs catalog existing codebase behaviors like APIs, user flows, and UI screens into structured requirements. This process generates testable functional requirements complete with user scenarios and success criteria for software planning.

How do I generate traceable requirements for software discovery and planning?▼

You generate traceable requirements by cataloging codebase features into structured specifications. This assigns unique REQ-XXX IDs to functional requirements, ensuring traceability between user scenarios and acceptance criteria during software discovery.

What is the best way to document user scenarios and acceptance criteria?▼

The best way to document user scenarios is by generating structured feature specifications from a codebase. This catalogs observable behaviors into testable functional requirements, assigning traceable REQ-XXX IDs and clear acceptance criteria.

Can I catalog UI behaviors and APIs into testable functional requirements?▼

Yes, you can catalog UI behaviors and APIs into testable functional requirements. Analyzing a codebase extracts user flows and observable behaviors, generating structured feature specs complete with traceable REQ-XXX IDs and success criteria.

Does feature inventorying work for projects already in the planning phase?▼

Feature inventorying applies specifically to software projects in discovery and planning. It analyzes existing codebases to extract APIs and user flows, producing ready-to-review spec documents with traceable REQ-XXX IDs and success criteria.

Related Skills

Explore More Product & Management Skills→
TheycallmehollaTheycallmeholla

eli5-features

Generate plain-language help articles from codebase features and UI terminology.

Community
Intermediate
ArtemioPadillaArtemioPadilla
3

traceability

Generate a bi-directional traceability matrix linking acceptance criteria to code, tests, and reviews.

Community
Advanced
olehsvyrydovolehsvyrydov
13

tester

Design test cases and reproduction tests from acceptance criteria.

Community
Intermediate
product-on-purposeproduct-on-purpose
527

deliver-user-stories

Generate user stories and Given/When/Then acceptance criteria from product requirements.

Official
Basic