Skills github awesome-copilot Epic breakdown workflow
breakdown-epic-arch
- Use it when:
- You have an Epic PRD, such as the one breakdown-epic-pm writes, and need its technical architecture before planning features.
- You get:
- /docs/ways-of-work/plan/{epic-name}/arch.md, with no code beyond pseudocode.
- It does:
- Summarizes the approach, draws a layered Mermaid diagram from users to infrastructure, lists features, enablers and technologies, and rates value and size.
- Assumes:
- TypeScript and Next.js in a Turborepo monorepo with tRPC, Stack Auth and Docker.
Skill 2 of 6 in the Epic breakdown workflow bundle, after breakdown-epic-pm and before breakdown-feature-prd.
Assumes a fixed stack: TypeScript and Next.js App Router in a Turborepo monorepo, tRPC, Stack Auth and Docker, with PostgreSQL, Qdrant, Redis and n8n in its diagram.
TL;DR
The second step of the breakdown workflow. The agent acts as a senior software architect and takes the Epic PRD's content as input. It writes six sections: an overview of the technical approach; a Mermaid diagram with subgraphs for the user, application, service, data and infrastructure layers, color-coded and showing both synchronous requests and asynchronous flows; the high-level features and the technical enablers they need, such as new services, libraries or infrastructure; the key technologies; the technical value as high, medium or low with a reason; and a T-shirt size from S to XL. It plans around domain-driven design, self-hosted and SaaS deployment, Docker for every service, and a TypeScript, Next.js App Router, Turborepo, tRPC and Stack Auth stack, and its diagram includes PostgreSQL, Qdrant, Redis and n8n. The file arch.md goes next to the epic's epic.md, and breakdown-feature-prd links to both from each feature's PRD.
Summarizes the skill at 797337f.
npx skills add https://github.com/github/awesome-copilot --skill breakdown-epic-arch skills.sh pageSource on GitHubAll skills from github/awesome-copilot
- Total Downloads
- 9,000 on skills.sh, Nov 9, 2026
- Repo stars
- 40,943 github/awesome-copilot
- First seen
- Feb 25, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 11 |
| Sep 28 | 17 |
| Oct 5 | 17 |
| Oct 12 | 2 |
| Oct 19 | 2 |
| Oct 26 | 2 |
| Nov 2 | 4 |
| Nov 9 | 3 |
| Category |
Make the agent question you and write the plan down before it writes code. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A one-shot action you invoke by name, such as turning the conversation into a PRD. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics | |
| Stack |
SKILL.md
From github/awesome-copilot at 797337f. Checked daily, last changed Nov 6, 2026.
Frontmatter
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]