decision-writer

Generate structured architecture decision records and save them as dated Markdown files.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill decision-writer-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-writer
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/decision-writer
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill decision-writer-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often make important architectural or business decisions without documenting the context, alternatives, and rationale, leading to repeated debates and lost institutional knowledge. This Skill standardizes decision documentation into a consistent, reviewable record format. ## Core Features & Use Cases - Structured ADR Generation: Produces decision records with status, date, decision makers, context, drivers, options, outcome, and consequences. - Standardized Output Location: Saves every record to docs/public/decisions/ using the YYYY-MM-DD-<short-title>.md naming convention. - Pros and Cons Analysis: Captures per-option trade-offs so future reviewers understand why alternatives were rejected. - Use Case: After choosing Rust over C++ for a DSP engine, ask the assistant to record the decision and receive a complete ADR file ready to commit to the repository. ## Quick Start Ask the assistant to document the decision to adopt WinUI 3 for the desktop UI as an architecture decision record.

Frequently Asked Questions about decision-writer

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

FAQPage Schema
How do I create an architecture decision record?

Provide the decision title, context, drivers, options considered, and chosen outcome. The Skill formats these into a standard ADR template with status, date, and consequences, then saves it as a dated Markdown file.

What should an ADR template include?

A complete ADR includes status, date, decision makers, context and problem statement, decision drivers, options considered, the chosen outcome with justification, positive and negative consequences, and pros and cons for each option.

Where are the generated decision records saved?

All records are written to the docs/public/decisions/ directory. Each file follows the naming convention YYYY-MM-DD-<short-title>.md so records sort chronologically.

When should I write a decision record instead of a code comment?

Use a decision record when a choice affects architecture, tooling, or business direction and involves trade-offs between multiple options. Code comments suit local implementation details, while ADRs capture cross-cutting rationale for future reviewers.

Can I record rejected or superseded decisions?

Yes. The status field supports Proposed, Accepted, Rejected, Deprecated, and Superseded, so you can document decisions that were declined or later replaced while preserving their original rationale.