architecture-agent

Generate Architecture Decision Records as Markdown files with structured sections.

Updated Oct 26, 2025
One-click install
npx skills add https://github.com/redmage123/artemis --skill architecture-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-agent
Source: https://github.com/redmage123/artemis/tree/main/src/prompts
Command: npx skills add https://github.com/redmage123/artemis --skill architecture-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires anthropic, openai.

What problem does it solve?

Architectural decision-making and documentation can be a bottleneck in software development, leading to inconsistent designs and wasted time. This Skill automates the creation of comprehensive Architecture Decision Records (ADRs), ensuring clarity, alignment, and efficiency from the very start of your project.

Core Features & Use Cases

  • Automated ADR Generation: Instantly drafts detailed, structured Architecture Decision Records for any software task.
  • Systematic Option Evaluation: Compares multiple technical approaches, detailing pros, cons, and trade-offs to guide optimal choices.
  • Clear Design Blueprints: Provides a foundational design document, outlining component structure, APIs, and data flow for developers.
  • Use Case: Before a new feature sprint, activate this Skill to generate an ADR for a complex component, ensuring all technical decisions are documented and justified, allowing your team to build with confidence and speed.

Quick Start

Use the architecture-agent skill to create an Architecture Decision Record for a new user authentication module, considering OAuth2 and JWT options.

Frequently Asked Questions about architecture-agent

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

FAQPage Schema
What is an Architecture Decision Record and why do I need one?

An Architecture Decision Record (ADR) is a structured document that captures architectural decisions, their context, and consequences. ADRs provide clear justification and traceability for design choices, ensuring team alignment and preventing duplicate effort on past decisions.

How do I create an Architecture Decision Record for my software project?

Use the architecture-agent skill to draft a comprehensive ADR by describing your architectural challenge. The skill generates a Markdown file with Title, Status, Context, Decision, Options Considered, Consequences, and Implementation Notes sections, ready to integrate into your development pipeline.

Can I compare multiple technical options before making an architectural decision?

Yes. The architecture-agent systematically evaluates multiple approaches, detailing pros, cons, and trade-offs for each option. This comparison guides your optimal choice and documents the reasoning in a structured ADR format.

When should I use Architecture Decision Records in my development process?

Use ADRs when initiating architectural planning, evaluating competing technical solutions, or transitioning requirements to implementation. They're especially valuable before feature sprints, for complex components, and when onboarding team members who need design rationale.

Does the architecture-agent work with OAuth2, JWT, and other authentication frameworks?

Yes. The architecture-agent handles any authentication approach or technical framework. You can use it to generate ADRs comparing authentication strategies like OAuth2 and JWT, documenting security trade-offs and implementation details.

What output format do Architecture Decision Records use?

ADRs are generated as Markdown files named ADR-XXX-title.md, containing structured sections with clear justification and traceability. This format integrates seamlessly with version control and documentation pipelines.