feature-analyzer

Analyze feature artifacts and output a structured readiness summary.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/andrey-belen/alto-iam-cloud --skill feature-analyzer-andrey-belen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-analyzer
Source: https://github.com/andrey-belen/alto-iam-cloud/tree/main/.claude/skills/feature-analyzer
Command: npx skills add https://github.com/andrey-belen/alto-iam-cloud --skill feature-analyzer-andrey-belen

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill helps teams load and analyze all feature artifacts to form a complete feature context before implementation, ensuring prerequisites and alignment across artifacts.

Core Features & Use Cases

  • Load and verify feature documents (spec.md, ux.md, plan.md, tasks.md, data-model.md, contracts/, research.md, setup.md)
  • Build a unified mental model of requirements and architecture for downstream planning and checklists
  • Prepare context for downstream tasks like checklist generation, task planning, and architecture queries
  • Trigger-driven activation: analyze feature, load feature context, prepare feature, check feature prerequisites, and understand feature scope

Quick Start

Run the prerequisites check for a feature directory and review its JSON output to confirm AVAILABLE and MISSING and readiness. Use: .claude/skills/feature-analyzer/scripts/check-prerequisites.sh /path/to/feature

Frequently Asked Questions about feature-analyzer

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

FAQPage Schema
How do I analyze feature artifacts to check readiness before implementation?

To analyze feature artifacts for readiness, run the prerequisites check script against your feature directory to verify coverage of spec.md, ux.md, plan.md, and tasks.md, outputting a structured JSON readiness summary.

What is feature context and why do I need it for architecture planning?

Feature context is a unified mental model built by loading and verifying feature documents like data-model.md and contracts. It ensures alignment across requirements and architecture, forming the baseline for downstream checklist generation and task planning.

How do I verify feature prerequisites and artifact coverage using jq?

You can verify feature prerequisites using jq to parse the JSON readiness summary output by the check-prerequisites script, which identifies AVAILABLE and MISSING documents within the target feature directory.

Can I use feature-analyzer to prepare context for task planning and checklists?

Yes, you can use feature-analyzer to prepare context for task planning and checklists by loading core documents such as research.md and setup.md to enforce artifact coverage and output a structured readiness summary.

What is the best way to load feature documents for downstream architecture queries?

The best way to load feature documents for architecture queries is to execute the prerequisites check script, which scans the feature directory and consolidates spec.md, plan.md, and contracts into a unified readiness summary.

What happens if required feature artifacts like spec.md or data-model.md are missing?

If required feature artifacts are missing, the prerequisites check script flags them as MISSING in its JSON readiness output, explicitly enforcing artifact coverage so you can resolve gaps before proceeding with implementation.