skills.rest
ultraviollettnympho
ultraviollettnymphoCOMMUNITY
Explore all skills by this author →
GitHub

breakdown-epic-arch

Generates a high-level technical architecture specification from an Epic PRD.

1|1|Updated Jan 29, 2026
Search Tags:#planning#architecture#system design#mermaid#technical specification#prd#epic
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill breakdown-epic-arch-ultraviollettnympho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: breakdown-epic-arch
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/breakdown-epic-arch
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill breakdown-epic-arch-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Translating a Product Requirements Document into a concrete technical plan is time-consuming and inconsistent across teams. This Skill turns an Epic PRD into a structured architecture specification that guides development. ## Core Features & Use Cases - Architecture Specification Generation: Produces a complete Epic Architecture document with overview, features, technical enablers, technology stack, value assessment, and t-shirt size estimate. - System Architecture Diagrams: Creates Mermaid diagrams covering user, application, service, data, and infrastructure layers. - Use Case: A product manager hands off an Epic PRD for a new notifications feature; the Skill outputs an arch.md file with a layered Mermaid diagram, tRPC and PostgreSQL component breakdown, and an effort estimate saved to the project docs folder. ## Quick Start Ask the AI to create the technical architecture specification for the Epic PRD in docs/ways-of-work/plan/notifications/epic.md.

Frequently Asked Questions about breakdown-epic-arch

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

FAQPage Schema
How do I create a technical architecture document from a PRD?▼

Provide the Epic PRD content as context and invoke the architecture prompt. It outputs a structured Markdown specification with an overview, Mermaid system diagram, features, enablers, stack, and sizing estimate saved to the plan directory.

What does the Epic architecture specification include?▼

The specification includes an architecture overview, a Mermaid diagram spanning user, application, service, data, and infrastructure layers, high-level features and technical enablers, a technology stack list, technical value rating, and a t-shirt size estimate.

Does the architecture output include actual code?▼

No, the specification explicitly avoids writing implementation code. Only pseudocode is permitted when needed to clarify technical situations, keeping the document focused on design decisions rather than implementation.

What technology stack does the architecture prompt assume?▼

The prompt assumes a TypeScript and Next.js stack with App Router, Turborepo monorepo patterns, tRPC APIs, Stack Auth for authentication, PostgreSQL, Redis, Qdrant, and Docker containerization for self-hosted and SaaS deployments.

Where is the generated architecture document saved?▼

The output is saved as arch.md under /docs/ways-of-work/plan/{epic-name}/, keeping architecture specifications organized alongside the corresponding Epic planning documents.

Related Skills

Explore More Software Engineering Skills→
codetail-aicodetail-ai

pm

Creates structured PRDs with user stories, acceptance criteria, and scope boundaries.

Official
Advanced
uutauuta
1

sub-issue-maker

Break down high-level product goals into concrete subtasks with ownership, estimates, dependencies, and acceptance criteria.

Community
Basic
saeed-vayghansaeed-vayghan
30

architect-reviewer

Review system designs and architectural patterns for scalability and maintainability.

Community
Advanced
govctl-orggovctl-org
239

quick

__init__

Official
Basic