convez.ai
Skill
julijakvetna

ba-project-factory

julijakvetna/ba-project-factory

Ver no GitHub
InicialPluginScore · de 0 a 100

A complete Business Analyst lifecycle skill — 24 structured prompts for enterprise software delivery

Instalação

$npx convez-ai julijakvetna/ba-project-factory

1 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

Estrelas
0
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 5 meses
Versão
v1.0.0
Issues abertas
0
Contribuidores
1

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.

License: MIT Skill Format Prompts Compatible


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)

  1. Download ba-project-factory.skill
  2. Open Claude desktop (Cowork mode)
  3. Go to Settings → Skills → Install from file
  4. Select the downloaded .skill file

Once installed, the skill activates automatically when you describe any BA activity.

Option 2 — Use prompts directly (any LLM)

  1. Browse the references/ folder
  2. Open the prompt file for the activity you need
  3. Copy the full content and paste it into your LLM of choice
  4. 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:

  1. What phase is the project in?
  2. What artifact do you most urgently need?
  3. What information do you already have?

The 24 Prompts

Initiation

#PromptWhat it produces
01Project Vision SynthesisProblem statement, objectives, scope, success metrics, assumptions, constraints
02Stakeholder & End User RegisterFull stakeholder register with roles, influence, communication strategy

Discovery

#PromptWhat it produces
03As-Is Process AnalysisCurrent state documentation from any source (Confluence, Jira, transcripts, user knowledge)
04To-Be Process DesignFuture state process with change impact analysis
05Gap AnalysisStructured gaps between current and future state, categorised and prioritised

Planning

#PromptWhat it produces
06Delivery Map GenerationEpic-to-phase mapping with Confluence table + Mermaid diagram
07Backlog GenerationInitial backlog from any available inputs with coverage analysis

Delivery

#PromptWhat it produces
08Backlog Item RefinementEpics, User Stories, Acceptance Criteria, FRs, NFRs — new or refined
09BPMN Process ModelingMermaid BPMN diagrams with swim lanes and process annotation tables
10Low-Fidelity Mockups & WireframesFigma-ready component specifications with screen flow diagram
11Consolidated Validation QuestionsDeduplicated VQ register across all artifacts with stakeholder meeting agenda
12Consolidated Requirements RegisterMaster FR and NFR register with conflict detection and coverage analysis
13Requirements Traceability MatrixSource → Requirement → Story → AC → Test Case → Status traceability
14Change Request Impact AnalysisFull CR impact across scope, requirements, timeline, testing, risk

Testing

#PromptWhat it produces
15Test Plan GenerationStructured test cases with preconditions, steps, test data, pass/fail criteria
16UAT Scenario DesignBusiness-language UAT scenarios with execution plan and issue log template

Release

#PromptWhat it produces
17Demo ScenariosAudience-tailored demo scripts with wow moments and contingency plans
18User Instructions & FAQTask-oriented how-to guides and categorised FAQ
19Release Notes GenerationUser-facing release notes across all standard sections
20User Training MaterialsStructured learning program with exercises and quick reference card

Cross-cutting — use at any time

#PromptWhat it produces
21Context GuardianConsistency check across Vision, Requirements, Backlog, Dependencies — verdict table
22Sprint Ceremony SupportAgendas, talking points, and output templates for Grooming, Planning, Retrospective
23RAID LogLiving register of Risks, Assumptions, Issues, Dependencies with health summary
24Meeting Transcript AnalysisStructured 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:

  1. Fork the repository
  2. Create a branch: git checkout -b prompt/your-prompt-name
  3. Follow the existing prompt structure (Objective → Prompt → Steps → Important Rules → Output & Storage Instructions)
  4. 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.

Ver o original no GitHub

Bom para

Relacionados