business-analyst

Name: business-analyst
Availability: InStock
Author: logisoft-web

Guide stakeholder interviews, market analysis, and requirements gathering for product briefs.

Updated Apr 17, 2026

Search Tags:#requirements gathering #market research #product brief #product discovery #stakeholder interview

Ready to run

npx skills add https://github.com/Logisoft-web/kiro-skills --skill business-analyst-logisoft-web

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: business-analyst
Source: https://github.com/Logisoft-web/kiro-skills/tree/main/business-analyst
Command: npx skills add https://github.com/Logisoft-web/kiro-skills --skill business-analyst-logisoft-web

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines product discovery and requirements analysis by guiding structured stakeholder interviews, market research, and problem validation.

Core Features & Use Cases

Structured Discovery Guidance: Provides comprehensive interview questions and frameworks to uncover real user problems.
Market & Competitive Research: Facilitates market sizing, competitor analysis, and gap identification.
Requirements Documentation: Assists in creating detailed product briefs with success metrics and risk assessments.
Use Case: Imagine launching a new feature; use this Skill to gather user needs, validate problems, analyze competitors, and compile a ready-to-share product brief.

Quick Start

Initiate a product brief by describing the target problem and key stakeholders, then follow the prompts to gather insights and prepare documentation.

Frequently Asked Questions about business-analyst

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

FAQPage Schema

How do I gather requirements and validate problems for a new product feature?▼

To gather requirements and validate problems for a new product feature, use structured stakeholder interviews and market analysis frameworks to uncover user needs and compile a comprehensive product brief. This approach ensures early-stage research accurately scopes features before development.

What is the best way to document a product brief after stakeholder interviews?▼

The best way to document a product brief after stakeholder interviews is to translate the gathered strategic input into detailed requirements documentation. This includes defining success metrics, identifying market gaps, and appending risk assessments to create a ready-to-share foundation for product planning.

Can I use this for market research and competitor analysis without technical dependencies?▼

Yes, you can conduct market research and competitor analysis without technical dependencies. This process requires only strategic input to facilitate market sizing, gap identification, and competitive analysis, making it suitable for early-stage product discovery environments.

How do I structure stakeholder interviews during product discovery?▼

Structure stakeholder interviews during product discovery by providing comprehensive interview questions and frameworks tailored to uncover real user problems. Describe the target problem and key stakeholders first, then follow guided prompts to gather actionable insights for feature scoping.

When do I need a structured product discovery process?▼

You need a structured product discovery process when launching a new feature or setting the foundation for product planning. It guides problem validation, market sizing, and requirements gathering to ensure teams build solutions backed by validated user needs and competitive gap analysis.

What limitations should I expect when using strategic input for requirements gathering?▼

When using strategic input for requirements gathering, expect limitations in technical execution and automated data parsing. This approach focuses exclusively on guiding stakeholder interviews, market analysis, and problem validation to craft product briefs, requiring human strategic direction rather than automated technical processing.