nfr-architecture-mapping

Non-functional requirement mapping translates performance, scalability, and security needs into specific architectural patterns and technology choices. This Skill generates comprehensive architecture documents that link each NFR to design decisions, implementation patterns, and Architecture Decision Records (ADRs) that justify your choices across frontend, backend, and fullstack projects.

Architecture mapping generates architecture documents with detected project type, complexity scoring, ADRs created, included sections, and traceable rationale for each technology decision. Outputs include architecture file paths, scale-adaptive depth based on project scope, and multi-domain coverage for new features, major upgrades, or cross-domain integrations.

Yes. Architecture mapping translates PRDs and epics into technical architecture, pattern selections, and ADRs. It applies across multi-domain use cases such as new features, major upgrades, and cross-domain integrations, producing detailed technical specifications with justified technology choices.

Architecture mapping uses scale-adaptive depth, automatically adjusting documentation richness based on project complexity. It calculates a complexity score and tailors ADR count and section depth to match frontend, backend, or fullstack project scope and integration requirements.

Architecture mapping explicitly links non-functional requirements like performance and security to specific architectural decisions and implementation patterns. It produces Architecture Decision Records with technology justification and traceable rationale, not generic design guidance.

Architecture mapping provides guidance on implementation patterns to satisfy NFRs, so foundational familiarity with architecture concepts helps but is not required. The Skill includes examples and ADR references that support pattern selection across frontend, backend, and fullstack contexts.