quality-engineering-business-analysis

Automate business analysis and user story creation with AC decomposition and truth tables.

Updated Jun 25, 2026

Search Tags:#product management #QA #acceptance criteria #business analysis #user story

Ready to run

npx skills add https://github.com/VSF-QC-TTS/vf-qc-copilot --skill quality-engineering-business-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quality-engineering-business-analysis
Source: https://github.com/VSF-QC-TTS/vf-qc-copilot/tree/main/.agents/skills/quality-engineering/quality-engineering-business-analysis
Command: npx skills add https://github.com/VSF-QC-TTS/vf-qc-copilot --skill quality-engineering-business-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenges of creating and reviewing high-quality user stories by providing a structured framework for analysis and story authoring, ensuring clarity and compliance with best practices.

Core Features & Use Cases

Atomic Acceptance Criteria (AC) Decomposition: Break down complex ACs into 1-Condition logic units for clarity.
Actor/Permission Matrix: Map constraints for each actor in the system.
Platform Parity Audit: Verify logic across Web and Mobile platforms.
Truth Table Verification: Map multi-condition logic to truth tables.
User Story Authoring Standards: Enforce story structure, scope, and tagging.

Quick Start

Analyze the requirements for your next user story using the quality-engineering-business-analysis skill.

Frequently Asked Questions about quality-engineering-business-analysis

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

FAQPage Schema

How do I decompose complex acceptance criteria into atomic logic units for user stories?▼

Atomic acceptance criteria decomposition breaks complex conditions into 1-condition logic units. This clarifies user story scope and ensures structured evaluation for QA professionals handling multi-condition logic or feature toggles.

What is the best way to verify multi-condition logic across Web and Mobile platforms?▼

Platform parity audit verifies logic consistency across Web and Mobile platforms. You map multi-condition logic to truth tables and use an actor/permission matrix to validate constraints, ensuring consistent behavior for market-specific requirements.

How does actor and permission matrix mapping work for business analysis?▼

Actor and permission matrix mapping identifies and maps constraints for each system actor. It enforces user story authoring standards by verifying scope, tagging, and permissions, which is critical for structured evaluation before development.

When do I need truth table verification for user story creation?▼

Truth table verification is needed when user stories contain complex acceptance criteria or feature toggles. It maps multi-condition logic to truth tables to validate expected outcomes, preventing ambiguous requirements in product management.

Can I enforce user story authoring standards for market-specific requirements?▼

User story authoring standards enforce story structure, scope, and tagging for market-specific requirements. The framework automates business analysis to ensure clarity and compliance with best practices for QA professionals and product managers.

Why use atomic AC decomposition for feature toggles in product management?▼

Atomic AC decomposition breaks feature toggles into 1-condition logic units to prevent scope ambiguity. It provides a structured framework for business analysis, ensuring high-quality user story creation and precise evaluation.