Resolve Spec Conflict

Always use the skill load-plain-reference to retrieve the ***plain syntax rules — but only if you haven't done so yet.

When This Applies

A conflict exists (or is suspected) when:

• Conformance tests for a previously passing functional spec begin to fail after a new spec is rendered.
• A new spec being added (via the add-functional-spec or add-functional-specs skill) appears to contradict an existing spec.
• Two specs make incompatible assertions about the same behavior, data, or state.

Workflow

Step 1: Identify the Conflicting Pair

Read the .plain file and pinpoint the two specs in tension. If the conflict was detected via a conformance test failure, also read the failing test and the generated implementation in plain_modules/ to understand what behavior changed.

Step 2: Diagnose the Root Cause