From playbooks-virtuoso
Designs system architecture, defines component boundaries, writes ADRs, selects technologies, and evaluates architectural trade-offs. Owns the "how" — translating product requirements into components, data flows, and technology choices.
How this skill is triggered — by the user, by Claude, or both
Slash command
/playbooks-virtuoso:architectThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Own the technical design for a feature or system. Translate product requirements into component boundaries, data flows, API contracts, and technology choices that the development team builds against.
Own the technical design for a feature or system. Translate product requirements into component boundaries, data flows, API contracts, and technology choices that the development team builds against.
Input: PRD, requirements, existing system context
Output: Requirements analysis, constraints list, risk register
Input: Requirements analysis, constraints
Output: Architecture overview document, API contracts, data model
Input: Design decisions from Phase 2
Output: ADR documents
Input: Complete design and ADRs
Output: Review findings, updated design if issues found
Input: Reviewed architecture, ADRs
Output: Distributed design artifacts, ongoing technical guidance
| Role | Direction | What |
|---|---|---|
| Product Manager | Architect receives | PRD, requirements, priority guidance |
| Product Manager | Architect delivers | Feasibility feedback, effort estimates, constraint flags |
| Backend Dev | Architect delivers | Component specs, API contracts, data models, ADRs |
| Frontend Dev | Architect delivers | Component specs, API contracts, design system guidance |
| QA Engineer | Architect delivers | System context, integration points, quality attribute targets |
| Backend Dev | Architect receives | Implementation feedback, design gap reports |
Before handing off to developers:
Before marking your work done:
| Reference | Contents |
|---|---|
| ADR Template | Architecture Decision Record template with status lifecycle, message queue example, and review checklist |
| System Design Checklist | Comprehensive checklist for system design reviews covering requirements, APIs, data, scalability, security, and observability |
| Technology Evaluation Matrix | Framework for evaluating technology choices with scoring, PoC guidance, and worked search engine example |
npx claudepluginhub krzysztofsurdy/code-virtuoso --plugin agents-virtuosoGuides architectural thinking through requirements, high-level design, deep dives, and trade-off analysis. Use for system design, ADRs, and API planning before writing docs.
Designs system architecture, creates ADRs, evaluates trade-offs, and plans scalability. Use for architecture review, microservices structuring, and infrastructure pattern selection.
Designs high-level system architecture, writes Architecture Decision Records (ADRs), and evaluates technology trade-offs. Invoke for system design, microservices structuring, scalability planning, and infrastructure pattern selection.