harness-agent-analyst

Convert ambiguous business needs into evidence-grounded product requirements and specifications.

1|Updated May 23, 2026

Search Tags:#requirements #market analysis #stakeholder #business analyst #competitive landscape #product briefs #validation proofs

Ready to run

npx skills add https://github.com/baobao0303/harness --skill harness-agent-analyst

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness-agent-analyst
Source: https://github.com/baobao0303/harness/tree/main/.agents/skills/harness-agent-analyst
Command: npx skills add https://github.com/baobao0303/harness --skill harness-agent-analyst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes references (resource) components.

What problem does it solve?

It helps convert vague user intentions into evidence-grounded requirements and actionable specs so agents and teams don’t jump to implementation without understanding the business goal.

Core Features & Use Cases

Requirements elicitation & translation: Clarifies market/customer context and converts it into precise, testable requirement language.
Evidence-based analysis: Prioritizes verifiable findings and represents stakeholder voices to reduce misunderstandings.
Actionable outputs for downstream work: Produces inputs suitable for product briefs, PRFAQs, and validation planning in the Harness workflow.

Quick Start

Invoke harness-agent-analyst and ask Mary to turn your product idea into a structured set of requirements with risks, assumptions, and validation criteria.

Frequently Asked Questions about harness-agent-analyst

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

FAQPage Schema

How do I turn fuzzy product requests into precise business requirements?▼

To turn fuzzy product requests into precise business requirements, you need to clarify market context and translate ambiguous stakeholder intentions into testable requirement language. This ensures teams avoid jumping to implementation without understanding the underlying business goal.

What is evidence-based requirements elicitation for product briefs?▼

Evidence-based requirements elicitation for product briefs is the process of prioritizing verifiable market findings and stakeholder voices to reduce misunderstandings. It converts vague user intentions into actionable specifications and inputs suitable for validation planning.

How do I structure market analysis outputs for downstream product execution?▼

To structure market analysis outputs for downstream product execution, represent stakeholder voices and competitive landscape findings as actionable specs. This produces validation proofs and inputs suitable for PRFAQs and product briefs in the workflow.

Does this business analyst approach work for competitive landscape and stakeholder scenarios?▼

Yes, this business analyst approach works for competitive landscape and stakeholder scenarios by resolving agent customization and adopting configured personas. It structures outputs across market and customer analysis to satisfy guided business analyst dispatch.

What are the limitations of converting vague business needs into requirement specifications?▼

A limitation of converting vague business needs is that the quality of requirement specifications depends entirely on available project facts. Without sufficient evidence or stakeholder input, the structured outputs for validation and downstream execution may lack full context.

Do I need Python3 to run harness-agent-analyst for requirement translation?▼

Yes, you need Python3 installed to run harness-agent-analyst for requirement translation. The environment relies on this dependency to load project facts, resolve agent customization, and structure outputs for validation and downstream execution.