pre-dev-feature-map

Feature mapping clarifies how features relate, group, and interact at a business level before architectural decisions. It extracts features from requirements, identifies user journeys, categorizes them (Core/Supporting/Enhancement), groups them into domains, and defines integration points and boundaries—preventing misaligned architectures and poor module boundaries downstream.

Organize features by categorizing them functionally, then group related features into logical business domains. Map user journeys to visualize how users flow through features and identify cross-feature interactions, integration points, and phased delivery priorities without detailing technical implementations.

Feature mapping fits between product requirements (PRD) and technical architecture (TRD). Apply it early when you have multiple features with complex interactions and need to define domains, journeys, boundaries, and priorities before making architectural decisions.

Yes. Feature mapping explicitly identifies integration points and boundaries by analyzing how features interact and depend on each other. This visibility prevents missed connections and helps design clean module boundaries aligned with business logic.

No. Feature mapping works entirely at the business level without detailing technical implementations. It focuses on feature relationships, user journeys, categorization, and boundaries—leaving technical decisions for the architecture phase.