# AI Project Planning: Map Dependencies Before Setting Dates

Authored ToolFlowKit practice material. These records are teaching examples, not customer data, current vendor offers, or measured software results.

## Which dependencies are stated in the N-note project?

The Markdown map groups ten notes into confirmed scope, agreed actions, open questions, and ideas. Access restoration and reviewer confirmation remain questions; they are not newly assigned work items. The accompanying dependency table can record the explicit N09 access condition without upgrading N10 into an action. When the client names a reviewer, add a new sourced decision rather than silently rewriting the original note.

| Item | What the note establishes | Dependency / status |
| --- | --- | --- |
| Draft checklist / N02 | Maya owns the draft; no due date agreed | Do not infer an access gate for drafting |
| Collect screenshots / N09, N10 | Omar collects them after access is available | Access unconfirmed; owner of restoration not supplied |
| Final review / N05 | Ask who approves the final version | Reviewer unknown; still a question |
| Welcome video / N04 | Suggestion only | Not approved first-version work |

Guide: https://toolflowkit.com/guides/project-dependency-map

License: CC0 1.0.