ui-adr-author

Draft UI Architecture Decision Records using governance templates.

20|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Accelerated-Innovation/governed-ai-delivery --skill ui-adr-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-adr-author
Source: https://github.com/Accelerated-Innovation/governed-ai-delivery/tree/main/agents/codex/skills/ui/adr-author
Command: npx skills add https://github.com/Accelerated-Innovation/governed-ai-delivery --skill ui-adr-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes the creation of UI Architecture Decision Records to ensure consistent governance across UI decisions.

Core Features & Use Cases

  • Template-driven ADR creation using the governance template to ensure consistency.
  • Contextual coverage including status, context, decision, MVVM impact, consequences, and alternatives.
  • Repository alignment: ADRs are stored in docs/ui/architecture/ADR/ and reference existing accepted ADRs to prevent contradictions.

Quick Start

Identify the decision title from the user request and draft a UI ADR using the governance template located at governance/ui/templates/architecture_preflight.md and save it in docs/ui/architecture/ADR/.

Frequently Asked Questions about ui-adr-author

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a UI Architecture Decision Record that aligns with governance templates?

Store UI Architecture Decision Records in the designated repository directory, typically docs/ui/architecture/ADR/. This repository alignment prevents contradictions by ensuring new UI architecture decisions reference and exist alongside existing accepted ADRs.

Where should UI Architecture Decision Records be stored in the repository?

Store UI Architecture Decision Records in the designated repository directory, typically docs/ui/architecture/ADR/. This repository alignment prevents contradictions by ensuring new UI architecture decisions reference and exist alongside existing accepted ADRs.

How do I prevent new UI architecture decisions from contradicting previous ones?

Prevent contradictions in UI architecture decisions by referencing existing accepted ADRs within the new document. Storing all records in a centralized ADR directory and cross-referencing them ensures consistent governance and architectural alignment.

What sections are required in a UI Architecture Decision Record?

Required sections in a UI Architecture Decision Record include status, context, decision, MVVM impact, consequences, and alternatives. These sections provide contextual coverage to fully document the rationale and effects of UI architecture choices.