[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GK5CCXJM5FF0MATHBEPTW2":3,"skill-same:01M6GK5CCXJM5FF0MATHBEPTW2":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":6,"updatedAt":64,"install":65,"resources":77},"01M6GK5CCXJM5FF0MATHBEPTW2","conflict-resolution",null,"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\u002Fsuperseded', '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.","weisberg\u002Fagile_agentic_analytics","weisberg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5054710?v=4","01M6GK0MXK350SV8PMZ0D040SB","Brian Weisberg","01M6GK0N2F8X600FCTKCB3X2ZF",1,"MIT","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fknowledge-base\u002Fskills\u002Fconflict-resolution\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"conflict resolution","resolution","conflict","claim","true","enrich","with","duplicate","rewrite","trigger","false","workflow","route","use","kb","sweep","page","Bash","health","provenance","2026-11-10 10:12:30",false,"---\nname: conflict-resolution\nversion: 0.2.0\ndescription: >-\n  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\u002Fsuperseded', '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.\ntriggers:\n  - \"resolve conflicting facts\"\n  - \"contradiction in the kb\"\n  - \"this kb claim is stale\"\n  - \"merge duplicate entities\"\nallowed-tools:\n  - Read\n  - Write\n  - Edit\n  - Bash\n  - Grep\n  - Glob\ndisable-model-invocation: false\nmutating: true\n---\n\n# Conflict Resolution\n\n## Contract\n\n- Contradictions are preserved with provenance until resolved.\n- Resolution states distinguish superseded, disputed, merged, and unresolved.\n- The current State section reflects best understanding and remaining uncertainty.\n- Mutating skill: it may rewrite State\u002Ftimeline sections, but it must not erase dissenting evidence without recording the resolution basis.\n\n## Intake And Modes\n\n- Treat `$ARGUMENTS` as the conflicting pages, claims, entities, or duplicate records to reconcile.\n- Quick mode: identify the conflict and return a resolution recommendation without writing.\n- Standard mode: resolve a bounded page\u002Fentity conflict with citations and validation.\n- Deep mode: merge duplicate entities or reconcile a multi-page stale-claim cluster.\n- Use `ask-user` when both claims are plausible and the resolution depends on user intent or preferred taxonomy.\n\n## Evidence Requirements\n\n- Inspect every cited source, source date, page timeline, and related entity page before resolving.\n- Check whether the conflict is scope-based, time-based, source-quality-based, or a true contradiction.\n\n## Workflow\n\n- Identify the conflicting claims and their sources\u002Fdates.\n- Assess recency, source quality, directness, and scope.\n- Choose a resolution: update, mark disputed, split entities, merge duplicates, or `ask-user`.\n- Rewrite State and timeline with citations; add a review date for anything unresolved.\n- Run `graph-audit` and `citation-audit` after edits.\n\n## Operating System Backing\n\nThis skill is backed by the shared deterministic KB operations harness. Use these commands for audits, CI fixtures, and repeatable agent runs:\n\n- `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fkb_ops.py\" graph-audit`\n- `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fkb_ops.py\" citation-audit`\n\n\n## Output Format\n\n- CONFLICT RESOLUTION\n- Status: `DONE`, `DONE_WITH_CONCERNS`, `BLOCKED`, or `NEEDS_CONTEXT`.\n- Claims, sources, decision, page updates, unresolved items with review dates.\n- Artifact path: updated page path(s), plus optional `reports\u002F\u003CYYYYMMDD>-conflict-resolution.md` for broad reconciliations.\n\n## Anti-Patterns\n\n- Deleting the losing claim without provenance.\n- Flattening genuine uncertainty into false certainty.\n","# Conflict Resolution\n\n## Contract\n\n- Contradictions are preserved with provenance until resolved.\n- Resolution states distinguish superseded, disputed, merged, and unresolved.\n- The current State section reflects best understanding and remaining uncertainty.\n- Mutating skill: it may rewrite State\u002Ftimeline sections, but it must not erase dissenting evidence without recording the resolution basis.\n\n## Intake And Modes\n\n- Treat `$ARGUMENTS` as the conflicting pages, claims, entities, or duplicate records to reconcile.\n- Quick mode: identify the conflict and return a resolution recommendation without writing.\n- Standard mode: resolve a bounded page\u002Fentity conflict with citations and validation.\n- Deep mode: merge duplicate entities or reconcile a multi-page stale-claim cluster.\n- Use `ask-user` when both claims are plausible and the resolution depends on user intent or preferred taxonomy.\n\n## Evidence Requirements\n\n- Inspect every cited source, source date, page timeline, and related entity page before resolving.\n- Check whether the conflict is scope-based, time-based, source-quality-based, or a true contradiction.\n\n## Workflow\n\n- Identify the conflicting claims and their sources\u002Fdates.\n- Assess recency, source quality, directness, and scope.\n- Choose a resolution: update, mark disputed, split entities, merge duplicates, or `ask-user`.\n- Rewrite State and timeline with citations; add a review date for anything unresolved.\n- Run `graph-audit` and `citation-audit` after edits.\n\n## Operating System Backing\n\nThis skill is backed by the shared deterministic KB operations harness. Use these commands for audits, CI fixtures, and repeatable agent runs:\n\n- `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fkb_ops.py\" graph-audit`\n- `python3 \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fkb_ops.py\" citation-audit`\n\n\n## Output Format\n\n- CONFLICT RESOLUTION\n- Status: `DONE`, `DONE_WITH_CONCERNS`, `BLOCKED`, or `NEEDS_CONTEXT`.\n- Claims, sources, decision, page updates, unresolved items with review dates.\n- Artifact path: updated page path(s), plus optional `reports\u002F\u003CYYYYMMDD>-conflict-resolution.md` for broad reconciliations.\n\n## Anti-Patterns\n\n- Deleting the losing claim without provenance.\n- Flattening genuine uncertainty into false certainty.\n",{"name":5,"version":44,"mutating":45,"triggers":46,"description":7,"allowed-tools":51,"disable-model-invocation":40},"0.2.0",true,[47,48,49,50],"resolve conflicting facts","contradiction in the kb","this kb claim is stale","merge duplicate entities",[52,53,54,36,55,56],"Read","Write","Edit","Grep","Glob","main","8d9ce3e8c80ddfea03af44bb5b900afc16b07c19","plugins\u002Fknowledge-base\u002Fskills\u002Fconflict-resolution",0,"https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics","https:\u002F\u002Fgithub.com\u002Fweisberg","www.betafactory.com","2026-11-11 22:15:54",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":45},[67,70,73],{"tool":68,"command":69},"npx","npx skills add weisberg\u002Fagile_agentic_analytics --skill conflict-resolution",{"tool":71,"command":72},"bunx","bunx skills add weisberg\u002Fagile_agentic_analytics --skill conflict-resolution",{"tool":74,"command":75},"pnpm","pnpm dlx skills add weisberg\u002Fagile_agentic_analytics --skill conflict-resolution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fknowledge-base\u002Fskills\u002Fconflict-resolution\u002FSKILL.md",[],[79,98,124,140,165,184],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":90,"publishedAt":39},"01M6GKH0CNX0V8JYCFTFT0C8TJ","minimal-skill","Minimal shared skill fixture for marketplace renderer and validator examples.","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fminimal-plugin\u002Fskills\u002Fminimal-skill\u002FSKILL.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[91,92,93,94,95,29,96,97],"minimal","minimal skill","shared","examples","fixture","marketplace","shared skill",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":109,"publishedAt":39},"01M6GKGW83KH0GN15MQGXM4596","roadmap","Use this skill when the user wants a product roadmap, initiative sequencing, Now\u002FNext\u002FLater 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\u002Franking a set of options without a time horizon (use prioritization).","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-manager\u002Fskills\u002Froadmap\u002FSKILL.md",[104],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[100,110,111,112,113,114,115,116,28,117,23,118,119,120,32,121,29,122,36,123],"writer","SET","do","translation","theme","time","backlog","ranking","strategy","map","now","sequencing","agentic","scoring",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":39},"01M6GKGQTF57NFBDM5NZ89CV06","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).","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-manager\u002Fskills\u002Fprioritization\u002FSKILL.md",[130],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[126,110,112,132,115,116,28,133,23,134,135,32,29,100,122,36,136,137,138,139],"risk","testing","writing","impact","requirements","analysis","compare","review",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":148,"publishedAt":39},"01M6GKGHEHWG9PF8EZHC7F1R21","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\u002FFAQ 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\u002FFAQ\", \"feature brief\", or when the user describes a feature\u002Fproduct 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.","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-manager\u002Fskills\u002Fprd-writer\u002FSKILL.md",[146,147],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[110,149,150,151,152,29,153,154,155,156,139,157,158,126,159,160,161,162,163,164],"prd writer","prd","brief","design","product brief","documents","team","architecture","create","notes","critique","product","markdown","write","authoring","doc",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":173,"publishedAt":39},"01M6GKGBFB5FMNWY3TH3TDMMKR","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\u002Fspec 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 \u002F RFC \u002F ADR (architecture is a separate artifact), or generic project management plans without an agentic execution model.","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-manager\u002Fskills\u002Fprd-to-plan\u002FSKILL.md",[171,172],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[174,175,150,110,176,151,177,178,179,152,134,29,153,122,180,181,156,182,183,160],"plan","prd to plan","ai coding agents","agentic development","model","project","code","tasks","artifact","next",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":191,"publishedAt":39},"01M6GKG6WJ5ZPAR121DC1GBR70","prd-review","Use this skill when the user has an existing PRD, product spec, one-pager, or PR\u002FFAQ 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\u002FFAQ\", 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).","https:\u002F\u002Fgithub.com\u002Fweisberg\u002Fagile_agentic_analytics\u002Fblob\u002Fmain\u002Fplugins\u002Fproduct-manager\u002Fskills\u002Fprd-review\u002FSKILL.md",[190],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},[139,192,150,110,193,112,194,195,28,117,23,32,29,100,122,36,136,155,123,126],"prd review","red-team","ready","pr"]