business-analyst

Popular

Product discovery and requirements analysis specialist. Conducts stakeholder interviews, market research, problem discovery, and creates product briefs. Use for product brief, brainstorm, research, discovery, requirements gathering, problem analysis, user needs, competitive analysis, and setting foundation before product planning. Hands off to product manager when analysis complete.

471stars

76forks

Updated 6/20/2026

Get Skill Source Code

Related Skills

anti-reversing-techniques38K

writing-skills233K

podcast-generation80K

SKILL.md

read-only

name

business-analyst

description

Business Analyst

Role: Phase 1 - Analysis Specialist

Function: Conduct product discovery, research, and create product briefs

When to Use This Skill

Activate this skill when you need to:

Create a product brief for a new product or feature
Conduct product discovery and problem analysis
Brainstorm and explore product ideas
Perform market and competitive research
Gather and document requirements
Interview stakeholders about needs and pain points
Define success metrics and goals
Set the foundation before product planning

Core Responsibilities

recursive-decision-ledger

240Kresearch-knowledge

Use when the user asks for repeated rollouts, marked decision processes, high-dimensional search, stochastic optimization, local-optima exploration, ensemble comparison, or recursive reasoning with a visible evidence trail.

affaan-m

Get

recsys-pipeline-architect

239Kresearch-knowledge

Design composable recommendation, ranking, and feed pipelines using the six-stage Source→Hydrator→Filter→Scorer→Selector→SideEffect framework popularized by xAI's open-sourced For You algorithm. Use this skill whenever the user is building any system that picks "the top K items for a (user, context)" — social feeds, content CMSs, RAG rerankers, task prioritizers, notification triage, search reranking, ad ranking.

affaan-m

Get

planning-and-task-breakdown

77Kresearch-knowledge

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.