feature-gaps-find

Audit repository codebases to identify and validate product capability gaps.

2|Updated May 18, 2022

Search Tags:#audit #product-management #repository-analysis #gap-analysis #feature-discovery

Ready to run

npx skills add https://github.com/alexfalkowski/bin --skill feature-gaps-find

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-gaps-find
Source: https://github.com/alexfalkowski/bin/tree/main/skills/feature-gaps-find
Command: npx skills add https://github.com/alexfalkowski/bin --skill feature-gaps-find

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of identifying missing product capabilities that align with a repository's specific architecture and purpose, preventing the accumulation of irrelevant or out-of-scope feature requests.

Core Features & Use Cases

Scoped Discovery: Systematically audits codebases to find actionable product-facing improvements while filtering out noise like test or build-system tasks.
Evidence-Based Validation: Uses a rigorous acceptance gate to ensure every proposed feature is backed by concrete evidence and clear user value.
Use Case: A product manager can use this skill to audit a repository to determine if a proposed integration or API extension is a genuine product gap or merely a project-workflow improvement.

Quick Start

Use the feature-gaps-find skill to audit the current repository for missing product capabilities.

Frequently Asked Questions about feature-gaps-find

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

FAQPage Schema

How do I identify product capability gaps in a codebase?▼

Product capability gaps are identified through a scoped audit process that evaluates APIs, commands, and library behaviors. This approach filters out workflow noise to ensure proposed features align with the repository's architecture.

What is the best way to validate feature discovery for API extensions?▼

Validating feature discovery for API extensions requires an acceptance gate backed by concrete evidence and clear user value. This ensures high-quality proposals by meeting structured ledger formats and evidence-based confidence thresholds.

Does gap analysis exclude repository-workflow and test-harness concerns?▼

Yes, gap analysis excludes repository-workflow and test-harness concerns. It operates strictly on product-facing surfaces to prevent the accumulation of irrelevant or out-of-scope feature requests during the codebase audit.

How do I audit a repository to find actionable product improvements?▼

Auditing a repository for actionable product improvements involves systematically evaluating library behaviors and commands. It requires adhering to a structured ledger format and evidence-based confidence thresholds to validate genuine product gaps.

When do I need a structured ledger format for product gap analysis?▼

A structured ledger format is needed for product gap analysis when validating proposed integrations against an acceptance gate. It enforces evidence-based confidence thresholds to determine if an API extension is a genuine product gap.