architecture

Translate feature requests and architecture analyses into formal architecture deliverables.

2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/avav25/ai-assets --skill architecture-avav25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/avav25/ai-assets/tree/main/.windsurf/skills/architecture
Command: npx skills add https://github.com/avav25/ai-assets --skill architecture-avav25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates high-level requirements and architectural ideas into concrete architecture deliverables that guide implementation, evaluation, and migration planning.

Core Features & Use Cases

  • Analyze PRDs and architectural initiatives to produce ARCHITECTURE.md updates, ADRs, and system diagrams.
  • Map constraints, non-functional requirements, and dependencies to tangible design decisions.
  • Use Case: Given a feature PRD, generate a coherent architecture context, identify gaps, and propose a migration or evolution plan.

Quick Start

Update ARCHITECTURE.md and create an ADR based on the current PRD and context.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I generate architecture deliverables from a PRD?

To generate architecture deliverables from a PRD, you translate high-level feature requests into formal outputs like ARCHITECTURE.md updates, ADRs, and system diagrams. This process identifies constraints, maps dependencies, and proposes a concrete migration or evolution plan.

What is an Architecture Decision Record and when do I need one?

An Architecture Decision Record (ADR) is a formal document that captures architectural decisions, their context, and consequences. You need an ADR when mapping non-functional requirements and constraints to tangible design choices during feature design or architecture evolution.

How do I map non-functional requirements to architecture decisions?

Mapping non-functional requirements to architecture decisions involves analyzing feature requests to identify system constraints and dependencies. This analysis produces formal deliverables like ADRs and ARCHITECTURE.md updates that document the chosen design paths.

Can I use this for cloud architecture and CI/CD architecture evolution?

Yes, this approach applies to cloud architecture and CI/CD architecture evolution. It translates architectural analyses into formal deliverables, identifying gaps and proposing migration plans across various system contexts.

What's the best way to update an ARCHITECTURE.md file based on new features?

The best way to update an ARCHITECTURE.md file is to analyze the feature PRD to generate a coherent architecture context. This identifies gaps, maps constraints, and proposes an evolution plan to formally document the changes.