business-analyst

Guide product discovery and create comprehensive product briefs.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/phoenicisf/forex-analyzer --skill business-analyst-phoenicisf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-analyst
Source: https://github.com/phoenicisf/forex-analyzer/tree/main/.agents/skills/business-analyst
Command: npx skills add https://github.com/phoenicisf/forex-analyzer --skill business-analyst-phoenicisf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill guides teams through structured discovery, stakeholder interviews, market research, and requirements analysis to produce clear, actionable product briefs ready for handoff.

Core Features & Use Cases

  • Product Discovery Guidance: Facilitate problem framing and opportunity identification to surface high-value initiatives.
  • Stakeholder Interview Framework: Structured question sets to elicit needs, constraints, and success criteria.
  • Market & Competitive Research: Analyze market context and competitive landscape to inform briefs.
  • Requirements Analysis & Product Briefs: Translate insights into clear, actionable requirements and comprehensive briefs for handoff.

Quick Start

Generate a complete product brief by identifying stakeholders, goals, and constraints, then document requirements and risks.

Frequently Asked Questions about business-analyst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure stakeholder interviews for product discovery?

A product brief for handoff includes problem statements, target users, success metrics, risk analysis, timelines, and stakeholder validation. These structured outputs ensure development teams receive clear, actionable requirements.

What is the best way to frame problems during product discovery?

Problem framing during product discovery facilitates opportunity identification to surface high-value initiatives. It guides teams to translate research insights into clear, actionable requirements for subsequent product briefs.

How do I translate market research into actionable requirements?

Market research translates into actionable requirements by analyzing market context and the competitive landscape to inform product briefs. This process turns raw insights into structured documentation ready for engineering handoff.

Can I generate a complete product brief from just stakeholder goals and constraints?

Yes, you can generate a product brief by identifying stakeholders, goals, and constraints. The skill then documents requirements, risk analysis, and success metrics to deliver a structured, ready-for-handoff output.

Does this approach to requirements analysis work without prior technical specifications?

Requirements analysis through this discovery process works without prior technical specifications by using stakeholder interviews and market research to build the brief. It frames the problem and establishes success metrics from scratch.