feature-inventory

Generates feature inventory files (FEATURES.json, FEATURES.md) and checks drift in CI.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/qdouble/stack-contracts --skill feature-inventory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-inventory
Source: https://github.com/qdouble/stack-contracts/tree/main/.agent/skills/feature-inventory
Command: npx skills add https://github.com/qdouble/stack-contracts --skill feature-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the discovery and cataloging of all project capabilities, ensuring a consistent and up-to-date inventory for better project understanding and maintenance.

Core Features & Use Cases

  • Automated Discovery: Scans code and configuration files to identify endpoints, IPC channels, skills, workflows, scripts, and more.
  • Inventory Generation: Produces both machine-readable (FEATURES.json) and human-readable (FEATURES.md) versions of the capability catalog.
  • CI Integration: Includes a check mode to detect drift between committed artifacts and the current codebase.
  • Use Case: Before adding a new API endpoint or IPC channel, use this Skill to ensure it's automatically registered and documented in the feature inventory.

Quick Start

Run the command to generate the feature inventory artifacts.

Frequently Asked Questions about feature-inventory

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

FAQPage Schema
How do I automatically generate a feature inventory for my software project?

To generate a feature inventory, run the provided scripts to scan your project and automatically catalog IPC channels, HTTP endpoints, skills, workflows, and UI panels into JSON and Markdown outputs.

What is an automated feature inventory and why do I need one for API discovery?

An automated feature inventory is a catalog of project capabilities like HTTP endpoints and IPC channels. You need it to maintain an up-to-date understanding of your codebase for easier project maintenance.

Can I use a feature inventory check mode to detect CI drift in my codebase?

Yes, you can use the integrated CI check mode to detect drift between your committed inventory artifacts and the current codebase, ensuring your documentation remains consistently synchronized.

What is the best way to document HTTP endpoints and IPC channels automatically?

The best way to document these capabilities is using an automated discovery script that scans your configuration files to produce both machine-readable JSON and human-readable Markdown catalogs.

Does the feature inventory support generating both machine-readable and human-readable outputs?

Yes, the feature inventory supports generating both machine-readable FEATURES.json and human-readable FEATURES.md files, providing formats for automated processing and developer reference.

What limitations exist when cataloging UI panels and scripts into a feature inventory?

A limitation is that the inventory relies on scanning code and configuration files, meaning capabilities not properly registered or dynamically generated may be missed during the automated discovery process.