harness-validate-prd

Forwards legacy PRD validation requests to harness-prd with customization context.

1|Updated May 23, 2026

Search Tags:#workflow #validation #compatibility #deprecation #architecture decisions #prd

Ready to run

npx skills add https://github.com/baobao0303/harness --skill harness-validate-prd

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you validate a Product Requirements Document (PRD) using the Harness PRD workflow, while maintaining backward compatibility for legacy invocations.

Core Features & Use Cases

DEPRECATED compatibility shim: Forwards legacy calls to the newer harness-prd skill with validate intent, so existing setups keep working.
Legacy customization resolution: Loads legacy overrides from _harness/custom/harness-validate-prd.toml and harness-validate-prd.user.toml, then passes resolved activation and persistence fields through to harness-prd.
User-facing deprecation notice: Emits a notice in the user’s resolved communication language to guide migration to harness-prd.

Quick Start

Tell your AI agent to run harness-validate-prd to validate the target PRD, and it will automatically forward you to harness-prd with validate intent.

Frequently Asked Questions about harness-validate-prd

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

FAQPage Schema

How do I validate a PRD while keeping legacy customizations working?▼

PRD validation forwards legacy requests to the newer harness-prd skill with validate intent, while resolving and preserving legacy override files from _harness/custom. Existing setups keep functioning without changes.

What happens to my legacy harness-validate-prd override files during PRD validation?▼

Legacy customization files like harness-validate-prd.toml and harness-validate-prd.user.toml are loaded, with resolved activation and persistence fields passed through to harness-prd. Your overrides are preserved across the migration.

Is harness-validate-prd deprecated and should I migrate to harness-prd?▼

Yes, harness-validate-prd is a deprecated compatibility shim that emits a migration notice guiding you to harness-prd. It forwards validate intent calls so existing workflows continue working during the transition.

How do I migrate from legacy PRD validation to the new Harness workflow?▼

Tell your AI agent to run harness-validate-prd to validate your target PRD, and it automatically forwards to harness-prd with validate intent. The skill resolves legacy workflow steps and persistent facts before invoking the new workflow.

Can I still use custom override files with the new harness-prd validation workflow?▼

Yes, legacy custom override files under _harness/custom are resolved through resolve_customization.py, and the activation and persistence fields are passed through to harness-prd. Backward compatibility is maintained for direct invocations.