skills.rest
baobao0303
baobao0303COMMUNITY
Explore all skills by this author →
WebsiteGitHub

harness-edit-prd

Forward legacy PRD edit requests into the harness-prd workflow with update intent.

1|Updated May 23, 2026
Search Tags:#prd#intent detection#agent customization#repository automation#compatibility shim#workflow forwarding#validation context
One-click install
npx skills add https://github.com/baobao0303/harness --skill harness-edit-prd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-edit-prd
Source: https://github.com/baobao0303/harness/tree/main/.agents/skills/harness-edit-prd
Command: npx skills add https://github.com/baobao0303/harness --skill harness-edit-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents you from repeatedly re-teaching an AI agent how to produce and validate accurate PRDs by forwarding legacy “edit PRD” requests into the newer standardized harness-prd workflow.

Core Features & Use Cases

  • Deprecated compatibility shim: Keeps existing invocations working by name and via legacy _harness/custom/harness-edit-prd.toml overrides.
  • Intent-preserving forwarding: Forces harness-prd to use update intent and passes through your original user input verbatim.
  • Legacy customization resolution: Resolves workflow legacy fields (activation steps, persistent facts, on-complete) and injects them into harness-prd so behavior stays consistent.

Quick Start

Invoke harness-edit-prd as you normally would, and migrate any customization from _harness/custom/harness-edit-prd.toml to _harness/custom/harness-prd.toml to silence the deprecation notice next time.

Frequently Asked Questions about harness-edit-prd

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

FAQPage Schema
How do I update an existing PRD using the harness-prd workflow?▼

Yes, legacy harness-edit-prd invocations still function by routing requests into the harness-prd workflow. The compatibility shim preserves update intent and forwards original user input verbatim, while resolving legacy customization fields for consistent behavior.

Why do I see a deprecation notice when editing my PRD?▼

A deprecation notice appears during PRD editing because harness-edit-prd is a deprecated shim routing to harness-prd. Migrate customizations from `_harness/custom/harness-edit-prd.toml` to `_harness/custom/harness-prd.toml` to silence it.

How do I migrate legacy PRD configurations to the new harness-prd workflow?▼

Migrate legacy PRD configurations by moving overrides from `_harness/custom/harness-edit-prd.toml` to `_harness/custom/harness-prd.toml`. The shim resolves legacy activation steps and persistent facts, injecting them into the new workflow.

Does harness-edit-prd preserve my original PRD update instructions?▼

Yes, harness-edit-prd uses intent-preserving forwarding to pass original user input verbatim to harness-prd. This ensures specific PRD update instructions execute exactly as provided without running additional shim steps.

Can I still use my existing repository automation scripts that call harness-edit-prd by name?▼

Yes, repository-level automation scripts calling harness-edit-prd by name continue to work. The shim applies to repository-level automation scenarios, resolving legacy customization and invoking harness-prd with update intent.

Related Skills

Explore More Product & Management Skills→
baobao0303baobao0303
1

harness-create-prd

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

Community
Basic
baobao0303baobao0303
1

harness-validate-prd

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

Community
Basic
mol4mol4
1

bmad-validate-prd

Validate product requirement documents by forwarding requests to bmad-prd.

Community
Basic
tiweentiween

bmad-validate-prd

Validate product requirements documents and forward calls to bmad-prd.

Official
Intermediate