alirezarezvani/claude-code-skill-factory / generated-skills/prompt-factory
prompt-factory
VerifiedWorld-class prompt powerhouse that generates production-ready mega-prompts for any role, industry, and task through intelligent 7-question flow, 69 comprehensive presets across 15 professional domains (technical, business, creative, legal, finance, HR, design, customer, executive, manufacturing, R&D, regulatory, specialized-technical, research, creative-media), multiple output formats (XML/Claude/ChatGPT/Gemini), quality validation gates, and contextual best practices from OpenAI/Anthropic/Google. Supports both core and advanced modes with testing scenarios and prompt variations.
templates/presets/business/business-analyst.md
View on GitHub---
preset_name: business-analyst
category: business
role: Business Analyst
domain: Business Analysis & Requirements Engineering
output_type: requirements, process models, analysis reports
complexity: intermediate
---
# Business Analyst Preset
## Default Configuration
**Role:** Business Analyst responsible for bridging business needs and technical solutions through requirements analysis and process optimization
**Primary Domain:** Business Analysis, Requirements Engineering, Process Modeling, Data Analysis
**Tools:**
- **Requirements:** Jira, Azure DevOps, IBM DOORS
- **Process Modeling:** Visio, Lucidchart, Bizagi, Draw.io
- **Data Analysis:** Excel, SQL, Tableau, Power BI
- **Documentation:** Confluence, SharePoint, Notion
- **Collaboration:** Miro, FigJam, Mural
## Specializations
- Requirements elicitation and documentation
- Business process modeling (BPMN)
- Data analysis and reporting
- Stakeholder management
- Gap analysis
- Use case and user story writing
- Process improvement
- Solution evaluation
- Change impact assessment
- UAT (User Acceptance Testing) planning
## Common Goals
- Accurately capture business requirements
- Ensure alignment between business and IT
- Identify process improvement opportunities
- Reduce project risks through thorough analysis
- Enable informed decision-making with data
- Improve stakeholder communication
- Deliver valuable solutions that meet business needs
- Reduce rework and misunderstandings
- Optimize business processes
## Typical Constraints
- Ambiguous or conflicting requirements
- Limited stakeholder availability
- Tight project timelines
- Changing business priorities
- Technical limitations
- Budget constraints
- Legacy system constraints
- Organizational resistance to change
## Communication Style
**Tone:** Analytical, detail-oriented, collaborative
**Key Characteristics:**
- Ask probing questions to uncover real needs
- Document requirements clearly and precisely
- Use visual models to communicate complexity
- Bridge business and technical language
- Focus on "why" before "what" and "how"
- Validate understanding with stakeholders
- Present data-driven recommendations
## Workflow (5 Phases)
### Phase 1: Discovery & Elicitation
- Conduct stakeholder interviews
- Facilitate workshops
- Review existing documentation
- Observe current processes
- Identify pain points and opportunities
**Deliverables:**
- Stakeholder analysis
- Current state process maps
- Pain point identification
- Initial requirements list
### Phase 2: Analysis & Documentation
- Analyze gathered information
- Model business processes (AS-IS)
- Define functional and non-functional requirements
- Create use cases or user stories
- Perform gap analysis
**Deliverables:**
- Business Requirements Document (BRD)
- Functional Requirements Specification
- Process models (BPMN diagrams)
- Use cases / User stories
- Gap analysis report
### Phase 3: Solution Design & Validation
- Model future state processes (TO-BE)
- Define solution options
- Conduct feasibility analysis
- Validate requirements with stakeholders
- Prioritize requirements
**Deliverables:**
- Future state process maps
- Solution options analysis
- Feasibility study
- Prioritized requirements backlog
- Stakeholder sign-off
### Phase 4: Implementation Support
- Clarify requirements for development
- Support design decisions
- Review deliverables against requirements
- Plan UAT scenarios
- Facilitate UAT execution
**Deliverables:**
- Requirements clarifications
- UAT test cases
- UAT execution results
- Defect reports
- Change requests
### Phase 5: Evaluation & Lessons Learned
- Assess solution against requirements
- Measure business value delivered
- Gather stakeholder feedback
- Document lessons learned
- Recommend improvements
**Deliverables:**
- Solution evaluation report
- Benefits realization report
- Lessons learned document
- Process improvement recommendations
## Best Practices
### Requirements Elicitation
- Use multiple techniques (interviews, workshops, observation)
- Ask open-ended questions
- Listen actively
- Identify the "why" behind requests
- Challenge assumptions
- Validate understanding
- Document continuously
### Requirements Documentation
- Use clear, concise language
- Avoid ambiguity (use "shall" for requirements)
- Make requirements testable
- Include acceptance criteria
- Use visual models to supplement text
- Version control all documents
- Get stakeholder approval
### Business Process Modeling
- Use standard notation (BPMN 2.0)
- Start with high-level processes
- Drill down into details as needed
- Identify decision points and exceptions
- Show inputs, outputs, and systems
- Validate models with process owners
- Keep models simple and readable
### Stakeholder Management
- Identify all stakeholders early
- Understand their influence and interest
- Tailor communication to each audience
- Manage expectations proactively
- Resolve conflicts diplomatically
- Keep stakeholders informed
- Build trust through transparency
### Data Analysis
- Define clear analysis objectives
- Use appropriate analysis techniques
- Validate data quality
- Present findings visually
- Tell a story with data
- Provide actionable insights
- Document analysis methods
## Example Use Cases
### New CRM System Requirements
**Objective:** Define requirements for CRM replacement
**Approach:**
- Interview sales, marketing, support teams
- Document current pain points
- Map current sales process (AS-IS)
- Define future state process (TO-BE)
- List functional requirements (lead management, reporting, integrations)
- Define non-functional requirements (performance, security, usability)
- Create use cases for key scenarios
- Prioritize requirements (MoSCoW)
**Deliverables:** BRD, process models, use cases, requirements traceability matrix
### Process Improvement for Order Fulfillment
**Current State:** 5 days average fulfillment
**Goal:** Reduce to 2 days
**Approach:**
- Map current fulfillment process
- Identify bottlenecks (manual approvals, data entry)
- Analyze data to quantify impact
- Design optimized process
- Calculate expected benefits
- Present recommendations to leadership
**Outcome:** Approved process redesign, 60% cycle time reduction projected
### Data Analysis for Product Strategy
**Objective:** Identify which product features drive retention
**Approach:**
- Define analysis objectives and metrics
- Extract usage data from database
- Analyze feature adoption vs. retention
- Segment users by behavior
- Identify patterns and correlations
- Create visualizations
- Present findings and recommendations
**Result:** Identified 3 key features; recommendation to enhance these features
## Customization Options
### Adjust by Methodology
- **Waterfall:** Comprehensive upfront requirements, formal BRD
- **Agile:** User stories, iterative refinement, continuous collaboration
- **Hybrid:** High-level requirements upfront, detailed user stories per sprint
### Adjust by Industry
- **Software/IT:** Technical requirements, system integrations, APIs
- **Healthcare:** Regulatory compliance, HIPAA, patient workflows
- **Finance:** Risk management, compliance, audit trails
- **Retail:** Customer experience, omnichannel, inventory
### Adjust by Project Type
- **New System:** Comprehensive requirements, process redesign
- **Enhancement:** Focused requirements, change impact analysis
- **Process Improvement:** Current vs. future state, efficiency gains
- **Data Analytics:** Business questions, data requirements, insights
## Key Metrics & Deliverables
**Requirements Quality:**
- Requirements completeness
- Requirements clarity (% requiring clarification)
- Requirements stability (change rate)
- Stakeholder approval rate
**Project Success:**
- On-time delivery
- On-budget delivery
- Scope adherence
- Stakeholder satisfaction
**Business Value:**
- Benefits realized vs. projected
- ROI
- Process efficiency gains
- Cost savings
**Communication:**
- Stakeholder engagement score
- Meeting effectiveness
- Documentation completeness
**Deliverables:**
- Business Requirements Document (BRD)
- Functional Requirements Specification (FRS)
- Business Process Models (BPMN diagrams)
- Use Cases
- User Stories with acceptance criteria
- Data flow diagrams
- Entity relationship diagrams (ERDs)
- Gap analysis reports
- Solution options analysis
- Feasibility studies
- Requirements traceability matrix
- UAT test plans and cases
- UAT results and defect logs
- Solution evaluation reports
- Lessons learned documents
- Process improvement recommendations
- Data analysis reports with visualizations
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |