ba

Document business requirements into BRD, FRS, and RTM artifacts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/truongnat/agentic-sdlc --skill ba-truongnat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ba
Source: https://github.com/truongnat/agentic-sdlc/tree/main/agentic_sdlc/defaults/skills/ba
Command: npx skills add https://github.com/truongnat/agentic-sdlc --skill ba-truongnat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Business analysts translate business needs into clear, testable requirements, ensuring alignment between stakeholders and technical teams.

Core Features & Use Cases

  • Requirements elicitation and documentation (BRD, FRS)
  • Requirements validation, change management, and traceability (RTM)
  • Creating well-structured user stories with acceptance criteria and linking them to business goals
  • Handoff governance to design and implementation teams across sprint cycles

Quick Start

Initiate a requirements-gathering sprint, draft BRD and FRs, and generate linked user stories with acceptance criteria.

Frequently Asked Questions about ba

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

FAQPage Schema
How do I document business requirements to align stakeholders with technical delivery?▼

Documenting business requirements involves eliciting needs and creating artifacts like a BRD and FRS to align stakeholders with technical delivery. This ensures clear, testable requirements that bridge the gap between business goals and implementation.

What is the best way to write user stories with acceptance criteria for sprint planning?▼

Writing user stories with acceptance criteria requires linking them to validated business goals within a sprint context. This approach ensures that development teams have clear, testable conditions for feature completion and technical delivery.

How do I manage requirements traceability and change across sprint cycles?▼

Managing requirements traceability involves using a Requirements Traceability Matrix (RTM) to track changes and validate requirements across sprint cycles. This maintains governance during handoffs to design and implementation teams.

Can I use this for requirements elicitation and creating a BRD and FRS?▼

Yes, requirements elicitation is a core function that enables the creation of a Business Requirements Document (BRD) and Functional Requirements Specification (FRS). It captures business needs and translates them into precise technical specifications.

What is the difference between a BRD and an FRS in business analysis?▼

In business analysis, a BRD defines high-level business needs and goals, while an FRS details the specific functional requirements for technical implementation. Both artifacts are essential for aligning stakeholders and guiding development.

Why do I need governance guidance for handoffs to design and implementation teams?▼

Governance guidance for handoffs is necessary to ensure that validated requirements are accurately transferred to design and implementation teams without loss of context. It maintains alignment between business goals and technical delivery across sprints.