Skip to main content
pdd conflicts is the Multi-Prompt Architecture workflow command. It compares two prompt files, identifies any conflicting requirements or incompatible specifications between them, and suggests how to resolve each conflict. The output CSV is compatible with pdd change --csv for batch application of resolutions.

​
Usage

pdd [GLOBAL OPTIONS] conflicts [OPTIONS] PROMPT_FILE_1 PROMPT_FILE_2

​
Arguments

​
PROMPT_FILE_1
string
required
The first prompt file to compare.
​
PROMPT_FILE_2
string
required
The second prompt file to compare.

​
Options

​
--output
string
Where to save the conflict analysis results CSV. Default: <prompt1_basename>_<prompt2_basename>_conflict.csv. Also reads from PDD_CONFLICTS_OUTPUT_PATH.

​
Output format

The output CSV has two columns:
ColumnDescription
prompt_nameThe prompt file that needs modification to resolve the conflict
change_instructionsSpecific instructions for resolving the conflict in that prompt
This format matches the output of pdd detect and can be used directly as input to pdd change --csv.

​
When to use

Use pdd conflicts as part of the Multi-Prompt Architecture workflow:
  • When two modules are being integrated and you suspect their prompts make conflicting assumptions.
  • After splitting a large prompt (with pdd split) to verify the resulting two prompts are consistent.
  • Before merging changes across modules to catch incompatibilities early.
  • As a pre-merge check in CI to detect prompt-level conflicts automatically.

​
Multi-Prompt Architecture workflow

The full conflict resolution workflow follows this sequence:
  1. Detect conflicts — pdd conflicts prompt_a.prompt prompt_b.prompt
  2. Resolve conflicts — pdd change --manual --csv conflicts_output.csv src/
  3. Regenerate code — pdd sync module_a && pdd sync module_b
  4. Update interfaces — pdd example to refresh interface files if needed
  5. Verify system — Run the full test suite

​
Example

pdd conflicts \
  --output conflicts_analysis.csv \
  data_processing_module_python.prompt \
  data_visualization_module_python.prompt
Then apply the suggested resolutions: 
pdd change --manual --csv conflicts_analysis.csv src/
  • pdd detect — Produces the same CSV format; detects which prompts need changes based on a description.
  • pdd split — Use conflicts after splitting a prompt to verify the two resulting prompts are compatible.
  • pdd change — Consumes the CSV output via --csv to apply resolutions in batch.

Build docs developers (and LLMs) love

Get started for freeTalk to us