lightweight-architecture

Write architecture briefs, ADRs, and architecture reviews grounded in repository evidence.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/lunarmoon26/agent-skills --skill lightweight-architecture-lunarmoon26
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lightweight-architecture
Source: https://github.com/lunarmoon26/agent-skills/tree/main/skills/lightweight-architecture
Command: npx skills add https://github.com/lunarmoon26/agent-skills --skill lightweight-architecture-lunarmoon26

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Architecture documentation often becomes either a bloated template nobody reads or a stale artifact disconnected from the actual code. This Skill produces compact, evidence-backed architecture briefs, decision records, and reviews that stay synchronized with the implementation. ## Core Features & Use Cases - Architecture Briefs: Create arc42-informed compact briefs covering purpose, quality scenarios, context, building blocks, critical flows, deployment, and risks, including only relevant sections. - Architecture Decision Records: Apply a significance test to decide when an ADR is warranted, then record context, drivers, options, consequences, and confirmation checks with a proper lifecycle (proposed, accepted, superseded). - Architecture Reviews: Audit drift between code, tests, deployment, and documentation with a structured findings template citing exact artifact evidence. - Use Case: When choosing between PostgreSQL advisory locks and a Redis lease for job ownership, use this Skill to produce one concise proposed ADR with both options, tradeoffs, and a conformance check, then update the architecture summary after acceptance. ## Quick Start Use the lightweight-architecture skill to write an architecture brief for the upload service based on its current code and deployment configuration.

Frequently Asked Questions about lightweight-architecture

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

FAQPage Schema
How do I write an architecture decision record (ADR)?▼

An ADR captures one significant decision with context, decision drivers, options considered, the chosen option with rationale, positive and negative consequences, and a confirmation check. Keep one decision per record and follow the repository's existing numbering and status conventions.

When should I create an ADR versus skipping it?▼

Create an ADR when a choice affects system boundaries, quality attributes, external interfaces, major dependencies, or is expensive to reverse. Skip it for local, low-risk, reversible changes like renaming a private helper, which belong in code review instead.

What is a lightweight alternative to the full arc42 template?▼

A compact architecture brief uses arc42-informed questions but includes only relevant sections: purpose, top quality scenarios, context and interfaces, level-one building blocks, critical flows, deployment, and risks. Irrelevant topics are omitted rather than filled with placeholder text.

Can I edit an accepted ADR when requirements change?▼

No, accepted ADRs are immutable in meaning. When context changes materially, create a new ADR that supersedes the old one, link both records, and update the current architecture summary and contracts separately.

When should I use research-driven-development instead of this skill?▼

Use research-driven-development first when the architectural direction depends on evidence from unfamiliar local or external codebases, such as comparing multiple open-source implementations. Lightweight-architecture handles the resulting current model and significant decisions.