design-with-traceability

Map requirements to architecture by generating traceable technical designs that tag all components, APIs, and data models with REQ-* keys. This ensures each architectural element connects explicitly to its source requirement, creating a verifiable chain from business rules through functional and non-functional requirements to implementation artifacts.

Maintain traceability by systematically tagging design artifacts—services, endpoints, schemas, and interactions—with REQ-* identifiers linked to validated requirements. This practice prevents design drift, simplifies compliance verification, and makes requirement changes easier to propagate through the architecture.

Yes. From validated REQ-* requirements, you can generate API contracts with traceable endpoint definitions and data model schemas with relationship specifications. Each design artifact receives REQ-* tagging so its origin requirement and coverage are immediately visible.

Yes. This Skill operates on validated REQ-* requirements as input. Pre-validation ensures requirements are complete, consistent, and ready for architecture mapping, preventing rework when non-functional and business-rule requirements emerge during design.

Functional requirements drive service and module boundaries—what the system does. Non-functional requirements (security, performance, scalability) shape component interactions, data model choices, and API contracts. Both are tagged in the resulting architecture so design decisions remain auditable.

Uncovered requirements create gaps in traceability. By tagging all components, APIs, and data models with REQ-* keys, missing coverage becomes visible immediately, triggering design iteration or requirement clarification before implementation begins.