skills.rest
manhthien2005
manhthien2005COMMUNITY
Explore all skills by this author →
WebsiteGitHub

business-analyst

Extracts complexity signals and dependencies from Use Case documents for story point estimation.

Updated Mar 3, 2026
Search Tags:#sprint planning#requirements analysis#story points#business analyst#dependency mapping#complexity estimation#use case analysis
One-click install
npx skills add https://github.com/manhthien2005/PM_REVIEW --skill business-analyst-manhthien2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: business-analyst
Source: https://github.com/manhthien2005/PM_REVIEW/tree/main/tooling/.windsurf-template/shared/skills/task-manager/skills/business-analyst
Command: npx skills add https://github.com/manhthien2005/PM_REVIEW --skill business-analyst-manhthien2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Estimating effort for software requirements is often subjective and inconsistent. This Skill turns Use Case documents into structured complexity data so teams can estimate Story Points and map dependencies systematically. ## Core Features & Use Cases - Complexity Signal Extraction: Parses UC files to count main flow steps, alternative flows, business rules, data fields, external integrations, and NFR requirements. - Story Point Classification: Maps extracted signals to Simple (1-2 SP), Medium (3-5 SP), or Complex (8-13 SP) buckets using a defined threshold table. - Dependency Identification: Detects <<include>>, <<extend>>, preconditions, and shared data tables to surface hard and soft dependencies between UCs. - Use Case: Given a folder of UC specification documents, produce a summary table listing each UC's complexity, estimated story points, dependencies, and key signals for sprint planning. ## Quick Start Analyze the Use Case documents in this project and produce a complexity and story point estimation table with dependencies.

Frequently Asked Questions about business-analyst

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

FAQPage Schema
How do I estimate story points from Use Case documents?▼

Estimate story points by counting complexity signals in each UC: main flow steps, alternative flows, business rules, data fields, and external integrations. Map these counts to Simple (1-2 SP), Medium (3-5 SP), or Complex (8-13 SP) using threshold tables.

How to identify dependencies between use cases?▼

Identify UC dependencies by scanning for <<include>> relationships (hard dependencies), <<extend>> relationships (soft dependencies), preconditions sections, and shared data tables between use cases. Each pattern indicates a different dependency strength.

What factors affect use case complexity estimation?▼

Use case complexity is driven by main flow step count, number of alternative flows, business rules, data fields requiring validation, external system integrations, and non-functional requirements like performance or security that add testing overhead.

Can this analysis handle non-English requirements documents?▼

Yes, the dependency detection recognizes patterns like "Tiền điều kiện" (Vietnamese for preconditions) alongside English terms. The structural signals such as step counts and include/extend relationships are language-independent.

What are the limitations of signal-based story point estimation?▼

Signal-based estimation relies on document completeness; poorly written UCs with missing flows or rules will be underestimated. It also cannot account for team velocity, technical debt, or unfamiliar technology stacks.

Related Skills

Explore More Product & Management Skills→
sirius-cc-wusirius-cc-wu
3

use-case

Draft use-case specifications from user stories using a structured template.

Community
Intermediate
camilooscargbaptistacamilooscargbaptista
7

sprint-planning

Convert backlog items into prioritized user stories with acceptance criteria and sprint backlog.

Community
Advanced
kay6198835kay6198835

estimate

Analyze task complexity, dependencies, velocity history, and risk factors to generate structured effort estimates with confidence levels.

Community
Advanced
supercent-iosupercent-io

task-estimation

Estimate software development tasks using story points, t-shirt sizing, and planning poker.

Official
Intermediate