{"kind":"Skill","metadata":{"namespace":"community","name":"breakdown-epic-arch","version":"0.1.0"},"spec":{"description":"Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.","files":{"SKILL.md":"---\nname: breakdown-epic-arch\ndescription: 'Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.'\n---\n\n# Epic Architecture Specification Prompt\n\n## Goal\n\nAct 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.\n\n## Context Considerations\n\n- The Epic PRD from the Product Manager.\n- **Domain-driven architecture** pattern for modular, scalable applications.\n- **Self-hosted and SaaS deployment** requirements.\n- **Docker containerization** for all services.\n- **TypeScript/Next.js** stack with App Router.\n- **Turborepo monorepo** patterns.\n- **tRPC** for type-safe APIs.\n- **Stack Auth** for authentication.\n\n**Note:** Do NOT write code in output unless it's pseudocode for technical situations.\n\n## Output Format\n\nThe output should be a complete Epic Architecture Specification in Markdown format, saved to `/docs/ways-of-work/plan/{epic-name}/arch.md`.\n\n### Specification Structure\n\n#### 1. Epic Architecture Overview\n\n- A brief summary of the technical approach for the epic.\n\n#### 2. System Architecture Diagram\n\nCreate a comprehensive Mermaid diagram that illustrates the complete system architecture for this epic. The diagram should include:\n\n- **User Layer**: Show how different user types (web browsers, mobile apps, admin interfaces) interact with the system\n- **Application Layer**: Depict load balancers, application instances, and authentication services (Stack Auth)\n- **Service Layer**: Include tRPC APIs, background services, workflow engines (n8n), and any epic-specific services\n- **Data Layer**: Show databases (PostgreSQL), vector databases (Qdrant), caching layers (Redis), and external API integrations\n- **Infrastructure Layer**: Represent Docker containerization and deployment architecture\n\nUse 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.\n\n#### 3. High-Level Features \u0026 Technical Enablers\n\n- A list of the high-level features to be built.\n- A list of technical enablers (e.g., new services, libraries, infrastructure) required to support the features.\n\n#### 4. Technology Stack\n\n- A list of the key technologies, frameworks, and libraries to be used.\n\n#### 5. Technical Value\n\n- Estimate the technical value (e.g., High, Medium, Low) with a brief justification.\n\n#### 6. T-Shirt Size Estimate\n\n- Provide a high-level t-shirt size estimate for the epic (e.g., S, M, L, XL).\n\n## Context Template\n\n- **Epic PRD:** [The content of the Epic PRD markdown file]\n"},"import":{"commit_sha":"541b7819d8c3545c6df122491af4fa1eae415779","imported_at":"2026-05-18T20:05:35Z","license_text":"MIT License\n\nCopyright GitHub, Inc.\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.","owner":"github","repo":"github/awesome-copilot","source_url":"https://github.com/github/awesome-copilot/tree/541b7819d8c3545c6df122491af4fa1eae415779/plugins/project-planning/skills/breakdown-epic-arch"}},"content_hash":[24,13,245,125,179,239,70,106,121,91,123,162,193,140,100,129,207,33,136,72,54,183,200,108,249,75,45,222,137,244,162,116],"trust_level":"unsigned","yanked":false}