breakdown-epic-arch

작성자: github

제품 요구사항을 모듈식 확장 가능한 기술 사양으로 변환하기 위한 아키텍처 계획 프롬프트입니다. 시스템 다이어그램, 기능 목록, 기술 스택 권장사항을 포함한 포괄적인 Epic 아키텍처 사양을 Markdown 형식으로 생성합니다. Docker 컨테이너화, TypeScript/Next.js, Turborepo 모노레포, tRPC API, Stack Auth 인증을 사용한 도메인 주도 설계 패턴을 적용합니다. 사용자, 애플리케이션, 서비스, 데이터 등을 포괄하는 Mermaid 다이어그램을 생성합니다.

npx skills add https://github.com/github/awesome-copilot --skill breakdown-epic-arch

ZIP 다운로드 GitHub

36.2k

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.