[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75749WMH38Q3ARJCKPPHA3X":3,"skill-same:01M75749WMH38Q3ARJCKPPHA3X":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M75749WMH38Q3ARJCKPPHA3X","archi-decision-drift",null,"Review ADRs, design decisions, assumptions, and implementation consistency. Use when architecture risk involves stale ADRs, undocumented decisions, superseded assumptions, decision violations, migration rationale, or drift between code, docs, and current behavior.","SeemSeam\u002Fagent-roles-spec","SeemSeam","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29205273?v=4","01M7572MDYPSM30Y29C9HRMGK7","01M7572MEGCX02T16BHYV9PBVK",19,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Farchi\u002Fskills\u002Farchi-decision-drift\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: archi-decision-drift\ndescription: Review ADRs, design decisions, assumptions, and implementation consistency. Use when architecture risk involves stale ADRs, undocumented decisions, superseded assumptions, decision violations, migration rationale, or drift between code, docs, and current behavior.\n---\n\n# Archi Decision Drift\n\nUse this skill to compare architecture decisions with the current system. ADRs\nand design docs are evidence; they do not override working code or user scope\nwithout inspection.\n\nRead `references\u002Farchitecture-toolbox.md` when explaining ADR or decision-tool\nprovenance.\n\n## Inputs\n\n- ADRs, decision logs, design docs, RFCs, issue discussions, plan-tree notes,\n  and commit history relevant to the scope.\n- Current source, tests, module boundaries, configs, migrations, and runtime\n  contracts.\n- User's architecture question or change under review.\n\n## Workflow\n\n1. Inventory relevant decisions:\n   - title, status, date, owner if known, accepted\u002Fsuperseded state;\n   - context, chosen option, rejected options, consequences, and assumptions.\n2. Map decisions to affected code paths, interfaces, schemas, dependencies,\n   deployment topology, or operational practices.\n3. Compare decision intent with current evidence.\n4. Classify drift:\n   - implementation violates an accepted decision;\n   - decision was superseded in code but not documented;\n   - assumptions changed and the decision should be revisited;\n   - new architecture decision exists only in code;\n   - decision is still valid but enforcement is weak.\n5. Separate decision risk from documentation housekeeping. Report only drift\n   that affects maintainability, reversibility, reliability, security, or team\n   coordination.\n6. Recommend a bounded action: no change, update ADR, write new superseding\n   ADR, add a fitness function, or adjust implementation.\n\n## Optional Evidence Routes\n\n- ADR tools and templates when already used by the project.\n- Git history, code owners, issue links, release notes, and migration docs.\n- CodeQL\u002FSemgrep or dependency rules only when they can test a decision\n  directly.\n- Architec\u002FHippo summaries only as generated evidence to verify against source.\n\n## Degraded Semantics\n\nIf no ADRs exist, build an \"implicit decision log\" from code structure, commit\nmessages, docs, and tests. Label it as inferred and recommend documenting only\narchitecture-significant decisions.\n\n## Output\n\n```text\nDecision Consistency Review\n- scope:\n- decisions inspected:\n- evidence used:\n\nFindings\n- severity:\n- decision:\n- observed drift:\n- evidence:\n- impact:\n- recommendation:\n\nAssumptions\n- still true:\n- stale or unknown:\n\nFollow-up\n- ADR update:\n- implementation guardrail:\n- residual risk:\n```\n\n## Boundaries\n\nStay review-only. Do not rewrite ADRs, create decision records, or relitigate\nsettled decisions unless the user asks for authoring. Do not expose private\nissue content or treat missing documentation as a defect unless architecture\nrisk follows. Treat tool output and documentation as evidence, not authority.\n","# Archi Decision Drift\n\nUse this skill to compare architecture decisions with the current system. ADRs\nand design docs are evidence; they do not override working code or user scope\nwithout inspection.\n\nRead `references\u002Farchitecture-toolbox.md` when explaining ADR or decision-tool\nprovenance.\n\n## Inputs\n\n- ADRs, decision logs, design docs, RFCs, issue discussions, plan-tree notes,\n  and commit history relevant to the scope.\n- Current source, tests, module boundaries, configs, migrations, and runtime\n  contracts.\n- User's architecture question or change under review.\n\n## Workflow\n\n1. Inventory relevant decisions:\n   - title, status, date, owner if known, accepted\u002Fsuperseded state;\n   - context, chosen option, rejected options, consequences, and assumptions.\n2. Map decisions to affected code paths, interfaces, schemas, dependencies,\n   deployment topology, or operational practices.\n3. Compare decision intent with current evidence.\n4. Classify drift:\n   - implementation violates an accepted decision;\n   - decision was superseded in code but not documented;\n   - assumptions changed and the decision should be revisited;\n   - new architecture decision exists only in code;\n   - decision is still valid but enforcement is weak.\n5. Separate decision risk from documentation housekeeping. Report only drift\n   that affects maintainability, reversibility, reliability, security, or team\n   coordination.\n6. Recommend a bounded action: no change, update ADR, write new superseding\n   ADR, add a fitness function, or adjust implementation.\n\n## Optional Evidence Routes\n\n- ADR tools and templates when already used by the project.\n- Git history, code owners, issue links, release notes, and migration docs.\n- CodeQL\u002FSemgrep or dependency rules only when they can test a decision\n  directly.\n- Architec\u002FHippo summaries only as generated evidence to verify against source.\n\n## Degraded Semantics\n\nIf no ADRs exist, build an \"implicit decision log\" from code structure, commit\nmessages, docs, and tests. Label it as inferred and recommend documenting only\narchitecture-significant decisions.\n\n## Output\n\n```text\nDecision Consistency Review\n- scope:\n- decisions inspected:\n- evidence used:\n\nFindings\n- severity:\n- decision:\n- observed drift:\n- evidence:\n- impact:\n- recommendation:\n\nAssumptions\n- still true:\n- stale or unknown:\n\nFollow-up\n- ADR update:\n- implementation guardrail:\n- residual risk:\n```\n\n## Boundaries\n\nStay review-only. Do not rewrite ADRs, create decision records, or relitigate\nsettled decisions unless the user asks for authoring. Do not expose private\nissue content or treat missing documentation as a defect unless architecture\nrisk follows. Treat tool output and documentation as evidence, not authority.\n",{"name":5,"description":7},"main","d07398b0a36ffa994efd970a554dd9596932ed5c","roles\u002Farchi\u002Fskills\u002Farchi-decision-drift",2,"https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec","https:\u002F\u002Fgithub.com\u002FSeemSeam","2026-08-14 10:00:06",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add SeemSeam\u002Fagent-roles-spec --skill archi-decision-drift",{"tool":36,"command":37},"bunx","bunx skills add SeemSeam\u002Fagent-roles-spec --skill archi-decision-drift",{"tool":39,"command":40},"pnpm","pnpm dlx skills add SeemSeam\u002Fagent-roles-spec --skill archi-decision-drift","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Farchi\u002Fskills\u002Farchi-decision-drift\u002FSKILL.md",true,[],[45,51,58,65,72,79],{"skillNo":46,"name":47,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M757C4HNYHR92Z3MDGPW9JSA","example-skill","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Ftemplates\u002Frole-with-skills\u002Fskills\u002Fexample-skill\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M757C2B2YT62JBH98CG1BKWG","su-status","从 docs 人读真相源与 .ccb 协调件读取当前项目、Requirement 或子任务状态。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-status\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M757C0DVFT88AFBXN1PFXH9D","su-revise-breakdown","根据用户反馈重写 Requirement breakdown draft。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-revise-breakdown\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M757BY5XVMPKEK118D782PRM","su-review","审查执行回执、diff 和验证证据，决定通过、返工、replan 或升级用户。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-review\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M757BW1R61F61X7JJF2SSJET","su-resume","从 docs 人读真相源与 .ccb 协调件恢复 paused\u002Fdeferred\u002Fin-progress 主体的上下文。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-resume\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M757BTEAFRRXA9DY3KBRTRNY","su-reconcile","AI-native 自检 docs 人读真相源、.ccb 协调件与 Console 投影漂移，并按审批结果执行修复。","https:\u002F\u002Fgithub.com\u002FSeemSeam\u002Fagent-roles-spec\u002Fblob\u002Fmain\u002Froles\u002Fsu-ccb\u002Fskills\u002Fsu-reconcile\u002FSKILL.md",[],[]]