Back to Skills

breakdown-epic-arch

Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.

30,587stars3,654forksUpdated 4/21/2026

Security Assessment

Safe(96/100)
Security Score96/100

About breakdown-epic-arch

This skill is a prompt that turns Copilot into a Senior Software Architect and guides it to produce a high-level technical architecture specification for an Epic, based on a Product Requirements Document. It solves the gap between product-level requirements and engineering execution by generating a structured architecture document that outlines the major components, features, and technical enablers needed to build the epic.

The skill takes an Epic PRD as input and outputs a complete Markdown specification saved to a conventional docs path. The specification follows a defined structure: an architecture overview, a comprehensive Mermaid system-architecture diagram organized into user, application, service, data, and infrastructure layers with color coding and data-flow arrows, a list of high-level features and technical enablers, a technology stack, a technical value estimate, and a t-shirt size estimate. It carries opinionated context assumptions about the target stack, including domain-driven architecture, self-hosted and SaaS deployment, Docker containerization, a TypeScript/Next.js App Router stack, Turborepo monorepo patterns, tRPC for type-safe APIs, and Stack Auth for authentication. The prompt instructs the model to avoid writing code except for pseudocode where technically necessary.

It targets software architects, tech leads, and product-minded engineers who plan work in epics and want a consistent, diagram-rich architecture artifact to guide implementation. It is a documentation and planning prompt with no scripts, commands, or destructive behavior.

FAQ

What input does the skill need?

An Epic Product Requirements Document (PRD). The skill uses it as the basis for the high-level technical architecture specification.

What does the output look like?

A complete Markdown architecture specification with an overview, a Mermaid system diagram, high-level features and technical enablers, a technology stack, a technical value estimate, and a t-shirt size estimate, saved to a conventional docs path.

Does it assume a particular tech stack?

Yes. Its context considerations assume domain-driven architecture, Docker, TypeScript/Next.js with App Router, Turborepo, tRPC, Stack Auth, and both self-hosted and SaaS deployment; you would adapt these to your project.

Will it write application code?

No. The prompt explicitly instructs the model not to write code in the output unless it is pseudocode for technical situations.

What is the Mermaid diagram meant to show?

A layered system architecture spanning user, application, service, data, and infrastructure layers with subgraphs, consistent color coding, and both synchronous and asynchronous data flows relevant to the epic.

Install breakdown-epic-arch

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill