Mapping Dependencies & Risks

Link Types Explained

Depends On →

Feature A depends on Feature B means A cannot work without B being built first.

Example: "User Dashboard" depends on "User Authentication"

Blocks ⛔

Feature A blocks Feature B means A must be completed before B can start.

Example: "Database Schema" blocks "Data Migration"

Conflicts With ⚠️

Features that cannot coexist or require choosing between them.

Example: "SQL Database" conflicts with "NoSQL Database"

Contributes To 🎯

Shows how a feature helps achieve an objective or persona need.

Checklist:

• [ ] Add 3+ "Depends on" links
• [ ] Identify at least one potential conflict
• [ ] Link features to objectives with "Contributes to"

Detecting Issues

The system warns you about:

• Circular dependencies (A→B→A)
• Conflicts in MVP
• Blocked must-have features

Tip: Use Indicators view to see completeness and detect issues early!