BSA Agent (Business Systems Analyst)

Analyze business requirements and translate them into testable technical specifications.

1|Updated Jul 8, 2016
One-click install
npx skills add https://github.com/oehm-smith/linux-env --skill bsa-agent-business-systems-analyst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: BSA Agent (Business Systems Analyst)
Source: https://github.com/oehm-smith/linux-env/tree/main/HOME/.claude/skills/lifecycle/requirements/requirements_analysis
Command: npx skills add https://github.com/oehm-smith/linux-env --skill bsa-agent-business-systems-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates business language into technical requirements to ensure nothing is lost in translation between stakeholders and engineering teams.

Core Features & Use Cases

  • Analyze tickets, feature requests, user stories, and ambiguous requirements to extract needs and constraints.
  • Identify stakeholders, risks, dependencies, and acceptance criteria to guide downstream design and validation.
  • Document technical requirements in a clear, testable format that can be handed off to software engineers.

Quick Start

Submit a clear business requirement or ticket and the BSA Agent will translate it into precise technical specifications.

Frequently Asked Questions about BSA Agent (Business Systems Analyst)

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

FAQPage Schema
How do I translate business requirements into testable technical specifications?

To translate business requirements into testable technical specifications, submit a clear business need or ticket. The BSA Agent analyzes the input to extract constraints, data requirements, acceptance criteria, and risks for engineering handoff.

What is the best way to analyze ambiguous user stories for engineering teams?

Analyzing ambiguous user stories requires extracting stakeholder needs and mapping dependencies. The BSA Agent processes feature requests to identify constraints, document data requirements, and generate clear technical specs for downstream design.

Can I use this to identify stakeholders and risks from a feature request?

Yes, you can identify stakeholders and risks from a feature request. The BSA Agent performs stakeholder mapping and risk analysis on submitted requirements to ensure alignment between business stakeholders and engineering teams.

Does the BSA Agent work with standard tickets and user stories?

The BSA Agent works with standard tickets, feature requests, and user stories. It analyzes these inputs to document technical requirements, acceptance criteria, and dependencies in a clear format that can be handed off to software engineers.

What should I include in a ticket for accurate requirements analysis?

For accurate requirements analysis, include the business language and needs in your ticket. The BSA Agent translates this input into precise technical specifications, documenting stakeholder needs, constraints, data requirements, and potential risks.

When do I need to map dependencies and acceptance criteria for a technical spec?

You need to map dependencies and acceptance criteria when preparing technical specs for downstream validation. The BSA Agent extracts these elements from business requirements to guide design and ensure alignment between stakeholders and engineering.