ADR Writer FAQs

Question 1

When should I use this skill?

Accepted Answer

Use this skill whenever you need to document a significant technical decision. Activate it with prompts like "create an ADR for our new caching strategy" or "update ADR-005 with new consequences" to maintain a clear and standardized decision log.

Question 2

How does this skill improve my workflow?

Accepted Answer

It saves you time by automating tedious tasks like numbering and formatting. By enforcing consistency and guiding you to document context, trade-offs, and alternatives, it improves the clarity and long-term value of your project's architectural history.

Question 3

What unique capabilities does it provide?

Accepted Answer

This skill enforces a strict ADR structure, automates file naming conventions, promotes documenting trade-offs, and guides the use of pseudocode instead of implementation-specific code. It also analyzes existing ADRs to match your project's specific style.

Question 4

What does the ADR Writer skill do?

Accepted Answer

The ADR Writer skill helps you create and edit Architecture Decision Records (ADRs). It strictly enforces a predefined structure (Context, Decision, Consequences), automates file naming, and ensures your team's technical decisions are documented consistently.

ADR Writer

主要功能

使用场景

ADR Writer

主要功能

使用场景