business-analyst

Formalize business requirements with traceability, KPIs, and acceptance criteria.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/united-software-platform/req-control --skill business-analyst-united-software-platform
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-analyst
Source: https://github.com/united-software-platform/req-control/tree/main/.claude/skills/business-analyst
Command: npx skills add https://github.com/united-software-platform/req-control --skill business-analyst-united-software-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Этот навык помогает систематизировать сбор требований и анализ бизнес-процессов, устраняя разночтения между целями бизнеса и технической реализацией. Он обеспечивает трассируемость требований, моделирование процессов, управление стейкхолдерами и измеримую бизнес-ценность.

Core Features & Use Cases

  • Требования и трассируемость: сбор, документирование и поддержание прослеживаемости требований от идеи до реализации.
  • Моделирование процессов: картирование текущих процессов, выявление узких мест и проектирование целевого состояния.
  • Управление изменениями: планирование коммуникаций, обучение пользователей и внедрение.
  • Использование данных: определение KPI, создание отчетов и визуализация для принятия решений.

Quick Start

Проанализируйте бизнес-контекст, идентифицируйте стейкхолдеров и текущие процессы, затем сформируйте упорядоченный бэклог требований для верификации.

Frequently Asked Questions about business-analyst

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

FAQPage Schema
How do I elicit and document business requirements for technical delivery?

To elicit business requirements, analyze the business context, identify stakeholders and current processes, then formalize an ordered requirements backlog with traceability from idea to implementation for technical delivery verification.

What is requirements traceability and when do I need it for process mapping?

Requirements traceability links business needs to technical outcomes across process mapping. You need it during cross-functional process analysis to ensure measurable value, governance, and that stakeholder scope aligns with delivery.

How do I define KPIs and acceptance criteria for business process analysis?

Define KPIs and acceptance criteria by capturing scope and measurable value during requirements elicitation, ensuring that business process analysis yields governance metrics and verifiable outcomes for stakeholders.

Can I use business analysis for cross-functional change management and stakeholder alignment?

Yes, business analysis applies to cross-functional change management by planning communications, mapping current processes to target states, and aligning stakeholders with technical delivery through structured requirements governance.

What's the best way to map current processes and identify bottlenecks for target state design?

Map current processes by analyzing cross-functional workflows, identifying bottlenecks, and formalizing target state designs that align stakeholder needs with technical delivery and measurable business value.

Why do my business goals and technical implementation outcomes misalign during delivery?

Business goals and technical implementation misalign when requirements lack traceability and formal scope capture, which business analysis resolves by structuring stakeholder workshops and defining acceptance criteria for governance.