Skillshub quality-engineering-business-analysis

Requirement investigation protocol: atomic AC decomposition, actor/permission matrix, platform parity audit, truth table verification, and edge case discovery. ALWAYS consult before writing test cases or impact analysis — especially for stories with multi-condition AC, feature toggles, market variants (VN/MY/SG), or undefined platform behavior. (triggers: **/user_story.md, acceptance criteria, AC, business rules, jira story, toggle, market)

install

source · Clone the upstream repo

git clone https://github.com/ComeOnOliver/skillshub

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/ComeOnOliver/skillshub "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/HoangNguyen0403/agent-skills-standard/quality-engineering-business-analysis" ~/.claude/skills/comeonoliver-skillshub-quality-engineering-business-analysis && rm -rf "$T"

manifest: skills/HoangNguyen0403/agent-skills-standard/quality-engineering-business-analysis/SKILL.md

source content

Business Analysis Standards (Deep Analysis)

Priority: P0 (CRITICAL)

1. Deep Investigation Protocol

Atomic AC Decomposition: Split Acceptance Criteria (AC) into 1-Condition logic units (e.g., "User can X and Y" -> "User can X", "User can Y").
Variable Identification: Extract all Feature Toggles, Market Rules (VN/MY/SG), and User Roles.
Platform Parity: Verify if logic applies to both Web and Mobile; Flag divergent behavior early.
Truth Table Verification: Map complex multi-condition logic to a Logic Truth Table.

2. Dynamic Actor & Permission Mapping

Identify all Actors (e.g.,
```
Customer
```
,
```
Sales Rep
```
,
```
Admin
```
).
Use an Actor/Permission Matrix to map specific constraints per Actor.
Permissions Patterns

3. Edge Case & Boundary Analysis

State Validation: Verify behavior across all entity (e.g.,
```
Active
```
,
```
Suspended
```
) and network states.
Boundary Detection: Analyze currency, date, and count limits.
Negative Testing: Identify flows for Unauthorized Access, Invalid Input, and Null-safety.

4. Anti-Patterns

No Surface Reading: investigate the implications, don't just restate.
No Assumption: Flag undefined states (e.g., Offline) as P0 blockers.
No Loose Mapping: Ensure AC aligns 100% with Technical Impact notes.