registro-decisao-arquitetura

Create Architectural Decision Records using the standardized Nygard template.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/konecty/Konecty --skill registro-decisao-arquitetura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: registro-decisao-arquitetura
Source: https://github.com/konecty/Konecty/tree/main/.cursor/skills/registro-decisao-arquitetura
Command: npx skills add https://github.com/konecty/Konecty --skill registro-decisao-arquitetura

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps teams document significant architectural decisions, ensuring clarity, context, and a shared understanding of system design choices.

Core Features & Use Cases

  • Standardized Templates: Provides a consistent format (Nygard) for documenting Architectural Decision Records (ADRs).
  • Contextualization: Captures the 'why' behind decisions, including context, consequences, and alternatives.
  • Use Case: When deciding on a new database technology, use this Skill to create an ADR that outlines the problem, the chosen database, its benefits and drawbacks, and why other options were rejected.

Quick Start

Use the registro-decisao-arquitetura skill to create a new Architectural Decision Record following the Nygard template.

Frequently Asked Questions about registro-decisao-arquitetura

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

FAQPage Schema
How do I document architectural decisions to avoid technical debt?

You document architectural decisions by creating Architectural Decision Records (ADRs) that capture context, alternatives, and consequences to prevent technical debt. This skill uses the standardized Nygard template to record architectural memory effectively.

What is the Nygard template for Architectural Decision Records?

The Nygard template is a standardized format for creating Architectural Decision Records that structures documentation by capturing context, decisions, consequences, and alternatives. It provides a consistent structure for teams to maintain architectural memory of significant software design choices.

How do I write an ADR for a new database technology selection?

To write an ADR for a new database technology, use this skill to outline the problem, the chosen database, its benefits and drawbacks, and why other options were rejected. This ensures the why behind your architectural decision is clearly contextualized for future reference.

When do I need to create an Architectural Decision Record?

You need to create an Architectural Decision Record when making significant system design choices that require shared understanding, such as selecting a new database technology. Documenting these decisions ensures clarity and preserves the context for future development teams.

What are common pitfalls to avoid when creating ADRs?

Common pitfalls in ADR creation include failing to capture the context and alternatives behind a decision, which obscures the reasoning for future teams. This skill includes best practices to avoid these common documentation mistakes and maintain clear architectural memory.