feature-inventory Skill
Catalogs existing features from a codebase (API endpoints, user flows, UI screens, observable behaviors) and generates structured feature specs with REQ-XXX IDs, user scenarios, and success criteria. Triggers: "inventory features", "catalog existing functionality", "list what the app does", "extract requirements from c Published by microsoft in github-copilot-modernization.
What is feature-inventory Skill?
Catalogs existing features from a codebase (API endpoints, user flows, UI screens, observable behaviors) and generates structured feature specs with REQ-XXX IDs, user scenarios, and success criteria. Triggers: "inventory features", "catalog existing functionality", "list what the app does", "extract requirements from c Published by microsoft in github-copilot-modernization. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Design and media use cases
Technical details
- Install or run with Copy skill directory
When to use feature-inventory Skill
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/github-copilot-modernization
- Skill file: plugins/github-copilot-modernization/skills/feature-inventory/SKILL.md
What it does
Catalogs existing features from a codebase (API endpoints, user flows, UI screens, observable behaviors) and generates structured feature specs with REQ-XXX IDs, user scenarios, and success criteria. Triggers: "inventory features", "catalog existing functionality", "list what the app does", "extract requirements from c
Skill instructions
User Input You MUST consider the user input before proceeding (if not empty). The text in the task description is the feature description. Assume you always have it available. Do not ask the user to repeat it unless they provided an empty command. Outline Given that feature description, do this: Output All outputs are written under your task's Artifact path: (from task metadata). spec.md ← main artifact (feature specification) requirements-checklist.md ← quality checklist (if applicable) Workflow 1. Load constitution document (if available) to understand principles and constraints. 2. Load clarification.md if it exists ({{BASEPATH}}/clarification.md or path from dependencyArtifacts). Treat every field that has an explicit value (i.e., resolution: user or resolution: default) as already resolved — do NOT re-ask the user about it and do NOT count it against the [NEEDS CLARIFICATION] budget below. Items listed under blockinggaps should be treated as known risks but still do not count agai
Explore related resources
Frequently asked questions
What is feature-inventory?
feature-inventory is a open-source AI agent skill with Copy skill directory. Catalogs existing features from a codebase (API endpoints, user flows, UI screens, observable behaviors) and generates structured feature specs with REQ-XXX IDs, user scenarios, and success criteria.
Who is feature-inventory best for?
feature-inventory is best for reusing agent instructions, scripts, and references, design and media workflows.
How do I install feature-inventory?
Install or run feature-inventory using Copy skill directory. Check feature-inventory for the latest setup command.
Is feature-inventory actively maintained?
feature-inventory may need a closer maintenance check before production use.
Auto-fetched from GitHub.
