dev-architecture-playbook
Installation
SKILL.md
Dev Architecture Playbook
Purpose
Use this as the lifecycle router before starting broad product or architecture work. It chooses the minimum useful skill chain, defines gates, and prevents starting implementation before the required contracts exist.
Route
Classify the request first:
| Request | Primary Skills | Output |
|---|---|---|
| Idea, product direction, or market/user problem | product-discovery, prd-master |
Product brief, user stories, success metrics |
| Architecture or module boundaries | architecture-foundation, technical-spec, elegant-architecture |
Architecture spec, boundaries, rejected alternatives |
| API, auth, data, or schema contract | api-design, auth-security, database-patterns, data-contract-migrations |
Versioned contracts and migration plan |
| UI/product surface | frontend-design, ui-ux-pro-max, ui-design-system, playwright-automation |
UX flow, component plan, visual checks |
| Implementation workflow | fixflow, plan-flow, threads, systematic-debugging |
Step-test-update plan and ownership |
| Quality and regression risk | comprehensive-testing, codebase-audit, vibeguard, project-health-auditor |
Test matrix and risk list |
| Release and operations | release-engineering, config-secrets-environments, performance-capacity, incident-slo-runbook, observability-sre, devops-excellence |
Rollout, config, capacity, SLO, runbook |