straymark-adr

Create Architecture Decision Records with required metadata and structured sections.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/StrangeDaysTech/arborist-cli --skill straymark-adr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: straymark-adr
Source: https://github.com/StrangeDaysTech/arborist-cli/tree/main/.gemini/skills/straymark-adr
Command: npx skills add https://github.com/StrangeDaysTech/arborist-cli --skill straymark-adr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Straymark ADR helps teams capture and communicate significant architecture decisions in a consistent, auditable way—while ensuring they receive human review.

Core Features & Use Cases

  • ADR creation workflow: Guides you through gathering context, confirming with stakeholders, assigning an ADR sequence id, and writing a complete record.
  • Templated, structured output: Produces an ADR file using the configured language template and required fields (draft status, review_required, and risk_level).
  • Repository-aligned storage: Saves decisions into .straymark/02-design/decisions/ using an ADR-YYYY-MM-DD-NNN naming convention for ongoing traceability.
  • Use case: You change a core subsystem architecture (e.g., persistence approach, service boundaries, or API style) and need a documented rationale plus consequences for future maintainers.

Quick Start

Provide the decision title, the context for why it is needed, and the alternatives you considered, then instruct the agent to create the ADR using the StrayMark template and mark it as a draft requiring human review.

Frequently Asked Questions about straymark-adr

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

FAQPage Schema
How do I document an architecture decision record for a software design change?

To create an architecture decision record, this Skill guides you through gathering context, confirming stakeholder details, assigning a sequence ID, and generating a structured ADR file with Context, Decision, Alternatives, and Consequences sections.

What do I need to provide to generate a draft ADR file?

You need to provide the decision title, the context for why the architectural change is needed, and the alternatives you considered. The Skill then uses this input to populate the ADR template and mark the file as a draft requiring human review.

When should I use an architecture decision record in my git repository?

You should create an architecture decision record when system structure, technology stack, integration approach, or design patterns change significantly and must be documented with rationale and consequences for future maintainers.

What is the best way to track design documentation and architecture decisions over time?

The best way to track design documentation is by saving ADR files using an ADR-YYYY-MM-DD-NNN naming convention inside the .straymark/02-design/decisions/ directory, ensuring ongoing traceability and repository-aligned storage.

Can I mark an architecture decision record as requiring human review before finalizing?

Yes, the generated ADR file includes metadata fields for draft status, review_required, and risk_level, ensuring that every architecture decision record is explicitly flagged for human review before integration.

Does the ADR workflow support documenting impacted components and success metrics?

Yes, the architecture decision record template includes dedicated sections for Impacted Components, Plan, and Success Metrics, allowing you to document structural impacts and measurable outcomes alongside the core decision rationale.