[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E8GARXPM7XM8FFJ0P5ASJX":3,"skill-same:01M7E8GARXPM7XM8FFJ0P5ASJX":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7E8GARXPM7XM8FFJ0P5ASJX","ln-24-architecture-decision-recorder",null,"Records one architecture decision with alternatives, consequences and status; does not design the whole system.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Farchitecture\u002Fln-24-architecture-decision-recorder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ln-24-architecture-decision-recorder\ndescription: \"Records one architecture decision with alternatives, consequences and status; does not design the whole system.\"\nsource: \"https:\u002F\u002Fgithub.com\u002Flevnikolaevich\u002Fclaude-code-skills\"\nsource_repository: \"levnikolaevich\u002Fclaude-code-skills\"\nsource_path: \"plugins\u002Farchitecture-suite\u002Fskills\u002Fln-24-architecture-decision-recorder\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n\n# Architecture Decision Recorder\n\n**Goal:** Preserve the context, forces, alternatives, decision, and consequences of one architecturally significant choice in a compact durable record. Change only approved decision documentation; do not design the whole system, approve a decision silently, delete history, audit code, or implement the choice.\n\n**Execution contract:** The checklist defines completion. Track each item internally as `PENDING`, `PROVEN` with evidence, `CLEARED` with evidence its condition is absent, or `UNPROVEN` with a gap; reading, delegation, or tool failure is not proof. Reconcile after each section. Before returning, resolve all `PENDING`, count only `PROVEN` and `CLEARED`, and apply verdict and approval rules to every gap.\nPreserve intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. Scale depth to material risk without skipping checks. Preserve dependency and safety order; otherwise choose an appropriate verification method.\nAccept equivalent user or repository evidence; no other skill, named artifact, or complete lifecycle is required. Preserve source requirement and decision IDs. Bind reused evidence to relevant source versions, dirty changes, configuration, and environment; invalidate only affected claims.\nOn continuation, reconcile task, authorization, current state, and unresolved evidence. For long work, return a compact continuation record or update an already authorized artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and external-action authority.\nPrepare authorized work before required approval. If blocked by an instruction, cite its exact source and unresolved boundary; do not invent approval gates from caution.\n\n\n## Tool Routing\n\n| Need | Preferred capability | Fallback |\n|---|---|---|\n| Existing decision convention | Repository search and direct document reads | Use the default path and compact format |\n| Decision drivers | Requirements, architecture artifacts, implementation evidence, and stakeholder statements | Mark unsupported drivers `UNKNOWN` |\n| Alternatives and external claims | Repository evidence plus current official sources | Mark time-sensitive claims `UNVERIFIED` |\n| Sequence and supersession | Existing filenames, indexes, and decision links | Return `BLOCKED` rather than reuse a number |\n| Document mutation | Minimal patch to one approved decision record and necessary supersession links | Return `BLOCKED` if authority or path is unclear |\n\nOne record captures one decision. If the request contains independent decisions with different drivers or lifecycles, split them only with explicit approval.\n\n## Artifact Rules\n\n- Reuse the repository's established ADR convention when one exists.\n- Otherwise use `docs\u002Farchitecture\u002Fdecisions\u002FNNNN-\u003Cslug>.md` with the next unused monotonic number.\n- Never renumber, delete, or rewrite the decision and rationale of historical records. Permit scoped status and supersession-link updates under the rules below; distinguish evolving proposed drafts from accepted history.\n- Default a new record to `Proposed`.\n- Use `Accepted` only after explicit confirmation from an authorized decision-maker.\n- A proposed replacement links to the current decision without changing its effective status. Mark the old record `Superseded` and link both directions only after the replacement is explicitly accepted; preserve historical content.\n- Keep the record short enough to review as a single decision.\n- Preserve the rationale a future maintainer needs to reconsider it safely.\n- Label retrospective records explicitly; do not imply that documentation created after implementation was prior approval.\n- Separate evidence needed before acceptance from monitoring required after adoption.\n- Prefer stable repository references over conversation, branch-local, or ephemeral links.\n\n## Checklist\n\n### 1. Establish the Decision Contract\n\n- [ ] Resolve the exact decision, scope, owner or deciders, affected system, and why the choice is architecturally significant.\n- [ ] Read repository instructions, Git state, and existing decision conventions.\n- [ ] Search for duplicate, conflicting, deprecated, or superseding decisions before allocating a new record.\n- [ ] Confirm the request is one decision rather than a broad design or implementation plan.\n- [ ] Resolve the approved status; default to `Proposed` when acceptance is not explicit.\n\n### 2. Gather Context and Forces\n\n- [ ] State the current context and problem in value-neutral language.\n- [ ] Extract business drivers, quality attributes, constraints, assumptions, and decision horizon from available evidence.\n- [ ] Identify affected boundaries, contracts, data, security, operations, cost, ownership, and migration implications.\n- [ ] Separate present facts from forecasts and preferences.\n- [ ] Record contradictions or missing evidence that could change the choice.\n\n### 3. Evaluate Alternatives\n\n- [ ] Include the status quo and the simplest credible option unless they are demonstrably infeasible.\n- [ ] For an open choice, compare materially different credible alternatives; for retrospective records, include only evidenced historical options and mark missing rationale unknown.\n- [ ] Compare options against the same drivers: correctness, quality targets, complexity, reversibility, cost, operations, team fit, and evolution.\n- [ ] State why each rejected alternative loses in this context without claiming universal inferiority.\n- [ ] Record sensitivity or review triggers that would make a rejected option preferable later.\n\n### 4. Record the Decision\n\n- [ ] Write title, status, date, deciders or owner, context, drivers, considered options, decision, consequences, validation, and review triggers.\n- [ ] State the decision in active, testable language and name what remains deliberately undecided.\n- [ ] Record positive, negative, and neutral consequences plus accepted risks.\n- [ ] Link affected requirements, designs, diagrams, interfaces, migration documents, or issues by stable repository reference.\n- [ ] Apply the Artifact Rules for proposed or accepted supersession; verify links and preserve prior rationale.\n\n### 5. Validate and Report\n\n- [ ] Confirm the record contains one decision and can be understood without conversation history.\n- [ ] Confirm consequential claims have evidence or labelled assumptions\u002Funknowns with validation actions; never invent historical rationale or rejected alternatives for a retrospective record.\n- [ ] Confirm `Accepted` was not assigned without explicit authority.\n- [ ] Identify the requirements, interfaces, and downstream decisions affected by this decision or its supersession; preserve the accepted\u002Fproposed distinction and historical rationale.\n- [ ] Use `RECORDED` when the record and status are valid; use `INCOMPLETE` when material context or required acceptance authority remains unresolved; a complete explicitly Proposed record does not require acceptance to be `RECORDED`; use `BLOCKED` for ambiguous scope, unsafe numbering, conflicting ownership, or no writable destination.\n\n## Self-Check\n\n- [ ] **Reconcile before returning.** Check item-level evidence, requirement coverage, contradictions, scope, verdict, and applicable cleanup. Correct the report or authorized artifacts. Reuse valid evidence; do not automatically rescan the repository or rerun successful commands. Repeat checks only for relevant changes, failures, or unresolved evidence. Disclose remaining gaps.\n\n## Output Contract\n\nReport in the user's language, in this order; retain all five fields and state each fact once. Small results may use one line per field; omit empty tables and do not copy linked artifacts:\n\n1. **Result:** Skill-specific verdict and supported outcome.\n2. **Scope:** Reviewed\u002Fchanged scope, exclusions, baseline, and material assumptions.\n3. **Evidence:** Skill-specific fields below; distinguish facts, inferences, and unverified claims. Link artifacts; use tables when useful.\n4. **Verification:** Checks\u002Fresults, unavailable evidence, and applicable cleanup\u002Fexternal state.\n5. **Completion:** `Checklist: X\u002FY complete`; `Incomplete: None` or each `UNPROVEN` item's reason, outcome impact, and exact next action; residual risks and required decisions.\n\n**Skill-specific evidence:** Artifact path, decision identity\u002Fstatus\u002Fowner, selected option, alternatives, consequences, evidence, and acceptance\u002Fvalidation needs. Report links or status changes to historical records, preserving their rationale; identify unresolved choices and review triggers without implying acceptance of a proposal.\n","# Architecture Decision Recorder\n\n**Goal:** Preserve the context, forces, alternatives, decision, and consequences of one architecturally significant choice in a compact durable record. Change only approved decision documentation; do not design the whole system, approve a decision silently, delete history, audit code, or implement the choice.\n\n**Execution contract:** The checklist defines completion. Track each item internally as `PENDING`, `PROVEN` with evidence, `CLEARED` with evidence its condition is absent, or `UNPROVEN` with a gap; reading, delegation, or tool failure is not proof. Reconcile after each section. Before returning, resolve all `PENDING`, count only `PROVEN` and `CLEARED`, and apply verdict and approval rules to every gap.\nPreserve intent, scope, and existing authorization. Continue authorized work; ask only for consequential unresolved choices or required external approval. Scale depth to material risk without skipping checks. Preserve dependency and safety order; otherwise choose an appropriate verification method.\nAccept equivalent user or repository evidence; no other skill, named artifact, or complete lifecycle is required. Preserve source requirement and decision IDs. Bind reused evidence to relevant source versions, dirty changes, configuration, and environment; invalidate only affected claims.\nOn continuation, reconcile task, authorization, current state, and unresolved evidence. For long work, return a compact continuation record or update an already authorized artifact; read-only skills do not persist it. Distinguish artifact readiness, verified behavior, and external-action authority.\nPrepare authorized work before required approval. If blocked by an instruction, cite its exact source and unresolved boundary; do not invent approval gates from caution.\n\n\n## Tool Routing\n\n| Need | Preferred capability | Fallback |\n|---|---|---|\n| Existing decision convention | Repository search and direct document reads | Use the default path and compact format |\n| Decision drivers | Requirements, architecture artifacts, implementation evidence, and stakeholder statements | Mark unsupported drivers `UNKNOWN` |\n| Alternatives and external claims | Repository evidence plus current official sources | Mark time-sensitive claims `UNVERIFIED` |\n| Sequence and supersession | Existing filenames, indexes, and decision links | Return `BLOCKED` rather than reuse a number |\n| Document mutation | Minimal patch to one approved decision record and necessary supersession links | Return `BLOCKED` if authority or path is unclear |\n\nOne record captures one decision. If the request contains independent decisions with different drivers or lifecycles, split them only with explicit approval.\n\n## Artifact Rules\n\n- Reuse the repository's established ADR convention when one exists.\n- Otherwise use `docs\u002Farchitecture\u002Fdecisions\u002FNNNN-\u003Cslug>.md` with the next unused monotonic number.\n- Never renumber, delete, or rewrite the decision and rationale of historical records. Permit scoped status and supersession-link updates under the rules below; distinguish evolving proposed drafts from accepted history.\n- Default a new record to `Proposed`.\n- Use `Accepted` only after explicit confirmation from an authorized decision-maker.\n- A proposed replacement links to the current decision without changing its effective status. Mark the old record `Superseded` and link both directions only after the replacement is explicitly accepted; preserve historical content.\n- Keep the record short enough to review as a single decision.\n- Preserve the rationale a future maintainer needs to reconsider it safely.\n- Label retrospective records explicitly; do not imply that documentation created after implementation was prior approval.\n- Separate evidence needed before acceptance from monitoring required after adoption.\n- Prefer stable repository references over conversation, branch-local, or ephemeral links.\n\n## Checklist\n\n### 1. Establish the Decision Contract\n\n- [ ] Resolve the exact decision, scope, owner or deciders, affected system, and why the choice is architecturally significant.\n- [ ] Read repository instructions, Git state, and existing decision conventions.\n- [ ] Search for duplicate, conflicting, deprecated, or superseding decisions before allocating a new record.\n- [ ] Confirm the request is one decision rather than a broad design or implementation plan.\n- [ ] Resolve the approved status; default to `Proposed` when acceptance is not explicit.\n\n### 2. Gather Context and Forces\n\n- [ ] State the current context and problem in value-neutral language.\n- [ ] Extract business drivers, quality attributes, constraints, assumptions, and decision horizon from available evidence.\n- [ ] Identify affected boundaries, contracts, data, security, operations, cost, ownership, and migration implications.\n- [ ] Separate present facts from forecasts and preferences.\n- [ ] Record contradictions or missing evidence that could change the choice.\n\n### 3. Evaluate Alternatives\n\n- [ ] Include the status quo and the simplest credible option unless they are demonstrably infeasible.\n- [ ] For an open choice, compare materially different credible alternatives; for retrospective records, include only evidenced historical options and mark missing rationale unknown.\n- [ ] Compare options against the same drivers: correctness, quality targets, complexity, reversibility, cost, operations, team fit, and evolution.\n- [ ] State why each rejected alternative loses in this context without claiming universal inferiority.\n- [ ] Record sensitivity or review triggers that would make a rejected option preferable later.\n\n### 4. Record the Decision\n\n- [ ] Write title, status, date, deciders or owner, context, drivers, considered options, decision, consequences, validation, and review triggers.\n- [ ] State the decision in active, testable language and name what remains deliberately undecided.\n- [ ] Record positive, negative, and neutral consequences plus accepted risks.\n- [ ] Link affected requirements, designs, diagrams, interfaces, migration documents, or issues by stable repository reference.\n- [ ] Apply the Artifact Rules for proposed or accepted supersession; verify links and preserve prior rationale.\n\n### 5. Validate and Report\n\n- [ ] Confirm the record contains one decision and can be understood without conversation history.\n- [ ] Confirm consequential claims have evidence or labelled assumptions\u002Funknowns with validation actions; never invent historical rationale or rejected alternatives for a retrospective record.\n- [ ] Confirm `Accepted` was not assigned without explicit authority.\n- [ ] Identify the requirements, interfaces, and downstream decisions affected by this decision or its supersession; preserve the accepted\u002Fproposed distinction and historical rationale.\n- [ ] Use `RECORDED` when the record and status are valid; use `INCOMPLETE` when material context or required acceptance authority remains unresolved; a complete explicitly Proposed record does not require acceptance to be `RECORDED`; use `BLOCKED` for ambiguous scope, unsafe numbering, conflicting ownership, or no writable destination.\n\n## Self-Check\n\n- [ ] **Reconcile before returning.** Check item-level evidence, requirement coverage, contradictions, scope, verdict, and applicable cleanup. Correct the report or authorized artifacts. Reuse valid evidence; do not automatically rescan the repository or rerun successful commands. Repeat checks only for relevant changes, failures, or unresolved evidence. Disclose remaining gaps.\n\n## Output Contract\n\nReport in the user's language, in this order; retain all five fields and state each fact once. Small results may use one line per field; omit empty tables and do not copy linked artifacts:\n\n1. **Result:** Skill-specific verdict and supported outcome.\n2. **Scope:** Reviewed\u002Fchanged scope, exclusions, baseline, and material assumptions.\n3. **Evidence:** Skill-specific fields below; distinguish facts, inferences, and unverified claims. Link artifacts; use tables when useful.\n4. **Verification:** Checks\u002Fresults, unavailable evidence, and applicable cleanup\u002Fexternal state.\n5. **Completion:** `Checklist: X\u002FY complete`; `Incomplete: None` or each `UNPROVEN` item's reason, outcome impact, and exact next action; residual risks and required decisions.\n\n**Skill-specific evidence:** Artifact path, decision identity\u002Fstatus\u002Fowner, selected option, alternatives, consequences, evidence, and acceptance\u002Fvalidation needs. Report links or status changes to historical records, preserving their rationale; identify unresolved choices and review triggers without implying acceptance of a proposal.\n",{"name":5,"source":24,"license":15,"description":7,"imported_at":25,"source_path":26,"source_repository":27},"https:\u002F\u002Fgithub.com\u002Flevnikolaevich\u002Fclaude-code-skills","2026-09-20","plugins\u002Farchitecture-suite\u002Fskills\u002Fln-24-architecture-decision-recorder\u002FSKILL.md","levnikolaevich\u002Fclaude-code-skills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Farchitecture\u002Fln-24-architecture-decision-recorder","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ln-24-architecture-decision-recorder",{"tool":40,"command":41},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ln-24-architecture-decision-recorder",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill ln-24-architecture-decision-recorder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Farchitecture\u002Fln-24-architecture-decision-recorder\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":56},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":56},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":56},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":56},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":56},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]