business-analysis

Gather business requirements into structured SRS documents and Given/When/Then acceptance criteria.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/duylinhdang1998/claude-template-agent --skill business-analysis-duylinhdang1998
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-analysis
Source: https://github.com/duylinhdang1998/claude-template-agent/tree/main/plugins/vfm-agent-company/skills/business-analysis
Command: npx skills add https://github.com/duylinhdang1998/claude-template-agent --skill business-analysis-duylinhdang1998

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Projects suffer from ambiguous requirements, uncontrolled scope, and untestable user stories; this skill transforms stakeholder inputs into clear, measurable, and prioritized requirements so teams build the right product with minimal rework.

Core Features & Use Cases

  • Requirements Engineering: Create Software Requirements Specifications with functional and non-functional requirements, use cases, and business rules.
  • User Story & Acceptance Criteria Writing: Write epics, user stories, and Given/When/Then acceptance criteria for TDD and QA verification.
  • Stakeholder & Scope Management: Run discovery interviews, apply MoSCoW prioritization, document change requests, and coordinate UAT with test scenarios and sign-off templates.
  • Templates & Quality Gates: Provide SRS structure, UAT test plans, weekly status reporting, and measurable success metrics for clear delivery contracts.

Quick Start

Ask the Amazon Business Analyst to run a discovery and produce an SRS, user stories with Given/When/Then acceptance criteria, and a prioritized MoSCoW backlog for the requested feature.

Frequently Asked Questions about business-analysis

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

FAQPage Schema
How do I turn vague stakeholder needs into testable software requirements?

To turn vague needs into testable software requirements, you gather stakeholder inputs during discovery workshops and translate them into structured SRS documents containing functional, non-functional, and measurable success metrics.

What is the best way to write user stories with Given/When/Then acceptance criteria?

Writing user stories with Given/When/Then acceptance criteria involves decomposing epics into actionable backlog items and defining specific test conditions to ensure clear QA verification and test-driven development alignment.

How do I apply MoSCoW prioritization to manage project scope?

Applying MoSCoW prioritization categorizes backlog items into Must-have, Should-have, Could-have, and Won't-have buckets, enabling teams to document change requests and control scope creep during sprint planning.

How do I create a UAT plan with test scenarios and sign-off templates?

Creating a UAT plan involves defining coordinated test scenarios based on structured acceptance criteria, executing user acceptance testing, and utilizing sign-off templates to establish clear delivery contracts.

Can I use this for backlog grooming and sprint planning?

Yes, you can use this during backlog grooming and sprint planning to transform ambiguous stakeholder inputs into clear, measurable, and prioritized requirements, ensuring engineering teams build the correct product with minimal rework.