Identify project dependencies, blockers, and the critical path

작성자: AILesson8 분 소요테스트::ChatGPT검토일: 2026-08-28

빠른 답변

Map task relationships and separate active blockers from risks before calculating schedule impact. 제공할 내용: Tasks, durations, and status, Dependencies and constraints, Planning rules. 예상 결과: An evidence-aware dependency map with blockers, schedule scenarios, owners, and missing data.

맥락 추가

텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.

Tasks, durations, and statusDependencies and constraintsPlanning rules

프롬프트

채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다

Analyze the project schedule using only the supplied facts.

Tasks, estimates, status, and owners:
[tasks]

Stated dependencies, constraints, assumptions, and issues:
[relationships]

Target, calendar, parallel-work rules, buffers, and authority:
[calendar]

Preserve every task ID. Classify each relationship as finish-to-start, start-to-start, finish-to-finish, external dependency, resource constraint, approval gate, assumption, active blocker, or risk; explain ambiguous classifications. An active blocker must be preventing work now, while a risk is only a possible future event. Check for missing predecessors, circular dependencies, unsupported dates, overloaded shared resources, and tasks with no owner or completion criterion.

Calculate earliest dates, float, and a critical path only when durations, dependency logic, calendar, and start conditions are sufficient. Otherwise provide bounded scenarios and name exactly what prevents a defensible calculation. Do not treat the longest task list as a critical path or invent links. Show any arithmetic. End with the highest-leverage unblock actions, an owner or Unassigned, evidence needed, latest useful decision date, and a reconciliation check covering all task IDs.

Playground에서 사용해 보기

기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.

입력에서 결과까지

적용 예시

구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요

실제 입력

Tasks, durations, and status: A (Mina): finalize copy, 2 working days, not started. B (Leo): translate approved copy, 3 days, not started. C (Ravi): implement page shell, 4 days, 2 days remaining. D (Ravi): insert final copy, 1 day. E (QA, owner unassigned): accessibility and browser test, 2 days. F (Mina): publish, 0.5 day. Work starts Monday 31 August 2026.
Dependencies and constraints: B starts after A approval. D needs B and C complete. E follows D. F follows E and legal approval. Legal review was requested but no reviewer or duration is recorded. Ravi cannot work on C and D simultaneously. The translation vendor might be unavailable next week, but Leo is currently assigned internally.
Planning rules: Monday-Friday, no holidays. Target publication Friday 11 September 2026. No schedule buffer. Mina can assign QA; department head can escalate legal review. Use whole or half working days.

예시 출력

Coverage: A-F all retained. Stated logic is A→B; B and C→D; D→E; E and legal approval→F. A approval is an approval gate whose duration/authority is missing. Legal is an external approval gate and an active blocker for a defensible publication date because reviewer and duration are unknown, although it does not stop C today. Vendor availability is a risk, not a blocker, because Leo is assigned internally. QA ownership is missing.

Known-duration network from 31 Aug: A occupies 31 Aug-1 Sep; B 2-4 Sep. C's remaining two days can run 31 Aug-1 Sep. D therefore starts 7 Sep and finishes that day; E runs 8-9 Sep; F needs half a day after E, so the task chain can finish 10 Sep if approvals are instantaneous and available. The controlling known chain is A-B-D-E-F at 8.5 working days versus C-D-E-F at 5.5 remaining days, leaving C roughly 3 working days of path float under those assumptions. This is a provisional controlling path, not a complete critical path, because A-approval and legal durations are absent.

Unblock now: Mina assigns QA and defines E completion evidence by 31 Aug. Department head names the legal reviewer, obtains duration/SLA, and confirms whether review can run before E; latest useful answer is 2 Sep to protect the 11 Sep target. Mina also records A approver. Recalculate once both gates are modeled. No circular link appears; Ravi's resource constraint does not add delay because D already waits for B.

효과가 있는 이유

1
Separating blockers, risks, assumptions, and constraints prevents teams from escalating unlike problems as if they were equivalent
2
Conditional critical-path calculation avoids false schedule precision when estimates or links are incomplete

결과 확인

Is every supplied task preserved and every inferred relationship explicitly labeled
Are current blockers separated from possible risks and ordinary constraints
Is any critical path supported by visible durations, logic, calendar, and arithmetic

안심하고 사용하세요

자주 묻는 질문

이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변

What should I prepare before using “Identify project dependencies, blockers, and the critical path”?

For “Identify project dependencies, blockers, and the critical path,” prepare Tasks, durations, and status, Dependencies and constraints, and Planning rules. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.

When is the “Identify project dependencies, blockers, and the critical path” result not ready to use?

The result is not ready if it does not yet deliver the stated outcome—An evidence-aware dependency map with blockers, schedule scenarios, owners, and missing data—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.

Which AI tools have recorded tests for “Identify project dependencies, blockers, and the critical path”?

The published test record for “Identify project dependencies, blockers, and the critical path” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.

더 많은 탐색 방법