skills.rest
truongnat
truongnatCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

business-analysis-pro

Translate business needs into structured BRD/FRD requirements with traceability.

1|Updated Jul 3, 2026
Search Tags:#requirements#traceability#analyze#frd#gap-analysis#decision-log#brd
One-click install
npx skills add https://github.com/truongnat/skills --skill business-analysis-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: business-analysis-pro
Source: https://github.com/truongnat/skills/tree/main/skills/business-analysis-pro
Command: npx skills add https://github.com/truongnat/skills --skill business-analysis-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams elicit and structure business requirements, produce auditable BRD/FRD artifacts, and preserve explicit reasoning and decisions with traceability.

Core Features & Use Cases

  • Elicitation, as-is / to-be analysis, and gap identification to define clear requirements.
  • MoSCoW prioritization, risk/assumption logging, and decision records to support governance.
  • Production of executive-ready reports and artifacts with traceability links to sources.

Quick Start

Elicit stakeholders, map the current state, define the target state, and generate a BRD-ready analysis with an explicit decision log.

Frequently Asked Questions about business-analysis-pro

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

FAQPage Schema
How do I create a BRD-ready analysis with traceability from stakeholder input?▼

Produce auditable BRD and FRD artifacts by eliciting stakeholders, mapping current states, defining target states, and generating gap analysis with explicit assumptions and acceptance criteria.

What is the best way to structure requirements traceability for gap analysis?▼

Structure requirements traceability by mapping elicited business needs to source documents, producing executable BRD and FRD artifacts that bridge as-is and to-be states.

How do I document assumptions and acceptance criteria in a decision log?▼

Apply MoSCoW prioritization and risk logging during BRD development to preserve explicit reasoning, assumptions, and acceptance criteria in an auditable decision log.

Can I generate both executive-ready reports and executable FR artifacts from stakeholder mapping?▼

Yes, the Skill produces executive-ready reports and executable FR artifacts by combining stakeholder mapping, gap analysis, and decision records with source traceability links.

When do I need to apply as-is and to-be analysis for business requirements?▼

Apply as-is and to-be analysis during BRD and FRD development to identify gaps, define clear requirements, and translate business needs into structured, executable artifacts.

Related Skills

Explore More Product & Management Skills→
qa-amanqa-aman
19

requirements-elicitation

Facilitate structured stakeholder requirement elicitation across interviews, workshops, observation, and document analysis.

Community
Advanced
shiroginshirogin
1

doc-chain

Orchestrate BRD, PRD, FRD, and SOW documentation with traceability gates.

Community
Intermediate
CrashBytesCrashBytes
6

product-owner

Manage product backlogs, write user stories, and prioritize with RICE.

Community
Advanced
intelligentcode-aiintelligentcode-ai
35

requirements-engineer

Capture and formalize stakeholder needs into testable requirements with traceability.

Official
Basic