system-architect

Transform product requirements into technical architecture with components, data models, and OpenAPI specs.

2|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/adnanmueller/am-dev-plugins --skill system-architect-adnanmueller
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: system-architect
Source: https://github.com/adnanmueller/am-dev-plugins/tree/main/plugins/development-pipeline/agents/02b-architect
Command: npx skills add https://github.com/adnanmueller/am-dev-plugins --skill system-architect-adnanmueller

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts product requirements into a robust technical architecture, enabling parallel backend and frontend development with clear API contracts, data models, and ADRs.

Core Features & Use Cases

  • Translate product requirements into a complete technical blueprint including components, data models, and OpenAPI specs.
  • Define and document architecture decisions (ADRs) to guide future evolutions.
  • Produce production-ready documentation (OpenAPI, data schemas, ADRs) that teams can implement against.

Quick Start

Provide the product requirements to the System Architect and obtain a fully scoped architecture blueprint, API contracts, and ADRs ready for implementation.

Frequently Asked Questions about system-architect

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

FAQPage Schema
How do I convert product requirements into a technical architecture with OpenAPI specs?▼

Documenting architecture decisions using ADRs captures technical design rationale and risk mitigations, guiding future system evolutions and providing production-ready documentation for teams implementing data schemas and API contracts.

What is the best way to plan parallel frontend and backend development from feature requirements?▼

Generating a technical design blueprint requires providing structured product requirements as input, which are then transformed into detailed components, data schemas, architecture decision records, and API contracts.

How do I create production-ready data schemas and ADRs for feature-rich pipelines?▼

Architecture decision records are produced alongside OpenAPI specs and data models, capturing the architectural choices and risk mitigations derived directly from your submitted product requirements.

Can I generate API contracts and data models for system architecture without manual coding?▼

The technical design blueprint covers components, data models, and API contracts, specifically satisfying requirements for documenting architectural decisions and risk mitigations in feature-rich pipelines.