feature-analyzer

Name: feature-analyzer
Availability: InStock
Author: petbrains

Scan and load feature artifacts to build a holistic feature context.

13|2|Updated Aug 9, 2025

Search Tags:#automation #planning #documentation #requirements #prerequisites #feature-analysis #context-building

Ready to run

npx skills add https://github.com/petbrains/mvp-builder --skill feature-analyzer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-analyzer
Source: https://github.com/petbrains/mvp-builder/tree/main/.claude/skills/feature-analyzer
Command: npx skills add https://github.com/petbrains/mvp-builder --skill feature-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill eliminates the time-consuming manual process of reading through scattered feature documentation by automatically scanning, loading, and building a comprehensive mental model of all feature artifacts before implementation begins.

Core Features & Use Cases

Artifact Scanning: Automatically checks for required files (spec.md, ux.md, plan.md, tasks.md) and reports what's available or missing.
Context Building: Extracts and internalizes requirements, user flows, architecture plans, and implementation tasks into a unified understanding.
Use Case: Imagine starting work on a new "payment processing" feature. This Skill scans the feature directory, loads all documentation, and prepares you with complete context about requirements, user interactions, technical architecture, and task sequence—saving hours of manual reading.

Quick Start

Use the feature-analyzer skill to load and analyze all documentation for the 'user-onboarding' feature located in the 'features/' directory.

Frequently Asked Questions about feature-analyzer

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

FAQPage Schema

How do I automatically load and understand all feature documentation before implementation?▼

Feature-analyzer scans your feature directory for required artifacts (spec.md, ux.md, plan.md, tasks.md, data-model.md, contracts/, research.md, setup.md), loads them in priority order, and builds a unified mental model of requirements, user flows, architecture, and tasks—eliminating manual reading and preparation time.

What files and artifacts does feature-analyzer check for when scanning a feature?▼

The Skill scans for core artifacts: spec.md (requirements), ux.md (user interactions), plan.md (architecture), tasks.md (implementation sequence), data-model.md (data structure), contracts/ (interfaces), research.md (context), and setup.md (environment). It reports what's available and flags gaps before analysis.

Can I use feature-analyzer to validate that a feature has all its prerequisites documented?▼

Yes. Feature-analyzer includes artifact validation and prerequisites-checking functionality, scanning for required documentation files and confirming readiness before implementation begins, surfacing missing artifacts that would block development.

How does feature-analyzer help with generating implementation checklists and architecture decisions?▼

By loading and internalizing all feature artifacts into a comprehensive context model, feature-analyzer extracts the foundation needed to generate task checklists, validate architecture decisions, and identify dependencies—turning scattered documentation into actionable implementation guidance.

What's the workflow for using feature-analyzer on a new feature project?▼

Feature-analyzer follows a four-step workflow: Scan (detect available artifacts), Load (extract content and metadata), Build (construct mental model of requirements and architecture), and Confirm (report readiness and gaps)—completing end-to-end before you begin coding.

Does feature-analyzer require any dependencies or tools to run?▼

Feature-analyzer depends on jq for JSON processing and uses scripts and references components to parse and validate feature artifacts, making it lightweight and compatible with standard documentation workflows.