# Ba Requirements Analysis

> >

- **Type:** Skill
- **Install:** `agentstack add skill-dungnotnull-hybrid-harness-chaos-process-prm-s01-ba-requirements`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [dungnotnull](https://agentstack.voostack.com/s/dungnotnull)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [dungnotnull](https://github.com/dungnotnull)
- **Source:** https://github.com/dungnotnull/hybrid-harness-chaos-process-prm/tree/main/skills/s01-ba-requirements

## Install

```sh
agentstack add skill-dungnotnull-hybrid-harness-chaos-process-prm-s01-ba-requirements
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# BA Requirements Analysis (s01) - BMAD Powered

## Purpose
Act as a Strategic Business Analyst using the **BMAD methodology** to align business value with technical architecture. The goal is to produce a rigorous Product Requirements Document (PRD) and Architecture Decision Records (ADRs) that are not just technically sound, but business-justified and audited for zero-gap implementation.

---

## Prerequisites
- [ ] Project description or user request available
- [ ] Stakeholder availability for interview/requirements gathering
- [ ] Access to existing documentation (if any)
- [ ] .commandcode/ directory initialized for artifact storage

## Input Contract

| Input | Source | Required |
|---|---|---|
| User project description | User prompt or s00 context | Yes |
| Taste preferences | `.commandcode/taste/taste.md` | No |
| Previous PRDs (if iterating) | s25 postmortem feedback | No |
| Existing codebase artifacts | Repository scan | No |
| Team/stakeholder info | User or org context | Recommended |

---

## Output Contract

| Output | Destination | Format |
|---|---|---|
| Product Requirements Document (PRD) | `.commandcode/prd.md` | Markdown |
| Architecture Decision Records (ADRs) | `.commandcode/adr/` | Markdown (one per decision) |
| Prioritized backlog | `.commandcode/backlog.md` | Markdown checklist |
| Structured context for s01-1 + s04 | Workflow context object | YAML |
| Risk register | Included in PRD | Table |

---

## BMAD Analysis Framework

```
BUSINESS MODEL (B) → ARCHITECTURE (A) → DESIGN (D) → ANALYSIS/AUDIT (A)

B: Align with value chain, OKRs, and economic impact.
A: Map business goals to technical components and trade-offs.
D: Prepare raw specs for User Flow/Detailed Design (s01-1).
A: Rigorous audit of the B-A-D chain to ensure zero contradictions.
```

---

## Phase 1: Business Model Discovery (B)
*Focus: The "Why" and the Value Chain.*

### Opening Questions (The Value Layer)
```yaml
questions:
  - "What is the core business value of this project? How does it generate revenue or reduce cost?"
  - "What are the la-line OKRs (Objectives and Key Results) this project supports?"
  - "What is the 'Value Exchange'? (What does the user provide, and what exact value do they get in return?)"
  - "What is the economic impact of NOT building this (Cost of Delay)?"
  - "Who are the primary and secondary stakeholders, and what is their definition of 'Winning'?"
```

### Domain & Context Deep-Dive
```yaml
questions:
  - "Walk me through the critical user journey from a business value perspective."
  - "What are the non-negotiable regulatory or compliance constraints (SOC2, GDPR, etc.)?"
  - "What's the expected scale and the growth trajectory for the next 12 months?"
  - "What SLAs are required to maintain business trust?"
```

---

## Phase 2: Architecture Mapping (A)
*Focus: Translating Business Value to Technical Strategy.*

### Technical Discovery & Alignment
```yaml
questions:
  - "What's the existing tech stack? How does it constrain or enable the Business Model?"
  - "Which components are the 'critical path' for the value exchange?"
  - "What are the top 3 failure modes that would bankrupt the business value (Critical Risks)?"
  - "What observability metrics will prove the Business Model is working (KPIs)?"
```

### Architecture Decision Records (ADR)
For every major decision, produce an ADR that explicitly links back to the Business Model:
```markdown
## ADR-: 
**Business Driver**: Which part of the Business Model (B) motivates this decision?
**Decision**: The technical choice.
**Context**: Why this over others?
**Consequences**: Trade-offs in terms of cost, speed, and reliability.
**Chaos Implications**: How this affects resilience (s14).
```

---

## Phase 3: Design Specification (D)
*Focus: Defining the "What" for downstream User Flow (s01-1).*

### Requirement Format (BMAD-Aligned)
```markdown
## REQ--: 
**Business Value**: How does this requirement support the Business Model?
**Priority**: P0 (must) | P1 (should) | P2 (could) | P3 (won't-now)
**Acceptance Criteria**: 
- [ ] Given , when , then 
**Test Strategy**: How will we verify this?
**Chaos Relevance**: Does this need resilience testing? (YES/NO)
```

---

## Phase 4: Analysis & Audit (A)
*Focus: The Quality Gate. No PRD is "Approved" without this audit.*

Perform a **BMAD Cross-Audit** and document it in the PRD:

### 1. Vertical Alignment Audit
- [ ] **B $\rightarrow$ A**: Does every business goal have a corresponding architectural component?
- [ ] **A $\rightarrow$ D**: Does every architectural decision translate into a set of requirements?
- [ ] **D $\rightarrow$ B**: Does every requirement actually contribute to the original business value?

### 2. Conflict & Gap Analysis
- [ ] **Contradiction Check**: Do any ADRs conflict with the SLAs or Constraints?
- [ ] **Edge Case Probe**: Have we identified the "Worst Case" for the business (e.g., data loss, total downtime)?
- [ ] **Complexity Audit**: Is the architecture over-engineered for the stated business value?

---

## Phase 5: Final Delivery (PRD & Backlog)

### PRD Template (BMAD Edition)
```markdown
# Product Requirements Document — 

## 1. Business Model (The 'B')
- **Value Proposition**: The economic/operational "Why".
- **Value Exchange Map**: User $\rightarrow$ System $\rightarrow$ Business Value.
- **Success Metrics (KPIs)**: Measurable business outcomes.
- **Cost of Delay**: Impact of not delivering.

## 2. Architecture Overview (The 'A')
- **System Map**: Component inventory and value flow.
- **ADR Summary Table**: Mapping decisions to business drivers.
- **Infrastructure & Tiers**: SLAs and Chaos budgets per tier.

## 3. Design Specifications (The 'D')
- **Functional Requirements**: (B-linked REQs).
- **Non-Functional Requirements**: (Performance, Security, Reliability).
- **Constraints & Risks**.
- **User Stories & Epics**.

## 4. BMAD Audit Report (The 'A')
- **Alignment Verdict**: (e.g., "Architecture fully supports Business Model").
- **Resolved Conflicts**: List of gaps found and fixed during audit.
- **Residual Risks**: What we are consciously accepting.

## 5. Implementation Roadmap
- **Prioritized Backlog**: P0 $\rightarrow$ P3.
- **Timeline & Milestones**.
- **Open Questions**.
```

---

## Context Handoff to Downstream Skills

```yaml
ba_output:
  business_model:
    value_proposition: string
    kpis: [string]
    value_exchange: string
  
  architecture:
    components: [{name, value_role, criticality}]
    adrs: [{id, decision, business_driver}]
    
  requirements:
    functional: [{id, business_value, acceptance_criteria}]
    chaos: [{id, hypothesis, business_impact}]

  audit_status:
    alignment_verified: boolean
    critical_gaps_resolved: boolean
    
  for_s01_1_user_flow:
    primary_personas: [string]
    critical_value_paths: [string]
    failure_modes_to_map: [string]
```

---

## AI Agent Integration

### Autonomy Level
| Aspect | Level | Description |
|---|---|---|
| Current | L2 | AI drafts the full BMAD chain, Human audits and signs off |
| Target | L3 | AI runs complete BMAD analysis autonomously, human approves final PRD |

### Harness AI Agent
**Agent**: Harness AI DevOps Agent

**Capabilities**:
- Full BMAD methodology execution (Business Model -> Architecture -> Design -> Analysis/Audit)
- Requirements gathering and stakeholder analysis
- ADR generation with business driver linkage
- PRD generation with vertical alignment audit
- Risk register creation and gap analysis

### Human Gates
- Final PRD approval and sign-off required before handoff to s01-1
- Architecture Decision Records require human review for business alignment
- Stakeholder validation required for Business Model (B) phase
- Backlog prioritization requires product owner confirmation

## Success Criteria
- [ ] Business Model (B) explicitly defines the "Value Exchange".
- [ ] Every ADR explicitly references a Business Driver.
- [ ] PRD contains a formal **BMAD Audit Report** section.
- [ ] Vertical alignment (B $\rightarrow$ A $\rightarrow$ D) is verified and documented.
- [ ] Context handoff provides specific "Critical Value Paths" for s01-1.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [dungnotnull](https://github.com/dungnotnull)
- **Source:** [dungnotnull/hybrid-harness-chaos-process-prm](https://github.com/dungnotnull/hybrid-harness-chaos-process-prm)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-dungnotnull-hybrid-harness-chaos-process-prm-s01-ba-requirements
- Seller: https://agentstack.voostack.com/s/dungnotnull
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.