architecture_design_lite

Create a single-file Architecture Delta Document with context, changes, and ADR rationale.

Updated Aug 23, 2026

Search Tags:#architecture #documentation #adr #software-engineering #design-review #architecture-delta

Ready to run

npx skills add https://github.com/ukrsite/kiro-workflows --skill architecture-design-lite

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture_design_lite
Source: https://github.com/ukrsite/kiro-workflows/tree/main/skills/sdlc/architecture_design_lite
Command: npx skills add https://github.com/ukrsite/kiro-workflows --skill architecture-design-lite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This lightweight guide defines a zero-preamble Architecture Delta Document that codifies architectural changes in a single-file ADR, ensuring concise, auditable design decisions.

Core Features & Use Cases

Single-file delta: captures context, changes, and rationale in one place for quick reviews.
Strict output protocol: enforces deterministic structure and avoids extraneous content.
Use Case: teams performing architecture reviews, refactoring planning, or onboarding new engineers benefit from a consistent ADR format.

Quick Start

Provide a complete Architecture Delta Document for the current feature by outlining context, delta changes, API/infrastructure, and ADR details in a single-file format.

Frequently Asked Questions about architecture_design_lite

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

FAQPage Schema

What is an Architecture Delta Document and when do I need one?▼

An Architecture Delta Document is a single-file ADR format that codifies architectural changes by capturing context, delta changes, and rationale. You need it during architecture reviews, refactoring planning, or onboarding to ensure concise, auditable design decisions.

How do I document architectural changes for a design review?▼

To document architectural changes for a design review, create a single-file delta outlining context, data changes, API or infrastructure impacts, and ADR rationale. This enforces a deterministic structure, ensuring traceability and governance across multiple tech stacks.

Can I use a single-file ADR format for refactoring planning across different tech stacks?▼

Yes, this single-file ADR format applies to engineering teams performing refactoring planning across multiple tech stacks. It enforces a strict output protocol with context, data changes, API or infrastructure details, and ADR rationale, ensuring consistent governance.

What's the best way to capture API and infrastructure changes in an ADR?▼

The best way to capture API and infrastructure changes in an ADR is using a structured delta format. It enforces deterministic structure by separating context, data changes, API or infrastructure impacts, and rationale in one file, avoiding extraneous content.

Does this architecture delta format require any specific dependencies or components?▼

No, this zero-bloat architecture delta format requires no specific dependencies or components. It provides a lightweight guide that enforces a strict output protocol to capture context, changes, and rationale in a single-file ADR.

Why does my architecture documentation include unnecessary preamble content?▼

Your architecture documentation includes unnecessary preamble because it lacks a strict output protocol. Using a zero-preamble Architecture Delta Document enforces a deterministic structure, capturing only context, changes, and rationale without extraneous content.