analyze-requirements

To turn a vague feature idea into structured user stories and PBIs, provide the written request to the skill. It analyzes the input and outputs a complete requirements package including user stories, acceptance criteria, and dependency maps.

Codebase analysis for new feature requirements identifies reusable components by scanning existing modules to assess feasibility and pinpoint integration opportunities. This assessment is then saved directly within the generated requirements markdown document.

Yes, you can automatically generate acceptance criteria and dependency maps from a feature request. The skill translates your input into these structured elements, creating a polished requirements package ready for development planning.

The best way to document feature requirements and PBI decomposition is to generate a standardized markdown file. The skill saves the polished requirements, including PBI decomposition and reuse assessments, under docs/requirements/[feature-name]-requirements.md.

You need a project structure that supports a docs directory to save generated requirements and user stories. The skill outputs the finalized markdown documents directly to the path docs/requirements/ within your existing codebase.