Scan and load feature artifacts to build a holistic feature context.
npx skills add https://github.com/petbrains/mvp-builder --skill feature-analyzer
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
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.
Use the feature-analyzer skill to load and analyze all documentation for the 'user-onboarding' feature located in the 'features/' directory.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
Ikram-AlamAnalyze codebases and extract architecture insights via DeepWiki MCP server.
statick88Generate phased task breakdown checklists in markdown from design documents.
ProgrammerAnthonyConverts product requirement documents into GitHub issues by analyzing their content.
PBH-BTNAutomate verification of implementations against OpenSpec change artifacts.
