jyjeanne/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.
$ install --global
skillsauthnpx skillsauth add jyjeanne/ai-setup-forge 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: Apr 20, 2026, 9:08 PM145.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
jyjeanne/legacy-circuit-mockups
development
VerifiedTrustedCommunity
Generate breadboard circuit mockups and visual diagrams using HTML5 Canvas drawing techniques. Use when asked to create circuit layouts, visualize electronic component placements, draw breadboard diagrams, mockup 6502 builds, generate retro computer schematics, or design vintage electronics projects. Supports 555 timers, W65C02S microprocessors, 28C256 EEPROMs, W65C22 VIA chips, 7400-series logic gates, LEDs, resistors, capacitors, switches, buttons, crystals, and wires.
1SKILL.mdUpdated Apr 6, 2026
jyjeanne/lean-ux
development
VerifiedTrustedCommunity
Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "UX experiment", "collaborative design", or "outcome over output". Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.
1SKILL.mdUpdated Apr 6, 2026
jyjeanne/lean-startup
development
VerifiedTrustedCommunity
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", or "test assumptions". Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done.
1SKILL.mdUpdated Apr 6, 2026
jyjeanne/langsmith
tools
VerifiedTrustedCommunity
Instrument, trace, evaluate, and monitor LLM applications and AI agents with LangSmith. Use when setting up observability for LLM pipelines, running offline or online evaluations, managing prompts in the Prompt Hub, creating datasets for regression testing, or deploying agent servers. Triggers on: langsmith, langchain tracing, llm tracing, llm observability, llm evaluation, trace llm calls, @traceable, wrap_openai, langsmith evaluate, langsmith dataset, langsmith feedback, langsmith prompt hub, langsmith project, llm monitoring, llm debugging, llm quality, openevals, langsmith cli, langsmith experiment, annotate llm, llm judge.
1SKILL.mdUpdated Apr 6, 2026