skills.rest
AngelMaldonado
AngelMaldonadoCOMMUNITY
Explore all skills by this author β†’
Website𝕏@amaldonado_07GitHub

cx-conflict-resolve

Resolve contradictions across memory files, specs, and implementation with documented decisions.

Updated Mar 25, 2026
Search Tags:#workflow#documentation#conflict-resolution#specs#memory-management#developer-guidance
One-click install
npx skills add https://github.com/AngelMaldonado/skills --skill cx-conflict-resolve
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: cx-conflict-resolve
Source: https://github.com/AngelMaldonado/skills/tree/main/.claude/skills/cx-conflict-resolve
Command: npx skills add https://github.com/AngelMaldonado/skills --skill cx-conflict-resolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conflicts between memory files, specifications, and implementation can cause inconsistent behavior. This skill provides a guided process to surface contradictions, present context from multiple sources, and drive a resolution that is documented and archived.

Core Features & Use Cases

  • Detect contradictions across memory, specs, and code, and surface them for the developer.
  • Present balanced perspectives with contextual evidence, then guide deprecation, merging, or creation of a new decision.
  • Update memory and specification docs to reflect the resolution, while preserving deprecated versions in an archive.

Quick Start

Describe the conflict and request a structured resolution path.

Frequently Asked Questions about cx-conflict-resolve

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

FAQPage Schema
How do I resolve conflicts between project specs and code implementation?β–Ό

To resolve conflicts between specs and code, surface the contradictions across memory files and implementation, then guide deprecation, merging, or creation of a new documented decision to maintain consistency.

What happens when memory files contradict development specifications?β–Ό

When memory files contradict specifications, the conflict is detected and surfaced with contextual evidence from multiple sources to drive a documented resolution that updates both memory and documentation.

How do I document deprecation decisions when merging conflicting specs?β–Ό

Document deprecation decisions by preserving deprecated versions in an archive while applying the resolved merge outcome to update memory and specification docs for consistent tracing.

What is the best way to trace contradictions across memory and documentation?β–Ό

The best way to trace contradictions across memory and documentation is detecting disagreements across sources, presenting balanced perspectives, and archiving the resolution path to maintain consistent guidance.

When should I use a guided process to resolve memory and spec disagreements?β–Ό

Use a guided process to resolve memory and spec disagreements when two specs disagree on an approach or when memory stores contradictions with implementation, ensuring tracing and merge decisions are documented.

Do I need to manually archive deprecated specs after resolving a conflict?β–Ό

You do not need to manually archive deprecated specs after resolving a conflict, as the resolution process automatically preserves deprecated versions in an archive while applying updates to memory and documentation.

Related Skills

Explore More Software Engineering Skills→
afonsoftafonsoft
1

create-github-issues-for-unmet-specification-requirements

Create GitHub issues for unmet specification requirements using feature_request.yml.

Community
Advanced
gesmith0606gesmith0606

gsd-complete-milestone

Archive milestone ROADMAP and REQUIREMENTS docs into versioned artifacts.

Community
Advanced
whritwhrit

Skill Builder

Create Claude Code Skills with YAML frontmatter and organized directories.

Community
Basic
leeoveryleeovery
27

start-specification

Consolidate concluded discussions into a standalone specification session.

Community
Advanced