feature-analyzer

Gather requirements and generate design documents for feature planning.

340|43|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/notedit/happy-skills --skill feature-analyzer-notedit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-analyzer
Source: https://github.com/notedit/happy-skills/tree/main/skills/feature-analyzer
Command: npx skills add https://github.com/notedit/happy-skills --skill feature-analyzer-notedit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning ideas into clearly defined designs and specs through structured discovery and collaborative validation, reducing ambiguity and rework during feature planning and major codebase changes.

Core Features & Use Cases

  • Structured context discovery to understand project structure, tech stack, patterns, and dependencies
  • Guided information gathering with question rounds to capture requirements, constraints, and success criteria
  • Design presentation workflow to generate architecture and design documents for engineers and stakeholders
  • Use Case: When planning a new feature, run this skill to produce a design spec lineage with goals, scope, and acceptance criteria

Quick Start

Provide a feature concept to start gathering requirements and design options.

Frequently Asked Questions about feature-analyzer

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

FAQPage Schema
How do I turn feature ideas into structured design specs?

To turn feature ideas into structured design specs, this skill uses guided dialogue to capture requirements, validate approaches, and generate architecture documents with goals, scope, and acceptance criteria.

What is the best way to gather requirements for architecture decisions?

The best way to gather requirements for architecture decisions is through structured information gathering with multiple question rounds to capture constraints, success criteria, and project dependencies.

How does guided information gathering work for product management planning?

Guided information gathering for product management planning works by running a structured discovery phase that analyzes your tech stack and patterns before presenting design options and generating documentation.

Can I use this for feature planning during substantial codebase changes?

Yes, you can use this for feature planning during substantial codebase changes, as it produces clear design artifacts and specifications to reduce ambiguity and rework for engineers and stakeholders.

What do I need to provide to start generating design documentation?

To start generating design documentation, you only need to provide a feature concept, and the skill will initiate the structured discovery process to gather context and explore design options.