skilld
All skills
github avatar

/breakdown-epic-arch

@90921cc official
by githubgithub/awesome-copilot40k stars
5,040

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

Ask your Agent

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/breakdown-epic-arch

This session only. Nothing lands on disk.

SKILL.md

≈33 tokens always: the name and description. ≈671 when used: this 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]

Source: SKILL.md on GitHub

Third-party checks

1 warning16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill is an architecture specification prompt that processes external Product Requirements Documents (PRDs). It contains an inherent indirect prompt injection vulnerability surface because it ingests untrusted text without structural boundaries or validation.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    1/1 file flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 90921cc. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 18 hours ago.

Activeupdated 7 months ago

Topics

  • TypeScript
  • architecture
  • epic-planning
  • prd
  • next.js
  • trpc
  • docker
  • turborepo
  • domain-driven-design

README badge

README badge for github/awesome-copilot/breakdown-epic-arch

What it does

Acts as a Senior Software Architect to transform an Epic PRD into a high-level technical architecture specification, including system diagrams, feature lists, technology stack, and effort estimates. Targets teams using TypeScript, Next.js, Turborepo, tRPC, and Docker who need structured guidance for breaking down large initiatives into architectural components.

Generated from the current SKILL.md.

Frequently asked

Does this skill generate code or just architecture documents?
It generates markdown architecture specifications only, no code. The skill explicitly states not to write code unless it's pseudocode for technical situations.
What stack does this skill assume?
TypeScript/Next.js with App Router, Turborepo monorepo, tRPC APIs, Stack Auth for authentication, Docker containerization, and PostgreSQL with optional Redis and Qdrant.
Can this skill handle both self-hosted and SaaS deployments?
Yes. The skill explicitly considers both self-hosted and SaaS deployment requirements when creating the architecture specification.
What input does this skill require?
An Epic PRD (Product Requirements Document) from a Product Manager. The skill acts as a Senior Software Architect and produces a technical architecture specification based on that PRD.
Does this skill create system diagrams?
Yes. It generates a comprehensive Mermaid diagram showing user, application, service, data, and infrastructure layers with data flow between components.

Generated from the current SKILL.md. These answers refresh after source changes.