Breakdown Epic Arch
- 8.9k installs
- 37.1k repo stars
- Updated July 28, 2026
- github/awesome-copilot
breakdown-epic-arch is an agent skill that Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
About
Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document. --- 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. - **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`.
- Epic Architecture Specification Prompt
- 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.
Breakdown Epic Arch by the numbers
- 8,860 all-time installs (skills.sh)
- +22 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #59 of 1,041 Cloud & Infrastructure skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
breakdown-epic-arch capabilities & compatibility
- Capabilities
- epic architecture specification prompt · the epic prd from the product manager. · **domain driven architecture** pattern for modul · **self hosted and saas deployment** requirements · **docker containerization** for all services.
- Use cases
- documentation
What breakdown-epic-arch says it does
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.
npx skills add https://github.com/github/awesome-copilot --skill breakdown-epic-archAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 8.9k |
|---|---|
| repo stars | ★ 37.1k |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 28, 2026 |
| Repository | github/awesome-copilot ↗ |
What problem does breakdown-epic-arch solve for developers using this skill?
Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
Who is it for?
Developers who need breakdown-epic-arch patterns described in the cached skill documentation.
Skip if: Skip when docs are empty or the task is outside the skill's documented scope.
When should I use this skill?
Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
What you get
Actionable workflows and conventions from SKILL.md for breakdown-epic-arch.
- architecture specification
- component definitions
- diagram outline
Files
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]
Related skills
Azure AiIntegrates Azure AI Content Safety, Document Intelligence, Speech, and Search services into Java-based agents and applications.479k1.3kAzure PrepareGenerate the exact Azure infrastructure files, Dockerfiles, and azure.yaml configuration needed before deploying any new or modernized application.479k1.3kAzure StorageConnect agents and applications to Azure Blob Storage, File Shares, Queues, Tables, and Data Lake without leaving the coding environment.478k1.3kAppinsights InstrumentationAutomatically instrument web applications running on Azure App Service with Application Insights for observability without manual configuration.478k1.3kAzure Resource LookupInstantly list, query, and discover any Azure resources across subscriptions without leaving the agent chat.478k1.3kAzure AigatewayConfigure Azure API Management as a secure, governed gateway for routing traffic to LLMs, MCP servers, and agent tools.478k1.3kHow it compares
Choose breakdown-epic-arch for PRD-to-epic architecture planning; use technology-stack-blueprint-generator when analyzing an existing codebase instead.
FAQ
What does breakdown-epic-arch do?
Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
When should I use breakdown-epic-arch?
Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
Is breakdown-epic-arch safe to install?
Review the Security Audits panel on this page before installing in production.