feature-backbone-specialist

User story mapping structures project requirements by organizing features and tasks chronologically based on user interaction. It transforms raw requirements into a structured user journey map, defining high-level features and granular user tasks.

Decompose project requirements by identifying high-level features in [Actor] [Action] [Result] [Object] format, then breaking them down into actionable user tasks formatted as [Action] [Result] [Object] to map the complete user journey chronologically.

Yes, you can map feature dependencies when organizing a product backlog. The process identifies critical and recommended dependencies between high-level features to ensure proper chronological sequencing of user tasks.

Define high-level features by utilizing context analysis to establish the project domain, user goals, and core capabilities. Format these broad goals as [Actor] [Action] [Result] [Object] to clearly outline intended user interactions.

Yes, this approach works for task decomposition in e-commerce platforms. It identifies features like user shopping and purchase completion, breaking them into granular tasks such as browsing the product catalog and selecting a payment method.