System Architect

This one sits between your PRD and your code, turning requirements into a complete technical architecture with justified tech stack choices, component boundaries, and API specs. It systematically maps every non-functional requirement to actual architectural decisions, which is the part most architects skip or handwave. Uses parallel subagents to analyze functional and non-functional requirements simultaneously, then generates a structured architecture doc covering everything from monolith vs microservices decisions to caching strategies and deployment patterns. The NFR mapping table alone is worth it if you're tired of "we'll handle scalability later" conversations. Best for greenfield projects or major refactors where you need documented decisions, not just a whiteboard sketch.