Blueprint Architectural Decisions FAQs

Question 1

Can I use custom templates for my decisions?

Accepted Answer

Yes, the skill is designed to use a central source of truth located in _templates/TEMPLATES.md to ensure all generated documentation follows your project's specific standards.

Question 2

How does the triage functionality work?

Accepted Answer

The skill analyzes your input for specific keywords. Technology choices become ADRs, user stories become Feature Specs, and performance targets (like latency) become Non-functional Requirements.

Question 3

What if I provide a decision without a reason?

Accepted Answer

Rationale is a critical component of a good ADR. If you provide a technology choice without a 'because' clause, the skill will prompt you for the rationale or mark the record as a Draft.

Question 4

What happens if a new decision conflicts with an old one?

Accepted Answer

The skill performs conflict detection by scanning your existing ADR directory. If a contradiction is found, it will ask if you wish to supersede the old decision or if the new one serves a different purpose.

Question 5

What is an ADR in the context of this skill?

Accepted Answer

An Architecture Decision Record (ADR) is a document that captures a significant architectural decision, including its context, the options considered, and the final rationale.

Blueprint Architectural Decisions

Key Features

Use Cases

Blueprint Architectural Decisions

Key Features

Use Cases