skills.rest
Luis-ERP
Luis-ERPCOMMUNITY
Explore all skills by this author →
GitHub

feature-analyze

Generate a structured Phase 1 analysis document from a user requirement.

Updated Feb 5, 2026
Search Tags:#documentation#analysis#feature#analyze#product-management#requirement#phase-1
One-click install
npx skills add https://github.com/Luis-ERP/dev-agent-crew --skill feature-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-analyze
Source: https://github.com/Luis-ERP/dev-agent-crew/tree/main/skills/feature-analyze
Command: npx skills add https://github.com/Luis-ERP/dev-agent-crew --skill feature-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps product teams crystallize the purpose, scope, and value of a new feature by producing a clear Phase 1 analysis based on a user requirement.

Core Features & Use Cases

  • Phase 1 analysis template generation: outputs a structured 01-analysis.md with context, problem statements, scope, assumptions, risks, and acceptance criteria.
  • Update feature index: automatically marks the feature's status and links to artifacts.
  • Stakeholder communication: provides a human-readable rationale to align teams before design.

Quick Start

Provide the 00-requirement.md for the feature slug docs/features/<slug>/00-requirement.md and run the Analyze phase to generate 01-analysis.md and update the feature index accordingly.

Frequently Asked Questions about feature-analyze

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

FAQPage Schema
How do I generate a Phase 1 analysis document from a user requirement?▼

To generate a Phase 1 analysis document, provide a 00-requirement.md file for your feature slug. The tool outputs a structured 01-analysis.md covering context, problem statements, scope, assumptions, risks, and acceptance criteria.

What is included in a feature analysis document for early product scoping?▼

A feature analysis document for early scoping includes the context, problem statements, project boundaries, assumptions, risks, and acceptance criteria needed to clarify what to build and why it matters.

How do I create feature scope and acceptance criteria from a requirement file?▼

You can create feature scope and acceptance criteria by running the analysis phase on your 00-requirement.md file. This automatically produces a structured 01-analysis.md document defining the project boundaries and validation criteria.

Can I update the feature index automatically after analyzing a new requirement?▼

Yes, generating the analysis document automatically updates the feature index. It marks the feature's current status and links to the newly created 01-analysis.md artifact while preserving the original 00-requirement for traceability.

Does early feature scoping help with stakeholder communication and team alignment?▼

Early feature scoping provides a human-readable rationale that aligns teams before design begins. The structured 01-analysis.md document clarifies the purpose, scope, and value of a new feature for all stakeholders.

What file format do I need to start analyzing a feature requirement?▼

You need a markdown file named 00-requirement.md placed in the docs/features/<slug>/ directory. This serves as the input for generating the 01-analysis.md document and updating the feature index.

Related Skills

Explore More Product & Management Skills→
loicalleyneloicalleyne
1

write-readme

Generate bufarrow-style READMEs from AGENTS.md, manifest files, and user details.

Community
Advanced
felix-howardfelix-howard

ck:plan

Generate technical implementation plans with phased documentation and architecture design.

Community
Advanced
Thawatchai-PetkaewThawatchai-Petkaew

delivery-artifacts

Manage versioned delivery artifacts and synchronize them with Linear issue tracking.

Community
Advanced
dr-codedr-code

feature-spec

Creates comprehensive feature specification documents in docs/specs/format.

Community
Advanced