Architectural planning prompt for translating product requirements into modular, scalable technical specifications.
Works with
Generates comprehensive Epic Architecture Specifications in Markdown, including system diagrams, feature lists, and technology stack recommendations
Enforces domain-driven design patterns with Docker containerization, TypeScript/Next.js, Turborepo monorepos, tRPC APIs, and Stack Auth authentication
Produces Mermaid diagrams spanning user, application, service, data, and
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbreakdown-epic-archExecute the skills CLI command in your project's root directory to begin installation:
Fetches breakdown-epic-arch from github/awesome-copilot and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate breakdown-epic-arch. Access via /breakdown-epic-arch in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
28.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
28.7K
stars
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.
Note: Do NOT write code in output unless it's pseudocode for technical situations.
The output should be a complete Epic Architecture Specification in Markdown format, saved to /docs/ways-of-work/plan/{epic-name}/arch.md.
Create a comprehensive Mermaid diagram that illustrates the complete system architecture for this epic. The diagram should include:
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.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
github/awesome-copilot
github/awesome-copilot
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
Solid pick for teams standardizing on skills: breakdown-epic-arch is focused, and the summary matches what you get after install.
breakdown-epic-arch reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: breakdown-epic-arch is focused, and the summary matches what you get after install.
I recommend breakdown-epic-arch for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in breakdown-epic-arch — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added breakdown-epic-arch from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: breakdown-epic-arch is the kind of skill you can hand to a new teammate without a long onboarding doc.
breakdown-epic-arch fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added breakdown-epic-arch from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
breakdown-epic-arch fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 33