skills.rest
Plasma-AndraaX
Plasma-AndraaXCOMMUNITY
Explore all skills by this author →
GitHub

new-adr

Guide creation of Architecture Decision Records and companion implementation plans.

Updated Jul 1, 2026
Search Tags:#microservices#software architecture#ADR#architectural decision record#decision documentation
One-click install
npx skills add https://github.com/Plasma-AndraaX/armature --skill new-adr-plasma-andraax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: new-adr
Source: https://github.com/Plasma-AndraaX/armature/tree/main/plugin/skills/new-adr
Command: npx skills add https://github.com/Plasma-AndraaX/armature --skill new-adr-plasma-andraax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill assists in structuring and reflecting on architectural decisions to produce Architecture Decision Records (ADRs) and their companion plans.

Core Features & Use Cases

  • Structured Reflection: Guide through the process of thinking through architectural decisions that lead to ADRs.
  • Decision Justification: Help determine when an ADR is justified based on specific criteria.
  • Process Guidance: Outline a structured process for drafting ADRs, including exploration, tradeoff analysis, and documentation.
  • Companion Plan Creation: Facilitate the creation of companion plans to guide implementation.

Quick Start

Start a new ADR for the topic "Implementing a microservices architecture".

Frequently Asked Questions about new-adr

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

FAQPage Schema
How do I create an Architecture Decision Record for microservices architecture?▼

To create an Architecture Decision Record, you must structurally reflect on complex architectural decisions, analyze explicit tradeoffs, and document the justification along with an implementation strategy.

When do I need an architectural decision record in software architecture?▼

You need an architectural decision record when facing complex architectural decisions that involve explicit tradeoffs. It is justified when your software development project requires detailed decision documentation and a structured implementation strategy.

What is the best way to document tradeoffs in software architecture decisions?▼

The best way to document tradeoffs in software architecture is by drafting an Architecture Decision Record. This involves a structured process of exploration and tradeoff analysis to ensure your architectural decisions are thoroughly justified and documented.

Can I generate a companion implementation plan alongside an ADR?▼

Yes, you can generate a companion implementation plan alongside an ADR. After structuring your architectural decision record, the process facilitates creating companion plans specifically designed to guide the subsequent implementation of those decisions.

What are the limitations of using ADRs for decision documentation in software engineering?▼

ADRs for decision documentation are primarily structured for complex architectural decisions with explicit tradeoffs, meaning they may be excessive for trivial software engineering choices that do not require detailed exploration or a companion implementation plan.

Related Skills

Explore More Software Engineering Skills→
petrSimonidesXartpetrSimonidesXart

approach-evaluation

Evaluate technical approaches against project constraints with documented evidence.

Community
Advanced
NehaTanti-afkNehaTanti-afk

design-plan

Generate implementation plans with architecture and phased execution from Linear tickets.

Community
Advanced
Joncik91Joncik91
29

architect

Creates architectural decision records and evaluates system design options.

Community
Advanced
xenitV1xenitV1
132

architecture

Systematize requirements analysis and ADR documentation for architecture decisions.

Community
Basic