pm-conflict-resolver

Generate a minimal diff to repair a failed downstream PM workflow node.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-conflict-resolver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-conflict-resolver
Source: https://github.com/Wcof/PMSkill/tree/main/skills/utility/pm-conflict-resolver
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-conflict-resolver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill fixes downstream workflow failures in a PM artifact pipeline without forcing a full rerun of the entire chain. It is designed for cases where one node breaks because of a mismatch with its immediate upstream JSON inputs, and only a precise local correction is needed.

Core Features & Use Cases

  • Local-only repair scope: Works strictly from the error context and the dependent upstream node JSON, avoiding global PMContext rewrites.
  • Minimal diff output: Produces a focused before-to-after change for the exact failing field instead of regenerating whole node files.
  • Conflict containment: Stops when required upstream JSON is missing, when the error is too vague to localize, or when a fix would spread across multiple upstream nodes and needs PM judgment.
  • Recovery logging: Records affected fields, value changes, and impacted downstream nodes in the conflict log so orchestrators can rerun only what is necessary.
  • Use Case: When a PRD node references a state that does not exist in the domain model, this Skill updates only that broken reference, preserves all healthy frozen fragments, and identifies which downstream nodes should be rerun.

Quick Start

Ask the AI to use pm-conflict-resolver on a failed node by providing the exact error context and the relevant upstream node JSON so it can return a minimal diff and rerun scope.

Frequently Asked Questions about pm-conflict-resolver

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

FAQPage Schema
How do I repair a failed PRD node without rerunning the entire product workflow?

To repair a failed PRD node, you generate a minimal diff from the error context and dependent upstream JSON fragments, applying localized recovery to fix only the broken reference while preserving healthy frozen fragments.

What is minimal diff workflow recovery for multi-step product artifact pipelines?

Minimal diff workflow recovery is a conflict resolution technique that fixes a single failing downstream PM node by applying precise local corrections instead of regenerating whole node files or triggering a full pipeline rerun.

How do I fix broken JSON references in a PRD node when the domain model state does not exist?

You fix broken JSON references by updating only the exact failing field using strict local scope control, which repairs the mismatched state without overwriting the global PMContext or healthy upstream dependencies.

When should I avoid partial backtracking for PM workflow conflict resolution?

You should avoid partial backtracking when required upstream JSON is missing, the error is too vague to localize, or a fix would spread across multiple upstream nodes, requiring manual PM judgment instead of automated JSON repair.

Does pm-conflict-resolver work with global PMContext reads during node repair?

No, pm-conflict-resolver prohibits global PMContext reads during node repair, working strictly from the error context and dependent upstream node JSON to ensure strict local scope control and prevent unintended pipeline overwrites.

How do I log affected fields and downstream rerun targets after fixing a frozen node?

You log affected fields, value changes, and impacted downstream nodes in the conflict log during frozen node repair, which allows orchestrators to identify exactly which downstream nodes should be rerun after the localized fix.