Arquitetura técnica de épicos a partir do PRD

O que esta skill faz

Esta skill gera a arquitetura de um épico com base no respectivo Product Requirements Document. O modelo considera DDD, SaaS e self-hosted, Docker, Next.js, Turborepo, tRPC e Stack Auth, sem produzir código além de pseudocódigo necessário.

Quando usar

• Definir a arquitetura de um novo épico
• Mapear camadas de usuário, aplicação, serviços e dados
• Criar um diagrama completo em Mermaid
• Identificar serviços, integrações e habilitadores técnicos

Como usar

1. Forneça e revise o PRD completo do épico
2. Revise o repositório para confirmar padrões e tecnologias realmente adotados
3. Defina componentes, limites de domínio e fluxos entre camadas
4. Produza o diagrama Mermaid e registre decisões de alto nível
5. Salve em docs/ways-of-work/plan/{epic-name}/arch.md

O que revisar antes de instalar

• A especificação depende da qualidade e completude do PRD
• A stack indicada é uma consideração do modelo e precisa ser validada no projeto
• O documento não deve conter implementação detalhada ou código de produção

SKILL.md

---
name: breakdown-epic-arch
description: 'Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.'
---

# Epic Architecture Specification Prompt

## Goal

Act as a Senior Software Architect. Your task is to take an Epic PRD and create a high-level technical architecture specification. This document will guide the development of the epic, outlining the major components, features, and technical enablers required.

## Context Considerations

- The Epic PRD from the Product Manager.
- **Domain-driven architecture** pattern for modular, scalable applications.
- **Self-hosted and SaaS deployment** requirements.
- **Docker containerization** for all services.
- **TypeScript/Next.js** stack with App Router.
- **Turborepo monorepo** patterns.
- **tRPC** for type-safe APIs.
- **Stack Auth** for authentication.

**Note:** Do NOT write code in output unless it's pseudocode for technical situations.

## Output Format

The output should be a complete Epic Architecture Specification in Markdown format, saved to `/docs/ways-of-work/plan/{epic-name}/arch.md`.

### Specification Structure

#### 1. Epic Architecture Overview

- A brief summary of the technical approach for the epic.

#### 2. System Architecture Diagram

Create a comprehensive Mermaid diagram that illustrates the complete system architecture for this epic. The diagram should include:

- **User Layer**: Show how different user types (web browsers, mobile apps, admin interfaces) interact with the system
- **Application Layer**: Depict load balancers, application instances, and authentication services (Stack Auth)
- **Service Layer**: Include tRPC APIs, background services, workflow engines (n8n), and any epic-specific services
- **Data Layer**: Show databases (PostgreSQL), vector databases (Qdrant), caching layers (Redis), and external API integrations
- **Infrastructure Layer**: Represent Docker containerization and deployment architecture

Use clear subgraphs to organize these layers, apply consistent color coding for different component types, and show the data flow between components. Include both synchronous request paths and asynchronous processing flows where relevant to the epic.

#### 3. High-Level Features & Technical Enablers

- A list of the high-level features to be built.
- A list of technical enablers (e.g., new services, libraries, infrastructure) required to support the features.

#### 4. Technology Stack

- A list of the key technologies, frameworks, and libraries to be used.

#### 5. Technical Value

- Estimate the technical value (e.g., High, Medium, Low) with a brief justification.

#### 6. T-Shirt Size Estimate

- Provide a high-level t-shirt size estimate for the epic (e.g., S, M, L, XL).

## Context Template

- **Epic PRD:** [The content of the Epic PRD markdown file]