Architect

Overview

The Architect is the guardian of system integrity. It ensures that every technical decision aligns with established patterns, scales appropriately, and does not introduce anti-patterns into the codebase. Before any significant implementation begins, the Architect evaluates the landscape and proposes multiple approaches.

When It's Used

Invoked during /dr-design for Level 3-4 tasks that require architectural decisions. Also participates in Consilium panels when system-wide impact needs evaluation.

Capabilities

• Context Gathering (Phase 1) — studies existing docs and code, defines scope, identifies constraints and dependencies
• Solution Exploration (Phase 2) — generates 3+ distinct technical approaches, each with detailed Pros and Cons
• Evaluation — scores approaches against Security, Pattern Alignment, DRY, and Testability criteria
• Rejection — automatically rejects approaches containing anti-patterns such as hardcoded secrets or raw SQL
• User Consultation (Phase 3) — presents alternatives and waits for explicit approval before proceeding
• Creates Architectural Decision Records (ADRs)

How It Works

The Architect follows a three-phase workflow. First, it gathers context by reading the project brief, existing system patterns, and prior decisions. Second, it explores solutions — never fewer than three — evaluating each against quality criteria. Third, it presents the options to you and waits. No architectural change happens without your approval.

Example

/dr-design "Add real-time notification system"
→ Architect reads systemPatterns.md and decisions.md
→ Generates 3 approaches: WebSockets, SSE, polling
→ Evaluates: security, scalability, pattern alignment
→ Presents comparison table → waits for approval
→ Updates systemPatterns.md with chosen approach

Context Loading

Reads datarim/projectbrief.md, datarim/systemPatterns.md, and datarim/decisions.md. Applies the datarim-system skill for creative phase enforcement. Loads tech-stack skill when making technology decisions.

Skills Used

datarim-system (always), tech-stack (when needed), performance (optional), security (optional).