ba-workflow

Name: ba-workflow
Author: omnigentx

31stars13forks

How to install ba-workflow?

omnigentx/jarvis/ba-workflow

$npx -y skills add omnigentx/jarvis --skill ba-workflow

Installs into the current project.

Summary

BA workflow for requirements gathering, BRD creation, and acceptance criteria. Use when BA needs to analyze project scope or validate deliverables.

Files · 1

View on GitHub

SKILL.md

1	# BA Workflow
2
3	## Your Process
4
5	1. Analyze brief → understand business goals, stakeholders, constraints
6	2. Write BRD → structured Business Requirements Document
7	3. Define acceptance criteria → Given/When/Then for each requirement
8	4. Review deliverables → verify Dev's implementation matches requirements
9
10	## Output Rule — MANDATORY
11
12	\| Deliverable \| Destination \| Tool \|
13	\|------------\|-------------\|------\|
14	\| BRD \| Confluence page \| `confluence_create_page` \|
15	\| Each requirement \| Jira Story \| `jira_create_issue` with acceptance criteria \|
16	\| Workspace files \| Temporary drafts ONLY \| `write_file` \|
17
18	## BRD Structure
19
20	Publish to Confluence with these sections:
21	- Executive Summary
22	- Functional Requirements (table: ID, Description, Priority, Acceptance Criteria)
23	- Non-Functional Requirements
24	- Open Questions
25
26	After publishing to Confluence, create Jira stories for each requirement.
27
28	## Analysis Tasks
29
30	When the project is ANALYSIS type (not building software):
31	- Read repos/docs, create comparison matrix, identify gaps
32	- Each finding = one Jira story with: Summary, Description, Priority, Acceptance Criteria
33	- Long-form analysis = Confluence page
34	- DO NOT write standalone .md files as final deliverables
35
36	## Quality Checks
37
38	Before delivering:
39	- Is each requirement testable and unambiguous?
40	- Are requirements complete (no gaps)?
41	- Is the scope clearly bounded?
42
43	## Visualizing user flows
44
45	When a requirement involves a multi-step user interaction or branching logic,
46	attach a Mermaid diagram to the BRD section — Confluence and the Jarvis
47	dashboard both render it.
48
49	```mermaid
50	flowchart TD
51	Start([User opens checkout]) --> A{Logged in?}
52	A -- No --> B[Redirect to login]
53	A -- Yes --> C[Show cart]
54	C --> D{Items in stock?}
55	D -- No --> E[Show out-of-stock warning]
56	D -- Yes --> F[Proceed to payment]
57	```
58
59	Use it sparingly: if the requirement is one paragraph, skip the diagram.
60
61	## References
62
63	\| Topic \| File \|
64	\|-------\|------\|
65	\| Meeting join/speak protocol \| [MEETING_PROTOCOL.md](references/MEETING_PROTOCOL.md) \|
66	\| Jira & Confluence conventions \| [JIRA_TRACKING.md](references/JIRA_TRACKING.md) \|

People who liked this also viewed

6 picks

Type

ba-workflow

31stars13forks

View on GitHub

How to install ba-workflow?

omnigentx/jarvis/ba-workflow

$npx -y skills add omnigentx/jarvis --skill ba-workflow

Installs into the current project.

Summary

BA workflow for requirements gathering, BRD creation, and acceptance criteria. Use when BA needs to analyze project scope or validate deliverables.

Files · 1

View on GitHub

SKILL.md

1	# BA Workflow
2
3	## Your Process
4
5	1. Analyze brief → understand business goals, stakeholders, constraints
6	2. Write BRD → structured Business Requirements Document
7	3. Define acceptance criteria → Given/When/Then for each requirement
8	4. Review deliverables → verify Dev's implementation matches requirements
9
10	## Output Rule — MANDATORY
11
12	\| Deliverable \| Destination \| Tool \|
13	\|------------\|-------------\|------\|
14	\| BRD \| Confluence page \| `confluence_create_page` \|
15	\| Each requirement \| Jira Story \| `jira_create_issue` with acceptance criteria \|
16	\| Workspace files \| Temporary drafts ONLY \| `write_file` \|
17
18	## BRD Structure
19
20	Publish to Confluence with these sections:
21	- Executive Summary
22	- Functional Requirements (table: ID, Description, Priority, Acceptance Criteria)
23	- Non-Functional Requirements
24	- Open Questions
25
26	After publishing to Confluence, create Jira stories for each requirement.
27
28	## Analysis Tasks
29
30	When the project is ANALYSIS type (not building software):
31	- Read repos/docs, create comparison matrix, identify gaps
32	- Each finding = one Jira story with: Summary, Description, Priority, Acceptance Criteria
33	- Long-form analysis = Confluence page
34	- DO NOT write standalone .md files as final deliverables
35
36	## Quality Checks
37
38	Before delivering:
39	- Is each requirement testable and unambiguous?
40	- Are requirements complete (no gaps)?
41	- Is the scope clearly bounded?
42
43	## Visualizing user flows
44
45	When a requirement involves a multi-step user interaction or branching logic,
46	attach a Mermaid diagram to the BRD section — Confluence and the Jarvis
47	dashboard both render it.
48
49	```mermaid
50	flowchart TD
51	Start([User opens checkout]) --> A{Logged in?}
52	A -- No --> B[Redirect to login]
53	A -- Yes --> C[Show cart]
54	C --> D{Items in stock?}
55	D -- No --> E[Show out-of-stock warning]
56	D -- Yes --> F[Proceed to payment]
57	```
58
59	Use it sparingly: if the requirement is one paragraph, skip the diagram.
60
61	## References
62
63	\| Topic \| File \|
64	\|-------\|------\|
65	\| Meeting join/speak protocol \| [MEETING_PROTOCOL.md](references/MEETING_PROTOCOL.md) \|
66	\| Jira & Confluence conventions \| [JIRA_TRACKING.md](references/JIRA_TRACKING.md) \|

People who liked this also viewed

6 picks

Type