architect

Translate specifications into technical designs with architecture decisions and testing strategies.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill architect-lleontor705
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/architect
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill architect-lleontor705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms textual proposals and specifications into concrete, implementation-ready architectural designs that guide development and validation.

Core Features & Use Cases

  • Architecture decision documents including alternatives and rationales
  • Data-flow diagrams and interface contracts that map to code changes
  • Persistence of designs into Cortex under the design topic
  • OpenSpec alignment: uses proposal and spec to ensure design completeness

Quick Start

Generate a complete architecture design for the specified SDD change by reading Cortex artifacts and producing a design document.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I turn specs into concrete technical designs?▼

Architecture design generation translates specifications and proposals into implementation-ready technical designs grounded in the actual codebase. It ensures every design includes architecture decisions with rationales, file changes, interfaces, and a robust testing strategy.

What is the Spec-Driven Development pipeline for architecture design?▼

The Spec-Driven Development pipeline reads Cortex artifacts like proposals and specs to ensure design completeness. It produces architecture decision documents that map data-flow diagrams and interface contracts to actual code changes.

How do I generate an architecture decision document with rationales?▼

Generate an architecture decision document with rationales by reading Cortex artifacts and producing a design document. This ensures every architectural choice includes alternatives, rationales, and maps interface contracts directly to code changes.

Does architecture design generation require OpenSpec alignment?▼

Architecture design generation uses OpenSpec alignment by reading proposal and spec artifacts to ensure design completeness. It transforms textual proposals into concrete technical designs that guide development and validation.

Can I persist technical designs into Cortex?▼

You can persist technical designs into Cortex under the design topic. The architecture design process writes the generated design document back to Cortex, ensuring implementation-ready architecture decisions are stored with the project artifacts.

What is the best way to map data-flow diagrams to code changes?▼

The best way to map data-flow diagrams to code changes is translating specifications into concrete technical designs. This approach ensures interface contracts and architecture decisions are directly grounded in the actual codebase.