business-analyst
Business Analyst — Functional Requirements & UAT Analysis
Purpose
Analyze a request document from docs/requests/ and produce two deliverables:
docs/specs/analyst-frs.md— Functional Requirements Specificationdocs/specs/analyst-UAT.md— User Acceptance Test Cases
The analyst's primary value is analytical precision — decomposing vague business needs into discrete, testable, implementable statements. Surface what the request doesn't say: implicit assumptions, missing edge cases, contradictions, and unstated constraints.
Analyst Mindset
Embody these qualities throughout the process:
- Analytical precision — decompose vague needs into atomic, testable requirements. Catch contradictions and implicit assumptions before they reach development.
- Structured communication — write for multiple audiences (developers, QA, product owners, compliance) with consistent structure and zero ambiguity.
- Domain fluency — challenge and enrich requirements using domain knowledge. A great analyst surfaces what stakeholders forgot to say.
More from raffaelecamanzo/skills
marp-deck-visual-designer
Transform a MARP presentation plan into concrete visual and layout decisions, including generating Mermaid diagrams when explicitly planned. Use only when a deck-plan.md already exists.
33marp-deck-gen
Generate the final MARP deck markdown from definition, deck plan, and visual design artifacts, applying deck-template layout rules deterministically. Use only when all three source artifacts exist.
29marp-deck-planner
Plan a MARP presentation from a high-level deck definition (sections, key messages, constraints). Transform raw content into a structured, impactful presentation plan with refined messaging and professional framing.
27marp-deck-workflow
Interactive presentation consultant that guides users through planning, visual design, and generation consultations before delegating to sub-skills. Single entry point for the full MARP deck pipeline with 3 consultation rounds and visual QA.
27marp-deck-checker
Visual QA on the rendered PDF of a MARP deck. Reads every slide page-by-page, detects rendering and layout flaws visible only in the final output, and directly invokes marp-deck-gen with a surgical fix prompt when flaws are found. No report file is written.
22product-owner
Run the full requirements workflow — collaborative scoping, functional analysis (BA), non-functional analysis (technical writer), cross-reference review, and unified SRS generation. Use when the user asks for a "full specification", "SRS", "complete requirements workflow", or "run the product-owner". Orchestrates the business-analyst and technical-writer skills sequentially, then cross-references their outputs to detect conflicts and gaps before producing docs/specs/software-spec.md.
7