AGENT SKILL

conflict-resolution

Detect, represent, and resolve contradictory KB facts, stale claims, duplicate entities, and competing interpretations while preserving provenance until resolved. Trigger on 'resolve conflicting facts', 'contradiction in the KB', 'this claim is stale/superseded', 'merge these duplicate entities'. This is the dedicated contradiction workflow other skills route to; for a routine page rewrite with no conflict use enrich; for a vault-wide sweep use health.

License 许可
MIT
最近更新
2026-11-11
Stars
★ 1
Forks
0

01 前言 Front Matter

name
conflict-resolution
version
0.2.0
mutating
true
triggers
[ "resolve conflicting facts", "contradiction in the kb", "this kb claim is stale", "merge duplicate entities" ]
description
Detect, represent, and resolve contradictory KB facts, stale claims, duplicate entities, and competing interpretations while preserving provenance until resolved. Trigger on 'resolve conflicting facts', 'contradiction in the KB', 'this claim is stale/superseded', 'merge these duplicate entities'. This is the dedicated contradiction workflow other skills route to; for a routine page rewrite with no conflict use enrich; for a vault-wide sweep use health.
allowed-tools
[ "Read", "Write", "Edit", "Bash", "Grep", "Glob" ]
disable-model-invocation
false

03 SKILL.md 正文

Conflict Resolution

Contract

  • Contradictions are preserved with provenance until resolved.
  • Resolution states distinguish superseded, disputed, merged, and unresolved.
  • The current State section reflects best understanding and remaining uncertainty.
  • Mutating skill: it may rewrite State/timeline sections, but it must not erase dissenting evidence without recording the resolution basis.

Intake And Modes

  • Treat $ARGUMENTS as the conflicting pages, claims, entities, or duplicate records to reconcile.
  • Quick mode: identify the conflict and return a resolution recommendation without writing.
  • Standard mode: resolve a bounded page/entity conflict with citations and validation.
  • Deep mode: merge duplicate entities or reconcile a multi-page stale-claim cluster.
  • Use ask-user when both claims are plausible and the resolution depends on user intent or preferred taxonomy.

Evidence Requirements

  • Inspect every cited source, source date, page timeline, and related entity page before resolving.
  • Check whether the conflict is scope-based, time-based, source-quality-based, or a true contradiction.

Workflow

  • Identify the conflicting claims and their sources/dates.
  • Assess recency, source quality, directness, and scope.
  • Choose a resolution: update, mark disputed, split entities, merge duplicates, or ask-user.
  • Rewrite State and timeline with citations; add a review date for anything unresolved.
  • Run graph-audit and citation-audit after edits.

Operating System Backing

This skill is backed by the shared deterministic KB operations harness. Use these commands for audits, CI fixtures, and repeatable agent runs:

  • python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kb_ops.py" graph-audit
  • python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kb_ops.py" citation-audit

Output Format

  • CONFLICT RESOLUTION
  • Status: DONE, DONE_WITH_CONCERNS, BLOCKED, or NEEDS_CONTEXT.
  • Claims, sources, decision, page updates, unresolved items with review dates.
  • Artifact path: updated page path(s), plus optional reports/<YYYYMMDD>-conflict-resolution.md for broad reconciliations.

Anti-Patterns

  • Deleting the losing claim without provenance.
  • Flattening genuine uncertainty into false certainty.

04 同仓库更多 Skills

weisberg
weisberg/agile_agentic_analytics

minimal-skill

Minimal shared skill fixture for marketplace renderer and validator examples.

Skill与智能体开发
★ 1
weisberg
weisberg/agile_agentic_analytics

roadmap

Use this skill when the user wants a product roadmap, initiative sequencing, Now/Next/Later plan, quarterly roadmap, release theme map, product strategy-to-roadmap translation, or executive roadmap narrative. Trigger on phrases like "build a roadmap", "roadmap these initiatives", "what should be now next later", "sequence this backlog", "quarterly product roadmap", "theme-based roadmap", or "plan the next two quarters". Do NOT trigger for drafting or reviewing a single PRD (use prd-writer or prd-review), converting a PRD into an agentic PLAN.md (use prd-to-plan), or scoring/ranking a set of options without a time horizon (use prioritization).

产品经理
★ 1
weisberg
weisberg/agile_agentic_analytics

prioritization

Use this skill when the user wants to rank, score, triage, or compare product opportunities, features, PRD requirements, backlog items, roadmap candidates, or initiatives using RICE, impact-effort, confidence, reach, value, effort, risk, or tradeoff analysis. Trigger on phrases like "prioritize these features", "rank this backlog", "RICE score", "impact effort matrix", "what should we build first", "compare these initiatives", or "stack rank product bets". Do NOT trigger for a time-based roadmap (use roadmap), writing or reviewing one PRD (use prd-writer or prd-review), turning a PRD into an agentic plan (use prd-to-plan), or analyzing experiment results (use ab-testing or experimentation skills).

产品经理
★ 1
weisberg
weisberg/agile_agentic_analytics

prd-writer

Use this skill whenever the user wants to write, draft, create, or scaffold a PRD (Product Requirements Document), spec, product brief, one-pager, or "working backwards" PR/FAQ from an idea, rough notes, discovery inputs, or an existing partial draft that needs authoring. Trigger on phrases like "write a PRD", "draft a spec", "product doc for X", "one-pager", "PR/FAQ", "feature brief", or when the user describes a feature/product idea and asks for it to be turned into a written requirements document. Do NOT trigger for critique or approval-readiness review of an existing PRD (use prd-review), engineering design docs, RFCs, ADRs, prioritization, roadmaps, or technical architecture documents. The output of this skill is always a markdown file (or section thereof) that a real product team could ship from.

产品经理Skill与智能体开发
★ 1
weisberg
weisberg/agile_agentic_analytics

prd-to-plan

Use this skill when the user has a PRD (Product Requirements Document), spec, or product brief and wants to turn it into an executable plan for agentic development — a plan that AI coding agents (Claude Code, sub-agents, orchestrators) can actually run. Trigger on phrases like "turn this PRD into a plan", "agentic plan", "execution plan", "task graph", "break this down for Claude Code", "decompose this spec", "build plan", "implementation plan from PRD", "scrum-master plan", or when the user provides a PRD/spec and asks "what's next" or "how do we build this with agents". The output is always a structured `PLAN.md` artifact with phases, tasks, dependencies, validation gates, sub-agent assignments, and context bundles. Do NOT trigger for: writing the PRD itself (use prd-writer), pure engineering design / RFC / ADR (architecture is a separate artifact), or generic project management plans without an agentic execution model.

产品经理Skill与智能体开发
★ 1
weisberg
weisberg/agile_agentic_analytics

prd-review

Use this skill when the user has an existing PRD, product spec, one-pager, or PR/FAQ and wants critique, approval-readiness review, quality-bar scoring, required changes, or a red-team pass. Trigger on phrases like "review this PRD", "critique my product spec", "is this PRD ready", "PRD quality bar", "red-team this requirements doc", "find gaps in this PR/FAQ", or "what would block approval". Do NOT trigger for drafting a new PRD from an idea (use prd-writer), converting an approved PRD into an agentic implementation plan (use prd-to-plan), building a roadmap (use roadmap), or ranking multiple initiatives (use prioritization).

产品经理
★ 1