ba-project-factory
julijakvetna/ba-project-factory
A complete Business Analyst lifecycle skill — 24 structured prompts for enterprise software delivery
Instalação
npx convez-ai julijakvetna/ba-project-factory1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
README
A tradução para o português deste README ainda está na fila.
BA Project Factory
A complete Business Analyst lifecycle skill for enterprise software delivery — 24 structured prompts covering every BA activity from project initiation to release.
What is this?
BA Project Factory is an agent skill that turns any LLM into a Senior Business Analyst co-pilot. It provides 24 structured, interconnected prompts covering the full software delivery lifecycle — from the first stakeholder conversation to release notes and training materials.
Each prompt is:
- Interactive — follows a generate → review → approve → store flow, never saves without user confirmation
- On-demand — works with whatever information is currently available, never blocks on missing docs
- Interconnected — flags which other prompts need updating when something changes
- Output-ready — produces Confluence-compatible markdown, Jira-ready user stories, and Figma-ready wireframe specs
Who is it for?
- Business Analysts who want consistent, high-quality artifact production
- Product Managers who need structured BA support without a dedicated BA resource
- Delivery Leads managing complex enterprise projects who want a single source of truth across all BA artifacts
- Consultants who need to onboard quickly and produce client-ready outputs fast
Install
Option 1 — Install as a skill (Claude / Cowork)
- Download
ba-project-factory.skill - Open Claude desktop (Cowork mode)
- Go to Settings → Skills → Install from file
- Select the downloaded
.skillfile
Once installed, the skill activates automatically when you describe any BA activity.
Option 2 — Use prompts directly (any LLM)
- Browse the
references/folder - Open the prompt file for the activity you need
- Copy the full content and paste it into your LLM of choice
- The LLM will guide you through the rest interactively
How to use
Once the skill is installed, just describe what you need:
"I need to document the current state process for the order management system"
"Help me write user stories for the approval workflow Epic"
"We just had a requirements workshop — here's the transcript, extract the action items"
The skill identifies the right prompt and runs it interactively, asking for your inputs and producing structured outputs ready to paste into Confluence, Jira, or Figma.
If you're unsure where to start, the skill will ask:
- What phase is the project in?
- What artifact do you most urgently need?
- What information do you already have?
The 24 Prompts
Initiation
| # | Prompt | What it produces |
|---|---|---|
| 01 | Project Vision Synthesis | Problem statement, objectives, scope, success metrics, assumptions, constraints |
| 02 | Stakeholder & End User Register | Full stakeholder register with roles, influence, communication strategy |
Discovery
| # | Prompt | What it produces |
|---|---|---|
| 03 | As-Is Process Analysis | Current state documentation from any source (Confluence, Jira, transcripts, user knowledge) |
| 04 | To-Be Process Design | Future state process with change impact analysis |
| 05 | Gap Analysis | Structured gaps between current and future state, categorised and prioritised |
Planning
| # | Prompt | What it produces |
|---|---|---|
| 06 | Delivery Map Generation | Epic-to-phase mapping with Confluence table + Mermaid diagram |
| 07 | Backlog Generation | Initial backlog from any available inputs with coverage analysis |
Delivery
| # | Prompt | What it produces |
|---|---|---|
| 08 | Backlog Item Refinement | Epics, User Stories, Acceptance Criteria, FRs, NFRs — new or refined |
| 09 | BPMN Process Modeling | Mermaid BPMN diagrams with swim lanes and process annotation tables |
| 10 | Low-Fidelity Mockups & Wireframes | Figma-ready component specifications with screen flow diagram |
| 11 | Consolidated Validation Questions | Deduplicated VQ register across all artifacts with stakeholder meeting agenda |
| 12 | Consolidated Requirements Register | Master FR and NFR register with conflict detection and coverage analysis |
| 13 | Requirements Traceability Matrix | Source → Requirement → Story → AC → Test Case → Status traceability |
| 14 | Change Request Impact Analysis | Full CR impact across scope, requirements, timeline, testing, risk |
Testing
| # | Prompt | What it produces |
|---|---|---|
| 15 | Test Plan Generation | Structured test cases with preconditions, steps, test data, pass/fail criteria |
| 16 | UAT Scenario Design | Business-language UAT scenarios with execution plan and issue log template |
Release
| # | Prompt | What it produces |
|---|---|---|
| 17 | Demo Scenarios | Audience-tailored demo scripts with wow moments and contingency plans |
| 18 | User Instructions & FAQ | Task-oriented how-to guides and categorised FAQ |
| 19 | Release Notes Generation | User-facing release notes across all standard sections |
| 20 | User Training Materials | Structured learning program with exercises and quick reference card |
Cross-cutting — use at any time
| # | Prompt | What it produces |
|---|---|---|
| 21 | Context Guardian | Consistency check across Vision, Requirements, Backlog, Dependencies — verdict table |
| 22 | Sprint Ceremony Support | Agendas, talking points, and output templates for Grooming, Planning, Retrospective |
| 23 | RAID Log | Living register of Risks, Assumptions, Issues, Dependencies with health summary |
| 24 | Meeting Transcript Analysis | Structured extraction of decisions, actions, requirements signals, risks from any meeting |
Design principles
Living documents — every prompt checks for an existing version before creating a new one. It updates, extends, or flags obsolete content rather than duplicating.
Source traceability — As-Is analysis and requirements capture work with fragmented sources (multiple Confluence pages, Jira stories, interview notes). Every entry traces back to its origin.
Cross-artifact awareness — after each activity, the prompt flags which other artifacts may need updating and which prompt to use.
No blocking on missing information — prompts adapt to what's available. A gap analysis can run without a complete To-Be document. A backlog can start from a single transcript.
Deduplication by default — registers (RAID Log, Validation Questions, Requirements) always check existing entries before adding new ones.
Repository structure
ba-project-factory/
├── SKILL.md # Skill entry point — routing logic and core principles
├── README.md # This file
├── LICENSE # MIT License
└── references/ # The 24 BA prompts
├── Prompt_01_Project_Vision_Synthesis.md
├── Prompt_02_Stakeholder_End_User_Register.md
├── Prompt_03_As_Is_Process_Analysis.md
├── Prompt_04_To_Be_Process_Design.md
├── Prompt_05_Gap_Analysis.md
├── Prompt_06_Delivery_Map_Generation.md
├── Prompt_07_Backlog_Generation.md
├── Prompt_08_Backlog_Item_Refinement.md
├── Prompt_09_BPMN_Process_Modeling.md
├── Prompt_10_Low_Fidelity_Mockups_Wireframes.md
├── Prompt_11_Consolidated_Validation_Questions.md
├── Prompt_12_Consolidated_Requirements_Register.md
├── Prompt_13_Requirements_Traceability_Matrix.md
├── Prompt_14_Change_Request_Impact_Analysis.md
├── Prompt_15_Test_Plan_Generation.md
├── Prompt_16_UAT_Scenario_Design.md
├── Prompt_17_Demo_Scenarios.md
├── Prompt_18_User_Instructions_FAQ.md
├── Prompt_19_Release_Notes_Generation.md
├── Prompt_20_User_Training_Materials.md
├── Prompt_21_Context_Guardian_Consistency_Check.md
├── Prompt_22_Sprint_Ceremony_Support.md
├── Prompt_23_RAID_Log.md
└── Prompt_24_Meeting_Transcript_Analysis.md
Contributing
Contributions are welcome. If you have improvements to existing prompts or new BA process prompts to add:
- Fork the repository
- Create a branch:
git checkout -b prompt/your-prompt-name - Follow the existing prompt structure (Objective → Prompt → Steps → Important Rules → Output & Storage Instructions)
- Open a pull request with a description of what the prompt covers and which lifecycle phase it belongs to
License
MIT License — see LICENSE for details.
Free to use, modify, and distribute. Attribution appreciated but not required.
Author
Built by a Business Analyst team to solve real delivery problems. Designed for enterprise software projects but applicable to any structured delivery context.
If this skill saves you time, consider starring the repo or sharing it with your team.