architect

Translate requirements into high-level architecture proposals with design recommendations.

Updated May 20, 2026
One-click install
npx skills add https://github.com/Jayarr03/Codex_ThreatModel_Skills --skill architect-jayarr03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/Jayarr03/Codex_ThreatModel_Skills/tree/main/skills/architect
Command: npx skills add https://github.com/Jayarr03/Codex_ThreatModel_Skills --skill architect-jayarr03

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in transforming functional and non-functional requirements into high-level architecture options, recommended designs, and tradeoffs. It is used when shaping a new system or feature, comparing architectural approaches, defining major components, and recommending a practical architecture before detailed implementation.

Core Features & Use Cases

  • Architecture Design: Translates requirements into a clear, decision-oriented architecture proposal.
  • Technical Drivers: Identifies the key factors that should shape the design.
  • System Scope: Defines the system boundaries and external dependencies.
  • Options Generation: Produces one to three viable architecture approaches.
  • Design Recommendation: Chooses a preferred option and explains the rationale.
  • Requirement Mapping: Shows how the recommendation addresses the requirements.
  • Next Steps: Suggests follow-on artifacts and decisions.

Quick Start

Use the architect skill to design a high-level architecture for a multi-tenant SaaS platform with audit logging and SSO.

Frequently Asked Questions about architect

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

FAQPage Schema
What is the best way to compare architecture design options for a new feature?

System scope is defined by establishing clear system boundaries and identifying external dependencies during the architecture design process. This ensures the resulting proposal accurately addresses requirements and maps the technical drivers.

How does technical decision-making work when shaping a new system architecture?

Comparing architecture design options involves generating one to three viable approaches, evaluating their tradeoffs, and selecting a preferred design. The recommendation includes a rationale explaining how the chosen option maps back to the original requirements.

Can I use this approach for designing a multi-tenant SaaS platform with specific requirements?

Technical decision-making in architecture design identifies key technical drivers that shape the system, generates viable architecture options, and recommends a preferred design. It provides a structured approach to evaluate tradeoffs before implementation.

What follow-on artifacts and decisions are needed after finalizing an architecture proposal?

Yes, this architecture design approach applies to designing multi-tenant SaaS platforms with specific needs like audit logging and SSO. It translates those requirements into a decision-oriented proposal with defined system scope and technical drivers.

What follow-on artifacts and decisions are needed after finalizing an architecture proposal?

After finalizing an architecture proposal, the next steps involve suggesting follow-on artifacts and decisions required for detailed implementation. This ensures the recommended design and requirement mapping translate smoothly into actionable development.