[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KNZ030WVTDD67T4TDA0H9V":3,"skill-same:01M6KNZ030WVTDD67T4TDA0H9V":69},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6KNZ030WVTDD67T4TDA0H9V","speckit-sync-conflicts",null,"Detect and surface conflicts between specs or between specs and design docs","AI-native-Systems-Research\u002Fai-native-storage-certus","AI-native-Systems-Research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F270755458?v=4","01M6KKQWSJX0D4X33E0KKSR4WM","AI-native Systems Research","01M6KKQWXTKR6MYVQMPKVJ5WD5",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fremote-lookup\u002F.claude\u002Fskills\u002Fspeckit-sync-conflicts\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"speckit sync conflicts","speckit","sync","conflicts","structure","kit","with","spec-kit","detect","design docs","commands","project","design","specify","project structure","github","docs","spec","directory","2026-11-10 10:12:30",false,"---\nname: speckit-sync-conflicts\ndescription: Detect and surface conflicts between specs or between specs and design\n  docs\ncompatibility: Requires spec-kit project structure with .specify\u002F directory\nmetadata:\n  author: github-spec-kit\n  source: sync:commands\u002Fconflicts.md\n---\n\n# Spec Sync: Detect Conflicts\n\nFind contradictions between specs, or between specs and design documents. Surface them for human resolution.\n\n## User Input\n\n$ARGUMENTS\n\n## Context\n\nRead all spec files and design documents:\n- `specs\u002F*\u002Fspec.md`\n- `docs\u002Fplans\u002F*.md` or `docs\u002Fdesign\u002F*.md`\n- Any files with \"design\" or \"plan\" in the name\n\n## Steps\n\n### 1. Extract Requirements from All Sources\n\nFor each spec, extract:\n- All FR-* requirements with full text\n- All SC-* success criteria\n- Key constraints and assumptions\n- Out of scope items\n\nFor design docs, extract:\n- Design decisions\n- Constraints\n- Behavioral specifications\n- Any \"MUST\", \"SHALL\", \"SHOULD\" statements\n\n### 2. Build Requirement Index\n\nCreate a semantic index of all requirements, keyed by:\n- Feature area (extraction, routing, register, etc.)\n- Entity type (document, transaction, row, etc.)\n- Behavior type (create, update, validate, etc.)\n\n### 3. Detect Direct Conflicts\n\nLook for contradictions:\n\n**Type 1: Same Feature, Different Behavior**\n- Spec A says \"one row per document\"\n- Spec B says \"split transactions produce multiple rows\"\n- Conflict: Row cardinality\n\n**Type 2: Obsolete Constraints**\n- Spec A says \"5 extraction fields: Date, Vendor, Total, Tax, Currency\"\n- Design doc says \"type-aware fields, 4-8 per document type\"\n- Conflict: Field count and composition\n\n**Type 3: Scope Overlap**\n- Spec A includes feature X\n- Spec B also includes feature X\n- Conflict: Unclear ownership\n\n**Type 4: Implicit Conflicts**\n- Spec A assumes auth is always valid\n- Spec B adds offline mode\n- Conflict: Assumption violated\n\n### 4. Determine Resolution Path\n\nFor each conflict:\n\n**SUPERSEDE**: Newer document replaces older\n- Check dates, version numbers\n- Design docs often supersede original specs\n- Later specs refine earlier specs\n\n**MERGE**: Combine into single authoritative source\n- When both have valid parts\n- Create unified spec\n\n**DEPRECATE**: Mark older as obsolete\n- When requirement is no longer relevant\n- Document why it was removed\n\n**HUMAN_REQUIRED**: Can't determine automatically\n- Architectural decisions\n- Trade-offs involved\n- Missing context\n\n### 5. Generate Conflict Report\n\n```markdown\n# Spec Conflict Report\n\nGenerated: [timestamp]\n\n## Summary\n\n| Conflict Type | Count |\n|---------------|-------|\n| Same Feature, Different Behavior | X |\n| Obsolete Constraints | X |\n| Scope Overlap | X |\n| Implicit Conflicts | X |\n\n## Conflicts\n\n### Conflict 1: Extraction Field Count\n\n**Sources**:\n- `specs\u002F008-field-extraction\u002Fspec.md` (FR-003)\n- `docs\u002Fplans\u002F2026-02-19-type-aware-extraction-design.md`\n\n**Description**:\nSpec 008 defines 5 fixed extraction fields for all document types.\nDesign doc introduces type-aware extraction with 4-8 fields per type.\n\n**Evidence**:\n\nFrom spec-008:\n> FR-003: System MUST extract the following fields: Date, Vendor, Total, Tax, Currency\n\nFrom design doc:\n> Document Types & Extraction Fields\n> ### Receipt\n> Fields: Date, Vendor, Total, Tax, Currency, Category\n> ### Bill\n> Fields: Date, Vendor, Description, Total, Due Date, Currency, Category\n\n**Suggested Resolution**: SUPERSEDE\n\nThe design doc (dated 2026-02-19) supersedes spec-008 for extraction fields.\nRecommend updating spec-008 to reference the design doc or incorporating\nthe type-aware fields directly.\n\n**Action Required**:\n- [ ] Mark spec-008\u002FFR-003 as superseded by design doc\n- [ ] Update spec-008 with type-aware field definitions\n- [ ] Or create new spec-013 for type-aware extraction\n\n---\n\n### Conflict 2: Register Row Cardinality\n\n[... additional conflicts ...]\n\n## Resolution Tracking\n\nTrack resolution decisions:\n\n| Conflict | Resolution | Decided By | Date |\n|----------|------------|------------|------|\n| Conflict 1 | SUPERSEDE | pending | - |\n\n## Recommendations\n\n1. Schedule a 30-min review session to resolve conflicts\n2. Consider consolidating specs 008 and design doc\n3. Add explicit \"supersedes\" metadata to specs\n```\n\n### 6. Save Report\n\nWrite to:\n- `.specify\u002Fsync\u002Fconflicts.md`\n- `.specify\u002Fsync\u002Fconflicts.json`\n\n## Conflict Resolution Commands\n\nAfter reviewing conflicts, mark resolutions:\n\n```\n\u002Fspeckit.sync.conflicts resolve 1 --supersede docs\u002Fplans\u002F2026-02-19-type-aware-extraction-design.md\n\n\u002Fspeckit.sync.conflicts resolve 2 --merge spec-011\n```\n\n## Example Usage\n\n```\n\u002Fspeckit.sync.conflicts\n\n\u002Fspeckit.sync.conflicts --include-design-docs\n\n\u002Fspeckit.sync.conflicts --spec 008\n```","# Spec Sync: Detect Conflicts\n\nFind contradictions between specs, or between specs and design documents. Surface them for human resolution.\n\n## User Input\n\n$ARGUMENTS\n\n## Context\n\nRead all spec files and design documents:\n- `specs\u002F*\u002Fspec.md`\n- `docs\u002Fplans\u002F*.md` or `docs\u002Fdesign\u002F*.md`\n- Any files with \"design\" or \"plan\" in the name\n\n## Steps\n\n### 1. Extract Requirements from All Sources\n\nFor each spec, extract:\n- All FR-* requirements with full text\n- All SC-* success criteria\n- Key constraints and assumptions\n- Out of scope items\n\nFor design docs, extract:\n- Design decisions\n- Constraints\n- Behavioral specifications\n- Any \"MUST\", \"SHALL\", \"SHOULD\" statements\n\n### 2. Build Requirement Index\n\nCreate a semantic index of all requirements, keyed by:\n- Feature area (extraction, routing, register, etc.)\n- Entity type (document, transaction, row, etc.)\n- Behavior type (create, update, validate, etc.)\n\n### 3. Detect Direct Conflicts\n\nLook for contradictions:\n\n**Type 1: Same Feature, Different Behavior**\n- Spec A says \"one row per document\"\n- Spec B says \"split transactions produce multiple rows\"\n- Conflict: Row cardinality\n\n**Type 2: Obsolete Constraints**\n- Spec A says \"5 extraction fields: Date, Vendor, Total, Tax, Currency\"\n- Design doc says \"type-aware fields, 4-8 per document type\"\n- Conflict: Field count and composition\n\n**Type 3: Scope Overlap**\n- Spec A includes feature X\n- Spec B also includes feature X\n- Conflict: Unclear ownership\n\n**Type 4: Implicit Conflicts**\n- Spec A assumes auth is always valid\n- Spec B adds offline mode\n- Conflict: Assumption violated\n\n### 4. Determine Resolution Path\n\nFor each conflict:\n\n**SUPERSEDE**: Newer document replaces older\n- Check dates, version numbers\n- Design docs often supersede original specs\n- Later specs refine earlier specs\n\n**MERGE**: Combine into single authoritative source\n- When both have valid parts\n- Create unified spec\n\n**DEPRECATE**: Mark older as obsolete\n- When requirement is no longer relevant\n- Document why it was removed\n\n**HUMAN_REQUIRED**: Can't determine automatically\n- Architectural decisions\n- Trade-offs involved\n- Missing context\n\n### 5. Generate Conflict Report\n\n```markdown\n# Spec Conflict Report\n\nGenerated: [timestamp]\n\n## Summary\n\n| Conflict Type | Count |\n|---------------|-------|\n| Same Feature, Different Behavior | X |\n| Obsolete Constraints | X |\n| Scope Overlap | X |\n| Implicit Conflicts | X |\n\n## Conflicts\n\n### Conflict 1: Extraction Field Count\n\n**Sources**:\n- `specs\u002F008-field-extraction\u002Fspec.md` (FR-003)\n- `docs\u002Fplans\u002F2026-02-19-type-aware-extraction-design.md`\n\n**Description**:\nSpec 008 defines 5 fixed extraction fields for all document types.\nDesign doc introduces type-aware extraction with 4-8 fields per type.\n\n**Evidence**:\n\nFrom spec-008:\n> FR-003: System MUST extract the following fields: Date, Vendor, Total, Tax, Currency\n\nFrom design doc:\n> Document Types & Extraction Fields\n> ### Receipt\n> Fields: Date, Vendor, Total, Tax, Currency, Category\n> ### Bill\n> Fields: Date, Vendor, Description, Total, Due Date, Currency, Category\n\n**Suggested Resolution**: SUPERSEDE\n\nThe design doc (dated 2026-02-19) supersedes spec-008 for extraction fields.\nRecommend updating spec-008 to reference the design doc or incorporating\nthe type-aware fields directly.\n\n**Action Required**:\n- [ ] Mark spec-008\u002FFR-003 as superseded by design doc\n- [ ] Update spec-008 with type-aware field definitions\n- [ ] Or create new spec-013 for type-aware extraction\n\n---\n\n### Conflict 2: Register Row Cardinality\n\n[... additional conflicts ...]\n\n## Resolution Tracking\n\nTrack resolution decisions:\n\n| Conflict | Resolution | Decided By | Date |\n|----------|------------|------------|------|\n| Conflict 1 | SUPERSEDE | pending | - |\n\n## Recommendations\n\n1. Schedule a 30-min review session to resolve conflicts\n2. Consider consolidating specs 008 and design doc\n3. Add explicit \"supersedes\" metadata to specs\n```\n\n### 6. Save Report\n\nWrite to:\n- `.specify\u002Fsync\u002Fconflicts.md`\n- `.specify\u002Fsync\u002Fconflicts.json`\n\n## Conflict Resolution Commands\n\nAfter reviewing conflicts, mark resolutions:\n\n```\n\u002Fspeckit.sync.conflicts resolve 1 --supersede docs\u002Fplans\u002F2026-02-19-type-aware-extraction-design.md\n\n\u002Fspeckit.sync.conflicts resolve 2 --merge spec-011\n```\n\n## Example Usage\n\n```\n\u002Fspeckit.sync.conflicts\n\n\u002Fspeckit.sync.conflicts --include-design-docs\n\n\u002Fspeckit.sync.conflicts --spec 008\n```",{"name":5,"metadata":43,"description":7,"compatibility":46},{"author":44,"source":45},"github-spec-kit","sync:commands\u002Fconflicts.md","Requires spec-kit project structure with .specify\u002F directory","unstable","dc564aa356769b7754391c9fa4fdaa0f179f476c","components\u002Fremote-lookup\u002F.claude\u002Fskills\u002Fspeckit-sync-conflicts",4,"https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research","https:\u002F\u002Fai-native-systems-research.github.io\u002Fai-native-systems-research\u002F","2026-11-12 06:08:32",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill speckit-sync-conflicts",{"tool":61,"command":62},"bunx","bunx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill speckit-sync-conflicts",{"tool":64,"command":65},"pnpm","pnpm dlx skills add AI-native-Systems-Research\u002Fai-native-storage-certus --skill speckit-sync-conflicts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fremote-lookup\u002F.claude\u002Fskills\u002Fspeckit-sync-conflicts\u002FSKILL.md",true,[],[70,87,103,114,129,141],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":38},"01M6KP29TWSNGADF3AJ47BR7TY","tools-spin-sync","Synchronize Spin\u002FPromela models with current source code and re-verify","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-spin-sync\u002FSKILL.md",[],[77,78,21,79,80,81,82,83,25,84,85,86],"tools spin sync","Tools","code","verify","model","models","name","re","source","source code",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":38},"01M6KP277TDY3ZAJEBP5P6MDT8","tools-spin-model","Create a new Spin\u002FPromela formal verification model for a system property","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-spin-model\u002FSKILL.md",[],[94,81,78,95,96,97,98,99,100,101,102],"tools spin model","system","formal verification","number","for","prove","new","create","verification",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":38},"01M6KP250W406CEDSF02BRXT9D","tools-creusot-install","Install the Creusot Rust verification tool","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-install\u002FSKILL.md",[],[110,111,78,112,102,113],"tools creusot install","install","rust","tool",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":38},"01M6KP22H28FQ1X0V7VJHEFWXD","tools-creusot-init","Prepare an existing Cargo project to use Creusot formal verification","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-init\u002FSKILL.md",[],[121,78,122,30,37,123,124,102,125,96,126,127,128],"tools creusot init","init","components","prepare","use","cargo","manager","Existing",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":38},"01M6KP1V506J9YM8DKKVDG1NRE","tools-creusot-coq-install","Add Coq 8.20 as an additional prover to an existing Creusot installation, for verification conditions that SMT solvers cannot discharge","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-coq-install\u002FSKILL.md",[],[136,137,111,78,98,128,138,139,102,140],"tools creusot coq install","Coq","as","installation","add",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":38},"01M6KP1PQJF3H765TYZAZ7P3EF","tools-creusot-annotate-interfaces","Formally verify a component's properties with Creusot and annotate its interface definitions","https:\u002F\u002Fgithub.com\u002FAI-native-Systems-Research\u002Fai-native-storage-certus\u002Fblob\u002Funstable\u002Fcomponents\u002Fzyre\u002F.claude\u002Fskills\u002Ftools-creusot-annotate-interfaces\u002FSKILL.md",[],[78,148,149,25,83,150,80,151,152],"tools creusot annotate interfaces","annotate","properties","component","interface"]