skills.rest
asmortongpt
asmortongptCOMMUNITY
Explore all skills by this author →
GitHub

requirements-analysis

Analyze and document software requirements with user stories and acceptance criteria.

Updated Aug 23, 2026
Search Tags:#planning#requirements#specifications#MoSCoW#user-stories#acceptance-criteria#stakeholders
One-click install
npx skills add https://github.com/asmortongpt/Fleet-AzureDevOps --skill requirements-analysis-asmortongpt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-analysis
Source: https://github.com/asmortongpt/Fleet-AzureDevOps/tree/main/.claude/skills/requirements-analysis
Command: npx skills add https://github.com/asmortongpt/Fleet-AzureDevOps --skill requirements-analysis-asmortongpt

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill guides teams to transform vague ideas into concrete, actionable software requirements, ensuring every project starts with a clear scope and direction.

Core Features & Use Cases

  • Framework for gathering context, goals, and success criteria from stakeholders.
  • Templates for user stories, acceptance criteria, and MoSCoW prioritization.
  • Deliverables including Requirements Document, User Stories Backlog, and Technical Specifications.

Quick Start

Start by defining project context and success criteria, then generate high-level user stories and acceptance criteria.

Frequently Asked Questions about requirements-analysis

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

FAQPage Schema
How do I write software requirements from vague project ideas?▼

To write software requirements, use a systematic framework to capture project context, goals, and success criteria from stakeholders. This process transforms vague ideas into actionable user stories, technical specifications, and clear project scopes.

What is MoSCoW prioritization and how do I apply it to user stories?▼

MoSCoW prioritization categorizes requirements into Must-have, Should-have, Could-have, and Won't-have tiers. It is applied to user stories to ensure teams deliver critical functionality first and manage project scope effectively during early planning sessions.

How do I write acceptance criteria for technical specifications?▼

Acceptance criteria are written using structured templates that define specific pass/fail conditions for user stories. This skill generates these criteria alongside technical specifications to ensure development teams have clear boundaries for feature implementation and testing.

Can I use this for early planning sessions across engineering teams?▼

Yes, this skill is designed for early planning sessions across product management and engineering teams. It captures functional and non-functional requirements, ensuring both technical and business stakeholders align on project direction before development begins.

What deliverables should I expect from the requirements analysis process?▼

The requirements analysis process yields structured deliverables including a comprehensive Requirements Document, a prioritized User Stories Backlog, and detailed Technical Specifications. These outputs provide a clear scope and actionable direction for software development.

Related Skills

Explore More Product & Management Skills→
AlekseiULAlekseiUL
64

business-architect

Transform raw ideas into structured business plans with milestones and lean canvas outputs.

Community
Advanced
jackmochjackmoch

Ticket Generation Skill

Generate implementation tickets with acceptance criteria and dependency mapping from design documents.

Community
Advanced
Fantasia1999Fantasia1999

agile-product-owner

Generate INVEST-compliant user stories with Given-When-Then acceptance criteria.

Community
Advanced
pxlcrtivpxlcrtiv

writing-fragments

Collect writing fragments and append them to a markdown document.

Community
Basic