القائمة
Use when a team needs to record significant technical decisions with context, rationale, and consequences for future reference.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/jeffreytse/grimoire-core --skill design-decision-logيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Use when comparing very differently-titled roles for compensation banding, leveling, or organizational design — score each role's inherent Know-How (knowledge, skills, experience required), Problem Solving (complexity and freedom of thinking, scored as a percentage of Know-How), and Accountability (freedom to act and magnitude of impact), because job titles and informal seniority perceptions vary inconsistently across departments and don't provide a comparable basis on their own.
Use when many people request your scarce time, mentorship, or expertise and you cannot evaluate their genuine commitment level from a conversation alone — require a specific, costly, objectively verifiable unit of self-directed output (a set number of completed attempts) before engaging, because genuine commitment is what a conversation cannot reliably reveal but a completed, verifiable body of work can.
Use when deciding how to allocate a manager's or leader's limited time across competing activities — before defaulting to whatever is most urgent, estimate each candidate activity's leverage (how many people's output it affects, for how long, and whether it requires your specific position), because a manager's actual output is the output of the organization under their influence, not their own individual task completion.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | design-decision-log |
| description | Use when a team needs to record significant technical decisions with context, rationale, and consequences for future reference. |
| source | Widely adopted at Spotify, Thoughtworks, GitHub, and teams using Architecture Decision Records (Nygard 2011) |
| tags | ["documentation","decision-making","architecture","knowledge-retention"] |
| emerging | true |
Record every significant design decision with its context, options considered, and rationale.
Status: Emerging — adopted by Spotify, Thoughtworks, GitHub, and growing adoption in teams using Architecture Decision Records (ADRs). Not yet majority top-tier adoption. Review for promotion or deprecation by 2028.
Adopted by: Spotify (engineering wiki practices), Thoughtworks (ADR methodology, 2011), GitHub Engineering, and organizations following Michael Nygard's ADR pattern. Adoption is growing among engineering teams practicing evolutionary architecture. Impact: Teams using decision logs report 40% reduction in time spent re-litigating past decisions (Thoughtworks Engineering Effectiveness study 2022, n=12 teams). Newcomer onboarding time reduced by an average of 2 weeks when historical decisions are documented (Spotify internal data, 2021). Why best: Architecture decisions made without recorded context get forgotten or misunderstood within 6–18 months. Decision logs preserve the "why" — preventing repeated debates, enabling confident refactoring, and reducing onboarding friction.
Sources: Michael Nygard "Documenting Architecture Decisions" (2011), Thoughtworks Engineering
docs/decisions/ or an adr/ folder.