architect

Generate complete technical architecture designs with bounded contexts, data contracts, and system topology.

2|1|Updated Mar 8, 2026

Search Tags:#design #architecture #documentation #requirements #bounded-context #system-design

Ready to run

npx skills add https://github.com/duggal1/Sapphire-cli --skill architect-duggal1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/duggal1/Sapphire-cli/tree/main/internal/skills/bundled/architect
Command: npx skills add https://github.com/duggal1/Sapphire-cli --skill architect-duggal1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds precise, requirement-driven architecture designs for complex software systems; it outputs a complete design document without implementation.

Core Features & Use Cases

End-to-end architecture design: defines bounded contexts, data contracts, system topology, and risk assessment for scalable software.
Stakeholder-aligned outputs: delivers design specifications that match exact user requirements with strict scope control.
Documentation-ready deliverable: outputs a structured architecture specification suitable for handoff to engineering teams.

Quick Start

Describe your system requirements and constraints, and I will generate a formal architecture design document.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I generate a system design document from software requirements?▼

To generate a system design document, you provide your software requirements and constraints to receive a formal architecture specification. The output includes defined bounded contexts, data contracts, and system topology without writing implementation code.

What is a bounded context and how does it fit into software architecture design?▼

A bounded context is a structural boundary in system design that defines specific domain models and data contracts. It fits into software architecture design by ensuring precise, requirement-driven scope control for scalable software systems.

Can I use this to define data contracts and system topology without writing implementation code?▼

Yes, you can define data contracts and system topology without implementation code. The process parses requirements to deliver complete technical architecture designs, outputting a documentation-ready specification suitable for engineering handoff.

Does this system design process include risk assessment and directory structure generation?▼

Yes, the system design process includes risk assessment and directory structure generation. It evaluates technical risk flags and defines the directory structure as part of the complete technical architecture design document.

What is the best way to document end-to-end architecture for engineering team handoff?▼

The best way to document end-to-end architecture for team handoff is to generate a structured specification covering bounded contexts, data contracts, and system topology. This delivers a documentation-ready output aligned with exact stakeholder requirements.

When should I not use an automated architecture design approach?▼

You should not use an automated architecture design approach if you need actual implementation code rather than a formal specification. This process strictly outputs technical architecture designs and documentation, triggering a hold protocol if implementation is requested.