Skip to content
cccskills
FreePublished on GitHub

breakdown-epic-arch

Turn a product requirements document for a major development initiative into a technical architecture specification, including a Mermaid system diagram, major features, supporting technologies, technical value, and a rough size estimate.

OriginalShow the original description

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

Works withDocker
See how to install

Good for

  • Turning product requirements into a technical architecture
  • Visualizing system layers and data flows
  • Identifying services and infrastructure needed for features
  • Estimating technical value and overall development size

Files included (1)

  • SKILL.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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]

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Map an existing codebase into seven documents covering its technology, structure, architecture, conventions, integrations, tests, and concerns. Link findings to file evidence, mark unknowns, and highlight differences between stated plans and the actual implementation.

  • Get oriented in an unfamiliar codebase
  • Prepare documentation for a project handover
  • Compare documented architecture with implementation
github/awesome-copilot40.2KUpdated Oct 17, 2026

Assess a repository’s readiness for AI agents with AgentRC and generate a standalone HTML dashboard. Review scores across nine areas, see prioritized improvements, and optionally apply scoring policies tailored to an organization.

  • Assessing a repository’s readiness for AI agents
  • Prioritizing improvements from assessment results
  • Reviewing scores under an organization’s own policy
github/awesome-copilot40.2KUpdated Oct 17, 2026

Generate coding agent instruction files from a project's actual code using AgentRC. Capture detected languages, frameworks, and conventions in one shared file or split rules by topic and project area, with a preview before writing.

  • Create project instructions for VS Code Copilot
  • Refresh agent rules after project changes
  • Split monorepo instructions by project area
github/awesome-copilot40.2KUpdated Oct 17, 2026

Customize AgentRC readiness assessments to match team or organization standards. Choose or create policies that adjust check importance, disable irrelevant checks, set pass thresholds, and define requirements for automated checks in CI workflows.

  • Set shared readiness standards across an organization
  • Focus assessments on AI tooling
  • Adjust the importance of individual checks
github/awesome-copilot40.2KUpdated Oct 17, 2026

Analyze supplied ad performance data to identify wasted spend, strong campaigns, and next tests. Compare channels, assess whether test differences are meaningful, and produce budget reallocation recommendations with a prioritized action plan.

  • Identify ads and keywords to pause
  • Find campaigns and audiences worth scaling
  • Assess whether A/B test results are meaningful
github/awesome-copilot40.2KUpdated Oct 17, 2026

Turn code files into learning resources by adding comments that explain syntax, programming concepts, and design choices. Adjust explanation depth and repetition to the reader’s knowledge while preserving file structure, encoding, and syntax.

  • Add beginner-friendly explanations to existing code
  • Document the reasoning behind syntax and design choices
  • Adjust comment depth for readers with different experience
github/awesome-copilot40.2KUpdated Oct 17, 2026

See all skills by github

Report a problem with this skill