Create standardized architecture decision records within a structured wiki-zone hierarchy.
npx skills add https://github.com/zoraxl/team-brain --skill wiki-adr
Please help me install this Agent Skill. Skill: wiki-adr Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/wiki-adr Command: npx skills add https://github.com/zoraxl/team-brain --skill wiki-adr
This skill solves the problem of fragmented or undocumented technical decisions by providing a structured, consistent way to capture architecture choices that emerge during implementation or review.
Use the wiki-adr skill to create a new decision record for the recent choice to migrate the authentication service to the platform namespace.
High-intent search queries and answers about installing and using this skill.
You can document ad-hoc architecture decisions by generating standardized Architecture Decision Records that capture the Context, Decision, and Consequences of implementation choices, infrastructure shifts, or dependency updates.
The best way to maintain a centralized index for architecture decision records is to enforce a wiki-zone boundary model that links new decisions to an existing wiki index, ensuring ad-hoc technical choices remain discoverable and durable.
Wiki-zone organization for technical governance documentation works by enforcing namespace boundary rules, ensuring that each architecture decision record is filed under the correct platform category or namespace.
Yes, you can use this to record infrastructure shifts and dependency updates, as it standardizes the creation of architecture decision records specifically for ad-hoc implementation choices that emerge during technical review.
Creating an architecture decision record requires standardized fields including Context, Decision, and Consequences to ensure that technical choices are captured consistently and linked to the wiki logs.
You need a standardized format for capturing architecture decisions when fragmented or undocumented technical choices emerge during implementation, requiring structured documentation to maintain governance and discoverability.
zoraxlStandardize operational runbooks and infrastructure documentation across wiki namespace zones.
DhumitechDocument architecture decisions with standardized ADR templates and lifecycle statuses.
JustineDevsManage a local markdown knowledge base with keyword and tag indexing.
cyhinverseCapture and justify architectural decisions using ADR templates and decision records.
