How to use the Project Dependency Mapper.
Dependencies should describe a real prerequisite. Distinguish work that must finish first from work that merely shares a preferred date.
Make the workflow fit your task.
Identify the prerequisite for each task and distinguish necessary sequencing from preferred timing. Record the relationship and inspect loops or missing predecessors before using the map to build a schedule.
- What you provide
- Task list and prerequisite notes.
- What you get
- Dependency relationships and possible circular dependencies.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Testing needs the completed import parser; documentation can start from the agreed specification.
Completed example
Link testing to parser completion while allowing documentation preparation to proceed independently.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should tasks sharing a date automatically be linked as dependencies?
No. Link them only when one genuinely requires the other's output, access or decision. Shared timing can be a planning preference.
Why does the dependency map prevent work that could start now?
Check whether a finish requirement was assumed unnecessarily. Some preparation may proceed from an approved specification before implementation is complete.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑