Prompt file imported from lem0n4id/mafia-game-role-allocator (.github/prompts/breakdown-epic-arch.prompt.md). Copyright stays with the author.

Epic Architecture Specification Prompt

Name: breakdown-epic-arch
Author: lem0n4id

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]

# 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]

{ "prompt": "# Epic Architecture Specification Prompt\n\n## Goal\n\nAct 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.\n\n## Context Considerations\n\n- The Epic PRD from the Product Manager.\n- **Domain-driven architecture** pattern for modular, scalable applications.\n- **Self-hosted and SaaS deployment** requirements.\n- **Docker containerization** for all services.\n- **TypeScript/Next.js** stack with App Router.\n- **Turborepo monorepo** patterns.\n- **tRPC** for type-safe APIs.\n- **Stack Auth** for authentication.\n\n**Note:** Do NOT write code in output unless it's pseudocode for technical situations.\n\n## Output Format\n\nThe output should be a complete Epic Architecture Specification in Markdown format, saved to `/docs/ways-of-work/plan/{epic-name}/arch.md`.\n\n### Specification Structure\n\n#### 1. Epic Architecture Overview\n\n- A brief summary of the technical approach for the epic.\n\n#### 2. System Architecture Diagram\n\nCreate a comprehensive Mermaid diagram that illustrates the complete system architecture for this epic. The diagram should include:\n\n- **User Layer**: Show how different user types (web browsers, mobile apps, admin interfaces) interact with the system\n- **Application Layer**: Depict load balancers, application instances, and authentication services (Stack Auth)\n- **Service Layer**: Include tRPC APIs, background services, workflow engines (n8n), and any epic-specific services\n- **Data Layer**: Show databases (PostgreSQL), vector databases (Qdrant), caching layers (Redis), and external API integrations\n- **Infrastructure Layer**: Represent Docker containerization and deployment architecture\n\nUse 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.\n\n#### 3. High-Level Features & Technical Enablers\n\n- A list of the high-level features to be built.\n- A list of technical enablers (e.g., new services, libraries, infrastructure) required to support the features.\n\n#### 4. Technology Stack\n\n- A list of the key technologies, frameworks, and libraries to be used.\n\n#### 5. Technical Value\n\n- Estimate the technical value (e.g., High, Medium, Low) with a brief justification.\n\n#### 6. T-Shirt Size Estimate\n\n- Provide a high-level t-shirt size estimate for the epic (e.g., S, M, L, XL).\n\n## Context Template\n\n- **Epic PRD:** [The content of the Epic PRD markdown file]", "variables": [], "notes": "Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document. Mode: agent.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/lem0n4id/mafia-game-role-allocator", "path": ".github/prompts/breakdown-epic-arch.prompt.md", "ref": "31e0e0b61c7519896252272c6175e029bec6d88f", "url": "https://github.com/lem0n4id/mafia-game-role-allocator/blob/31e0e0b61c7519896252272c6175e029bec6d88f/.github/prompts/breakdown-epic-arch.prompt.md", "key": "lem0n4id/mafia-game-role-allocator/.github/prompts/breakdown-epic-arch.prompt.md" } } }

breakdown-epic-arch

About