Map every dependency before a project officially kicks off
Projects stall not because of bad execution but because of unacknowledged dependencies discovered mid-flight. This prompt forces a systematic dependency audit before work begins.
You are acting as my chief of staff performing a dependency audit before project kickoff. Here is the project: {{PROJECT_DESCRIPTION}}. Here are the teams or people involved: {{TEAMS_AND_PEOPLE}}. Here is the target delivery date: {{TARGET_DATE}}. Here are the known risks or constraints I am already aware of: {{KNOWN_RISKS}}.
1. List every category of dependency this project likely has: people, data, tools, approvals, budget, external vendors, legal/compliance, infrastructure, and other teams' timelines. For each category, identify the specific dependency and who owns it.
2. Flag which dependencies are on the critical path (delay them and the project slips) versus supportive (delay them and work continues).
3. For each critical-path dependency, identify: (a) current status — confirmed, assumed, or unknown, (b) the latest date it must be resolved to keep the project on track, and (c) the person accountable for resolving it.
4. Surface any circular dependencies or cases where Team A is waiting on Team B who is waiting on Team A.
5. Output a one-page dependency map I can share at the kickoff meeting, plus a list of the top three dependency conversations I need to have in the next 48 hours.
If the project description is too vague to identify dependencies reliably, ask me up to five clarifying questions before proceeding. {{PROJECT_DESCRIPTION}}{{TEAMS_AND_PEOPLE}}{{TARGET_DATE}}{{KNOWN_RISKS}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{PROJECT_DESCRIPTION}}{{TEAMS_AND_PEOPLE}}{{TARGET_DATE}}{{KNOWN_RISKS}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Perplexity
$0/mo (Pro at $20)AI search engine with citations.
Perplexity is the answer engine Google would build if it weren't protecting search ad revenue. Cited answers, follow-up questions, focused source modes.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.