dev-arch

Automate architecture decisions and document ADRs for feature design.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/codihaus/claude-skills --skill dev-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-arch
Source: https://github.com/codihaus/claude-skills/tree/main/skills/dev-arch
Command: npx skills add https://github.com/codihaus/claude-skills --skill dev-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decisions and technical design for features ensure scalability and maintainability from the start.

Core Features & Use Cases

  • Make architecture decisions for features to ensure scalability, maintainability, and quality from the start.
  • Validate if current architecture supports requirements and identify patterns for API, data, and component design.
  • Document architecture decisions and ADRs to guide future work.

Quick Start

Provide the feature context and run the architecture workflow to produce architecture.md and ADRs.

Frequently Asked Questions about dev-arch

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

FAQPage Schema
How do I make architecture decisions for scalable features?

Architecture decisions for scalable features are automated by validating if your current design supports requirements and selecting patterns for API, data, and component design to ensure maintainability and quality.

What is the best way to document architecture decision records?

Documenting architecture decision records is handled by generating ADRs and an architecture.md file, guiding future work and ensuring alignment with quality attribute patterns during major changes.

When do I need to validate my current architecture for new requirements?

Validate your current architecture for new requirements during greenfield development or major changes to ensure existing design patterns support scalability, maintainability, and overall quality attributes.

How do I select design patterns for API and data components?

Select design patterns for API and data components by running the architecture workflow with feature context, which evaluates requirements and outputs appropriate patterns to ensure quality and scalability.

Can I use this architecture workflow for greenfield projects?

You can use this architecture workflow for greenfield projects or major changes, validating if the current architecture supports requirements and selecting patterns to ensure scalability from the start.