dependency-mapping_skill

Overview

This skill maps implementation slice dependencies using a Design Structure Matrix (DSM), computes risk and leverage scores, and recommends an execution sequence. It helps teams identify blockers, prioritize safe ships, and surface where reusing design patterns reduces risk. The output is a ranked list of slices with clear remediation recommendations.

How this skill works

Build a square DSM with slices on both axes and mark dependencies (row depends on column). Calculate fan-in and fan-out for each slice, then score leverage by checking existing design-system components and Storybook patterns. Combine dependency count, leverage score, and priority tier into a Risk Score to rank slices and surface blockers and recommended sequencing.

When to use it

• During Ask mode Phase 2 (CONVERGE) when planning multi-slice features
• Before phasing or sprint planning to determine safe implementation order
• When you need to identify blockers that force early shipping or stubbing
• When evaluating reuse opportunities versus building new patterns
• When backend contract or data-model changes may increase scope

Best practices

• Populate the DSM collaboratively with engineers and designers to capture implicit dependencies
• Verify leverage scoring against /docs/design-system/components.md and Storybook (.stories.tsx)
• Treat high fan-in slices as blockers—consider stubs or early delivery
• Prefer shipping low-risk slices first to unblock iterative testing
• Revisit the DSM as design or API contracts change; risk is dynamic

Example use cases

• Plan rollout for a members experience that spans UI, API, and data changes
• Decide whether to implement a shared WorkspaceInvite entity early or stub it
• Prioritize frontend-only widgets that reuse design-system components
• Choose safe order for features requiring backend contract updates
• Quantify trade-offs when composing multiple design-system components vs creating new patterns