/f5-ba

description: Business analysis workflow
argument-hint: <start|continue|complete> [phase]

/f5-ba - Business Analysis Workflow Command

Manage Business Analysis workflow following BABOK standards, from Enterprise Analysis to Validation & Sign-off.

ARGUMENTS

The user's request is: $ARGUMENTS

⚠️ CRITICAL OUTPUT RULES

**BA Workflow files MUST be in `.f5/ba-workflow/` NOT in project root or `docs/`.**

**BẮT BUỘC tuân theo cấu trúc sau:**

| Document Type | Output Path | |--------------|-------------| | BA Workflow | `.f5/ba-workflow/` | | Phase 1 docs | `.f5/ba-workflow/phase-1-enterprise-analysis/` | | Phase 2 docs | `.f5/ba-workflow/phase-2-planning/` | | Phase 3 docs | `.f5/ba-workflow/phase-3-elicitation/` | | Phase 4 docs | `.f5/ba-workflow/phase-4-documentation/` | | Phase 5 docs | `.f5/ba-workflow/phase-5-validation/` | | Status file | `.f5/ba-workflow/status.json` |

**✅ CORRECT paths:**

.f5/ba-workflow/status.json ✅
.f5/ba-workflow/phase-1-enterprise-analysis/stakeholder-map.md ✅
.f5/ba-workflow/phase-4-documentation/documents/srs.md ✅

**❌ WRONG paths:**

ba-workflow/status.json ❌  (missing .f5/ prefix!)
docs/stakeholder-map.md ❌
phase-1/stakeholder-map.md ❌

BA WORKFLOW OVERVIEW

BA WORKFLOW PHASES
════════════════════════════════════════════════════════════════

  Phase 1: Enterprise Analysis
  ├── Stakeholder Identification
  ├── Current State Documentation
  └── Problem Statement
          ↓ Gate 1

  Phase 2: Requirements Planning
  ├── Scope Definition
  ├── Requirements Management Plan
  └── Communication Plan
          ↓ Gate 2

  Phase 3: Requirements Elicitation
  ├── Interviews
  ├── Workshops
  ├── Document Analysis
  └── Excel Import (from customer)
          ↓ Gate 3

  Phase 4: Analysis & Documentation
  ├── BRD (Business Requirements Document)
  ├── SRS (Software Requirements Specification)
  └── FRS (Functional Requirements Specification)
          ↓ Gate 4

  Phase 5: Validation & Sign-off
  ├── Review Sessions
  ├── Approval Workflow
  └── Baseline
          ↓ Complete

════════════════════════════════════════════════════════════════

STEP 1: PARSE SUBCOMMAND

| Pattern | Action | |---------|--------| | `init` | **INIT_WORKFLOW** | | `status` | **SHOW_STATUS** | | `stakeholders` | **MANAGE_STAKEHOLDERS** | | `elicit` | **ELICITATION** | | `gate` | **CHECK_GATE** | | `document` | **GENERATE_DOCUMENT** | | `iterate` | **ITERATE_PHASE** | | (default) | **SHOW_HELP** |

---

ACTION: INIT_WORKFLOW

`/f5-ba init`

Initialize BA workflow for the project.

WORKFLOW:

1. Create directory structure:
   .f5/ba-workflow/
   ├── phase-1-enterprise-analysis/
   │   ├── stakeholder-map.md
   │   ├── current-state.md
   │   └── problem-statement.md
   ├── phase-2-planning/
   │   ├── scope.md
   │   ├── requirements-management-plan.md
   │   └── communication-plan.md
   ├── phase-3-elicitation/
   │   ├── interview-notes/
   │   ├── workshop-notes/
   │   └── imported-documents/
   ├── phase-4-documentation/
   │   ├── documents/
   │   │   ├── brd.md
   │   │   ├── srs.md
   │   │   └── frs.md
   │   └── signoff/
   ├── phase-5-validation/
   │   ├── review-notes/
   │   └── signoff/
   ├── templates/
   ├── gates/
   │   ├── gate-1-checklist.md
   │   ├── gate-2-checklist.md
   │   ├── gate-3-checklist.md
   │   ├── gate-4-checklist.md
   │   └── gate-5-checklist.md
   └── status.json

2. Create status.json to track progress
3. Copy templates from F5 Framework
4. Display next steps

Output

## BA Workflow Initialized

**Project:** {{PROJECT_NAME}}
**Created:** {{TIMESTAMP}}

### Directory Structure Created

.f5/ba-workflow/
├── phase-1-enterprise-analysis/
├── phase-2-planning/
├── phase-3-elicitation/
├── phase-4-documentation/
├── phase-5-validation/
├── templates/
├── gates/
└── status.json

### Status File

Created: .f5/ba-workflow/status.json

### Next Steps

1. Start with stakeholder identification:
   `/f5-ba stakeholders --add`

2. Document problem statement:
   `/f5-ba document --problem`

3. Check Phase 1 gate:
   `/f5-ba gate --phase 1`

4. Check overall status:
   `/f5-ba status`

---

ACTION: SHOW_STATUS

`/f5-ba status`

Display BA workflow status.

WORKFLOW:

1. Read .f5/ba-workflow/status.json
2. Calculate phase progress
3. Check gate statuses
4. Show document pipeline integration
5. Display next actions

Output

## BA Workflow Status

**Project:** {{PROJECT_NAME}}
**Started:** {{START_DATE}}
**Current Phase:** {{CURRENT_PHASE}}

### Phase Progress

| Phase | Status | Progress |
|-------|--------|----------|
| 1. Enterprise Analysis | {{STATUS_1}} | {{PROGRESS_1}} |
| 2. Requirements Planning | {{STATUS_2}} | {{PROGRESS_2}} |
| 3. Requirements Elicitation | {{STATUS_3}} | {{PROGRESS_3}} |
| 4. Analysis & Documentation | {{STATUS_4}} | {{PROGRESS_4}} |
| 5. Validation & Sign-off | {{STATUS_5}} | {{PROGRESS_5}} |

### Gate Status

| Gate | Status | Passed Date |
|------|--------|-------------|
| Gate 1 | {{GATE_1_STATUS}} | {{GATE_1_DATE}} |
| Gate 2 | {{GATE_2_STATUS}} | {{GATE_2_DATE}} |
| Gate 3 | {{GATE_3_STATUS}} | {{GATE_3_DATE}} |
| Gate 4 | {{GATE_4_STATUS}} | {{GATE_4_DATE}} |
| Gate 5 | {{GATE_5_STATUS}} | {{GATE_5_DATE}} |

### Document Pipeline Integration

| Metric | Value |
|--------|-------|
| Latest Version | {{DOC_VERSION}} |
| Total Versions | {{VERSION_COUNT}} |
| Requirements | {{REQ_COUNT}} |

### Stakeholders

| Category | Count |
|----------|-------|
| Executive | {{EXEC_COUNT}} |
| Business User | {{BIZ_COUNT}} |
| Technical | {{TECH_COUNT}} |
| External | {{EXT_COUNT}} |

### Next Actions

{{#each NEXT_ACTIONS}}
- {{this}}
{{/each}}

Status Indicators

| Symbol | Status | |--------|--------| | ✅ | COMPLETED | | 🔄 | IN PROGRESS | | ⬜ | NOT STARTED | | ⏸️ | ON HOLD | | ❌ | BLOCKED |

---

ACTION: MANAGE_STAKEHOLDERS

`/f5-ba stakeholders`

Manage stakeholder identification and mapping.

Options

| Option | De