Epic Architecture Specification
OfficialFreeCreate high-level architecture from PRDs efficiently.
Free · Opens the source repo
What Epic Architecture Specification does
The Epic Architecture Specification skill is designed for software architects and developers tasked with translating product requirements documents (PRDs) into detailed technical architecture specifications. This skill guides users through the process of developing a comprehensive architecture document that outlines the major components and features necessary for an epic, ensuring that all technical aspects are thoroughly considered. By utilizing a structured approach, this skill helps in maintaining clarity and consistency in architecture design.
The skill emphasizes the use of domain-driven architecture principles, which are essential for building modular and scalable applications. It takes into account various deployment scenarios, including self-hosted and SaaS models, and incorporates modern development practices such as Docker containerization. The specified technology stack includes TypeScript and Next.js, leveraging the App Router for efficient routing, and utilizing Turborepo monorepo patterns for better organization of code.
Users will benefit from detailed output formats that include a system architecture diagram created with Mermaid, which visually represents the different layers of the application, such as user, application, service, data, and infrastructure layers. This diagram aids in understanding the interactions between various components and the flow of data throughout the system. Additionally, the skill provides a clear breakdown of high-level features, technical enablers, and the overall technology stack required for the epic, making it an invaluable resource for any development team.
In summary, this skill is targeted at software architects and developers who need to create high-level architecture specifications efficiently. It streamlines the process of turning PRDs into actionable architectural documents, ensuring that all necessary technical considerations are addressed in a systematic manner.
When to use it
Use this skill when you need to create a high-level architecture document from a product requirements document for a software epic.
When not to use it
This skill may not be suitable for simple projects or when detailed coding is required, as it focuses on architecture specification rather than implementation.
What you can build with it
Creating a New Epic Architecture
When starting a new software epic, this skill helps in structuring the architecture based on the provided PRD.
Updating Existing Architecture
Use this skill to revise and enhance the architecture of an existing epic based on new requirements or feedback.
Team Collaboration on Architecture Planning
Facilitate discussions among team members by providing a clear architecture specification that outlines all components and their interactions.
How to install Epic Architecture Specification
View source1. Install with the skills CLI
npx skills add github/awesome-copilot/breakdown-epic-arch --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by githubEpic 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]
Frequently asked questions about Epic Architecture Specification
Similar skills
Markdown to HTML Conversion
Efficiently convert Markdown documents to HTML.
Code Tour
Create structured walkthroughs for codebases.
Acquire Codebase Knowledge
Streamline onboarding with comprehensive codebase documentation.
Documentation & Modernization
Streamline codebase documentation and modernization planning.
Azure Resource Visualizer
Generate architecture diagrams for Azure resources.
CLAUDE.md Improver
Optimize your CLAUDE.md files for better project context.