breakdown-epic-arch

Generate a technical architecture specification from a Product Requirements Document.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/lluppesms/dadabase.demo --skill breakdown-epic-arch-lluppesms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-epic-arch
Source: https://github.com/lluppesms/dadabase.demo/tree/main/.github/skills/breakdown-epic-arch
Command: npx skills add https://github.com/lluppesms/dadabase.demo --skill breakdown-epic-arch-lluppesms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of a high-level technical architecture specification for an Epic, based on its Product Requirements Document (PRD), ensuring a solid technical foundation for development.

Core Features & Use Cases

  • Automated Architecture Generation: Generates a comprehensive technical architecture document from an Epic PRD.
  • Key Component Identification: Outlines system architecture, features, technical enablers, and technology stack.
  • Use Case: A Product Manager provides an Epic PRD for a new user authentication module. This Skill generates the technical architecture document, including a Mermaid diagram, technology stack (TypeScript/Next.js, Stack Auth, tRPC), and estimated t-shirt size, ready for the engineering team.

Quick Start

Use the breakdown-epic-arch skill to generate the architecture for the epic described in the attached 'user-onboarding-epic.md' file.

Frequently Asked Questions about breakdown-epic-arch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a technical architecture specification from a PRD?

You create a technical architecture specification by processing an Epic PRD to outline system architecture, features, technical enablers, and technology stack, outputting a structured Markdown document with a Mermaid system architecture diagram.

What is included in an automated high-level system architecture document?

A high-level system architecture document includes outlined features, technical enablers, a specific technology stack utilizing TypeScript, Next.js, tRPC, and Stack Auth, plus a Mermaid system architecture diagram for visual representation.

How do I create a Mermaid system architecture diagram for a software epic?

You generate a Mermaid system architecture diagram by processing the Epic PRD through an automated specification tool, which outputs a Markdown file containing the visual Mermaid diagram mapping the system architecture.

Can I use this architecture generation approach with TypeScript, Next.js, and Turborepo?

Yes, this approach specifically supports TypeScript, Next.js, Turborepo, tRPC, and Stack Auth, ensuring the generated architecture specification adheres to domain-driven design and containerization principles for your stack.

Does automated technical specification generation support domain-driven design and containerization?

Yes, automated technical specification generation explicitly adheres to domain-driven design and containerization principles, structuring the system architecture and technology stack to fit containerized environments and bounded contexts.