harness-agent-pm

Drive PRD creation and requirements discovery from product vision.

1|Updated May 23, 2026
One-click install
npx skills add https://github.com/baobao0303/harness --skill harness-agent-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-agent-pm
Source: https://github.com/baobao0303/harness/tree/main/.agents/skills/harness-agent-pm
Command: npx skills add https://github.com/baobao0303/harness --skill harness-agent-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams avoid building code before product requirements are understood and aligned by driving structured PRD creation and requirements discovery with an explicit, validation-oriented workflow.

Core Features & Use Cases

  • PRD creation and requirements discovery: Converts product vision into a PRD through user interviews, stakeholder alignment, and iterative clarification.
  • Validated increments for delivery: Translates outcomes into small, shippable components (epics and stories) that development can execute with clear assumptions.
  • Decision support through alignment: Produces requirement outputs that reduce rework by clarifying goals, risks, and evidence needed for validation.

Quick Start

Use the harness-agent-pm skill when you want the product manager to help draft or validate a PRD by interviewing users and extracting stakeholder requirements.

Frequently Asked Questions about harness-agent-pm

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

FAQPage Schema
How do I translate product vision into validated PRDs?

PRD creation converts product vision into requirements by conducting user interviews, eliciting assumptions, and aligning stakeholders to produce validated, shippable epics and stories for development teams.

What is the best way to align stakeholders during requirements discovery?

Stakeholder alignment during requirements discovery uses iterative clarification and decision support to extract assumptions, clarify goals, and produce requirement outputs that minimize development rework.

How to write epics and stories from user interviews?

Transform user interview outcomes into shippable epics and stories by validating discovered requirements, clarifying risks, and breaking product vision into small components with explicit assumptions for development execution.

When do I need a structured PRD workflow?

A structured PRD workflow is needed when teams must avoid building code before requirements are aligned, using validation-oriented processes to clarify goals, extract assumptions, and drive stakeholder alignment.

Can I use this for validating increment delivery and reducing rework?

Validated increment delivery is supported by translating PRD outcomes into small shippable components, clarifying assumptions and risks to produce decision support evidence that actively reduces development rework.