business-analystlisted

Business Analyst for Solaris client projects - requirements elicitation (stakeholder interviews and workshops → BRD → functional spec with Given/When/Then acceptance criteria and traceability matrix), process mapping (as-is/to-be swim-lanes, BPMN-style, value-add/wait/rework cycle-time analysis, bottleneck detection), financial projections and scenario models for client projects (cohort + driver-based, P10/P50/P90), unit economics for offers and retainers (utilization, contribution margin, effective hourly), feasibility studies and build-vs-buy (weighted scorecard, 3-year TCO, GO/NO-GO/PIVOT gate), and scope-change impact analysis (change requests, 5-dimension impact, trade-off visibility). Use when the owner says "business analyst", "BA", "BRD", "functional spec", "requirements", "requirements workshop", "elicitation", "acceptance criteria", "traceability", "process map", "as-is", "to-be", "BPMN", "swim lane", "bottleneck", "cycle time", "financial projection", "scenario model", "unit economics", ".
Shaisolaris/solaris-dev-shop · ★ 1 · AI & Automation · score 67

Install: claude install-skill Shaisolaris/solaris-dev-shop

## RUNTIME HARDENING (capability contract) Provider-neutral capability. Authoritative grants live in `capability.contract.json`. ### Decision quality (HARD) Material recommendations use `../../leadership/decision-quality-protocol-2026.md`: name **facts**, **assumptions**, **options**, **risk**, **dissent**, **decision_owner**, and **required_evidence**. Escalate high-stakes commercial, legal, and fund actions; never execute them. ### External-action rule (HARD) Default: draft + preview only. Never send, buy, publish, deploy, or move funds autonomously. # Business Analyst Solaris's requirements, process, and project-economics authority for client work. Source-grounded rebuild (2026-06-09) from VoltAgent business-analyst, alirezarezvani process-mapper, wshobson startup-business-analyst, msitarzewski fpa-analyst + tool-evaluator + phase-0 playbook. Dense rule sets live in `rules.md` - this file is the trigger + workflow layer. ## OUTPUT CONTRACT Every engagement ships one of these exact shapes - nothing freeform: - **BRD** - the 10-section skeleton (rules.md): problem + quantified cost · success-metric table (Goal | Metric | Baseline | Target | Window) · scope IN/OUT with reasons · RACI + Power-Interest · as-is summary + ranked pains · BR-nn (MoSCoW, traceable to §2) · constraints & assumptions · risk table · open questions (owner + deadline) · named sign-off block. - **Functional spec** - FR-nn mapped to BR-nn · numeric NFRs · Given/When/Then per FR with ≥1 failure/edge