architect

Translate product requirements into data models, API contracts, ADRs, and OpenAPI specs.

6|Updated Jan 25, 2026

Search Tags:#DDD #ADR #SOLID #architect #system-design #API-contracts

Ready to run

npx skills add https://github.com/gajakannan/nebula-crm --skill architect-gajakannan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/gajakannan/nebula-crm/tree/main/agents/architect
Command: npx skills add https://github.com/gajakannan/nebula-crm --skill architect-gajakannan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Architects translate product requirements into scalable, maintainable architectures, enabling teams to build robust software platforms without ad-hoc compromises.

Core Features & Use Cases

Define system boundaries, data models, and module interfaces to ensure clean separations of concerns.
Create API contracts, ADRs, and governance artifacts to guide implementation and future decisions.
Lead Phase B design reviews and Phase C implementation planning to reduce rework and misalignment.

Quick Start

Review planning-mds/INCEPTION.md for Phase A inputs, then consult planning-mds/examples/architecture for established patterns. Open planning-mds/architecture/SOLUTION-PATTERNS.md to align on architecture patterns before starting.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I translate product requirements into scalable software architectures?▼

To translate requirements into scalable software architectures, define system boundaries, data models, and module interfaces. This ensures clean separations of concerns and prevents ad-hoc compromises during implementation.

What is the best way to document API contracts and architectural decisions?▼

The best way to document API contracts and architectural decisions is by creating OpenAPI specs and ADRs. These governance artifacts guide implementation and align teams on future technical choices.

How does DDD apply to defining system boundaries and data models?▼

DDD applies to defining system boundaries by translating product requirements into clean module interfaces and data models. This structured approach ensures maintainable separations of concerns across the platform.

Can I use OpenAPI specs for Phase B design reviews and Phase C planning?▼

Yes, you can use OpenAPI specs for Phase B design reviews and Phase C implementation planning. They align architectural artifacts with data models and validation schemas to reduce rework.

Why do I need ADRs and governance artifacts for system design?▼

You need ADRs and governance artifacts for system design to guide implementation and future decisions. They provide documented alignment across teams, reducing misalignment and preventing ad-hoc architectural compromises.