---
title: "Introduction"
description: "Business analysis practices, Jira story standards, and Cursor Agent Skills that help teams write consistent, testable user stories for Propay delivery."
canonical_url: "https://handbook.propay.co.za/analysis/introduction"
---
# Introduction

> Business analysis practices, Jira story standards, and Cursor Agent Skills that help teams write consistent, testable user stories for Propay delivery.

## Purpose

The **Analysis** section documents how we capture requirements in Jira, align stories with testing and dependencies, and use **Cursor Agent Skills** so drafting and refinement stay consistent across teams.

## What you will find here

- **User story layout** — Human-first Jira story structure (flow-sized scope, Gherkin summary, tech tasks, business rules, test cases) with section helptext and a quick-copy block.
- **Jira user story skill** — Installable Cursor skill (`propay-jira-user-story`) with the canonical story template, acceptance criteria patterns, and references for AI-assisted drafting.
- **Jira MCP in Cursor** — Connect Cursor to Jira via Model Context Protocol so the agent can use live issue context when refining stories (setup pattern, credentials, security).
- **Figma MCP in Cursor** — Connect Cursor to Figma via MCP so design context can inform story drafting without pasting everything by hand.
- **BA code-to-BPMN skills** — Install and use Cursor skills and MCP servers to reverse-engineer existing Laravel code into BPMN 2.0 process models, business rules, user flows, and draw.io diagrams.

## Ownership

Updates to analysis content and the bundled skill go through the same [handbook](https://github.com/PropaySystems/handbook) pull-request process as the rest of this site. Propose changes in a focused PR; for the skill specifically, update `analysis/propay-jira-user-story/` and note the version bump in its `CHANGELOG.md`.

## Related handbook areas

- [Testing](https://handbook.propay.co.za/laravel/tests) — how acceptance criteria tie to automated tests.
- [Git](https://handbook.propay.co.za/git/introduction) — branch naming and delivery workflow.
- [Developer guidelines](https://handbook.propay.co.za/guides/introduction) — expectations for clarity and responsibility in specs.


## Sitemap

See the full [sitemap](https://handbook.propay.co.za/sitemap.md) for all pages.
