williamlimasilva/breakdown-epic-arch
skills/breakdown-epic-arch/SKILL.md
Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
documentation
Updated Apr 29, 2026
$ install --global
skillsauthnpx skillsauth add williamlimasilva/.copilot breakdown-epic-archInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 1:29 AM101.3s1 file scanned
SKILL.md
- name:
- breakdown-epic-arch
- description:
- Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
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]
Related Skills
williamlimasilva/workshop-create
tools
VerifiedTrustedCommunity
Create a new workshop or use an existing directory as one. Handles two paths: (A) use an existing local directory the operator points at, or (B) create a new private GitHub repo in the signed-in account. Never creates a repo inside another repo.
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/vcpkg
development
VerifiedTrustedCommunity
Guide for setting up vcpkg in C++ projects, managing dependency versions, and cross-compiling. Covers manifest initialization, CMake and Visual Studio integration, classic-to-manifest migration, version pinning, baselines, overrides, triplets, and cross-compilation. Use when a user is working with vcpkg project setup, installation, version management, or cross-platform builds. For specialized tasks, additional references cover custom registries and overlay ports (references/registries.md), CI/CD and binary caching (references/ci.md), and troubleshooting and dependency lifecycle (references/troubleshooting.md).
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/signal-write
testing
VerifiedTrustedCommunity
Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals/ for dashboard consumption and noted in the journal for persistence.
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/markstream-install
development
VerifiedTrustedCommunity
Install and configure Markstream streaming Markdown renderers for Vue, React, Svelte, Angular, Nuxt, and Vue 2 applications. Use for package selection, minimal peer dependencies, CSS order, SSR boundaries, streaming mode, and renderer setup.
SKILL.mdUpdated Jul 22, 2026