Spec Analyzer Skill

Analyze unstructured project specifications and output a structured RequirementsManifest in JSON.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/mdmagnuson-creator/helm-ade-toolkit --skill spec-analyzer-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Spec Analyzer Skill
Source: https://github.com/mdmagnuson-creator/helm-ade-toolkit/tree/main/skills/spec-analyzer
Command: npx skills add https://github.com/mdmagnuson-creator/helm-ade-toolkit --skill spec-analyzer-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of extracting structured requirements from unstructured project specifications, saving significant time and ensuring clarity.

Core Features & Use Cases

  • Automated Requirement Extraction: Analyzes project specs, PRDs, or feature descriptions to identify key aspects like product type, business model, scale, features, integrations, constraints, entities, and user stories.
  • Structured Output: Generates a RequirementsManifest in JSON format, compatible with other development tools.
  • Interactive Mode: Guides users through a series of questions to gather requirements when input is ambiguous.
  • Use Case: Provide a raw feature description for a new SaaS product, and the Skill will output a detailed RequirementsManifest that can be directly used by a Stack Advisor to recommend technologies.

Quick Start

Use the spec-analyzer skill to analyze the project specification located at /path/to/project/spec.md.

Frequently Asked Questions about Spec Analyzer Skill

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

FAQPage Schema
How do I extract structured requirements from unstructured project specifications?

To extract structured requirements from unstructured project specifications, use the Spec Analyzer to identify product type, business model, features, and user stories, outputting a structured RequirementsManifest in JSON format.

What is a RequirementsManifest and how does it organize product management documentation?

A RequirementsManifest is a JSON schema output that organizes product management documentation by structuring extracted entities, integrations, constraints, and user stories from raw specification text into a standardized format.

Can I analyze specifications from a file path or URL instead of pasting text?

Yes, you can analyze specifications from a file path or URL. The Skill accepts text, file paths, or URLs as input to process unstructured project specifications and extract the structured requirements.

How do I generate user stories from a raw feature description for a SaaS product?

To generate user stories from a raw feature description for a SaaS product, input the description into the analyzer. It identifies scale, features, and entities, then outputs structured user stories within the JSON manifest.

Does the spec analysis tool support interactive clarification for ambiguous requirements?

Yes, the spec analysis tool supports interactive clarification. When input is ambiguous, it guides users through a series of questions to accurately gather and extract the necessary product requirements.

What's the best way to convert a PRD into JSON format for development tools?

The best way to convert a PRD into JSON format for development tools is to run the Spec Analyzer on the document. It produces a conforming RequirementsManifest JSON containing features, constraints, and entities.