skills.rest
vincent-kk
vincent-kkCOMMUNITY
Explore all skills by this author →
GitHub

design-architect

Convert EARS requirements into components, APIs, and ADR documentation.

1|Updated Nov 13, 2024
Search Tags:#ADR#EARS#data-model#API-design#architectural-design#component-diagrams
One-click install
npx skills add https://github.com/vincent-kk/albatrion --skill design-architect-vincent-kk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-architect
Source: https://github.com/vincent-kk/albatrion/tree/main/.claude/skills/design-architect
Command: npx skills add https://github.com/vincent-kk/albatrion --skill design-architect-vincent-kk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

EARS requirements are often high-level and vague; this Skill translates them into concrete technical architecture concepts, enabling precise design of components, APIs, and data models early in the project lifecycle.

Core Features & Use Cases

  • Transform EARS requirements into component, API, and data-model design artifacts.
  • Produce architecture documentation including ADRs, diagrams, and design notes to guide implementation.
  • Use Case: Given an EARS specification, generate an architectural plan that maps requirements to a scalable tech stack and design documents.

Quick Start

Provide the EARS requirement document and project context to generate a complete design package including components, API specs, and ADRs.

Frequently Asked Questions about design-architect

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

FAQPage Schema
How do I translate EARS requirements into concrete software architecture?▼

To translate EARS requirements into concrete software architecture, provide the EARS specification and project context to generate a complete design package mapping requirements to components, APIs, and data structures.

What is the best way to generate ADRs and component diagrams from requirement specifications?▼

Generating ADRs and component diagrams from requirement specifications is best achieved by converting EARS syntax into detailed architectural designs, outputting traceable architecture-level documentation and design artifacts.

How do I design data models and API specs from high-level functional requirements?▼

You can design data models and API specs from high-level functional requirements by processing EARS documents to produce precise technical architecture concepts, enabling early component and API design.

Can I use EARS syntax for end-to-end architectural planning in software projects?▼

Yes, you can use EARS syntax for end-to-end architectural planning in software projects by transforming functional and non-functional requirements into scalable tech stack mappings and architectural plans.

Why do high-level EARS requirements often lead to vague architectural designs?▼

High-level EARS requirements often lead to vague architectural designs because they lack specific technical context, requiring translation into concrete component diagrams, data structures, and API definitions.

What is needed to generate an architectural plan from EARS requirements?▼

To generate an architectural plan from EARS requirements, you need to provide the EARS requirement document and project context to produce a design package including components, API specs, and ADRs.

Related Skills

Explore More Software Engineering Skills→
notta50notta50

kiro-spec-requirements

Translate project briefs and steering context into EARS-format requirements drafts.

Community
Advanced
theandyalvarez7-rubytheandyalvarez7-ruby

senior-architect

Analyze software architecture and generate Mermaid, PlantUML, or ASCII diagrams.

Community
Advanced
MatrixFounderMatrixFounder
4

architecture-format-extended

Generate extended architecture templates covering components, data models, interfaces, and deployment details.

Community
Intermediate
ConsiliencyConsiliency
8

c4-modeling

Generate standardized C4 architecture diagrams using Mermaid syntax.

Official
Advanced