harness-create-prd

Forward legacy harness-create-prd requests to harness-prd with preserved overrides.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps legacy users generate a Product Requirements Document (PRD) intent while preserving existing invocation compatibility after the workflow was consolidated into a newer skill.

Core Features & Use Cases

  • Deprecated Compatibility Forwarder: Maintains support for the harness-create-prd name and related legacy customization override files so existing agent setups keep working.
  • Customizations Resolution & Injection: Resolves legacy fields from _harness/custom/harness-create-prd.toml and .user.toml, then forwards the resolved activation steps and persistent facts into the new workflow.
  • Intent Forwarding: Forces create-intent behavior by invoking harness-prd with a pre-set intent and verbatim original user input, avoiding duplicate intent detection.
  • Use Case: A team previously configured _harness/custom/harness-create-prd.toml for PRD generation; after upgrading, they can continue using the old skill name while the system routes execution to harness-prd.

Quick Start

Invoke harness-create-prd to forward the request to harness-prd with create intent, preserving any legacy overrides found in _harness/custom/harness-create-prd.toml.

Frequently Asked Questions about harness-create-prd

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

FAQPage Schema
How do I generate a PRD using deprecated legacy workflow overrides?▼

To generate a PRD using deprecated legacy workflow overrides, invoke the legacy harness-create-prd forwarder. It resolves your custom fields from _harness/custom/harness-create-prd.toml and routes execution to the updated harness-prd skill.

What happens to my existing harness-create-prd.toml configurations after a workflow upgrade?▼

Your existing harness-create-prd.toml configurations remain functional after a workflow upgrade. The system resolves legacy fields from this file and injects them as persistent facts into the new harness-prd workflow.

How does the compatibility shim forward create-intent to the new PRD workflow?▼

The compatibility shim forwards create-intent by invoking harness-prd with a pre-set intent and verbatim user input. This bypasses duplicate intent detection while preserving your original request data.

Do I need to update my agent configurations if I rely on the deprecated harness-create-prd name?▼

You do not need to update agent configurations relying on the deprecated harness-create-prd name. The legacy forwarder intercepts the invocation, emits a deprecation notice, and applies pre-resolved activation steps to the new workflow.

Why am I seeing a deprecation notice when generating a Product Requirements Document?▼

You see a deprecation notice during Product Requirements Document generation because the legacy harness-create-prd skill has been consolidated into harness-prd. The notice is emitted in your resolved communication language to alert you of the forwarder mechanism.

Can I preserve persistent facts and activation steps when migrating to a new PRD generation workflow?▼

You can preserve persistent facts and activation steps during PRD workflow migration. The legacy forwarder resolves these customizations from your override files and passes them directly to the new harness-prd execution path.