Classify task dependencies by finish and start types
Structure unorganized project backlogs into precise chronological logic. Use this when setting up Gantt charts, critical paths, or sprint sequences.
You getTask Sequence Table, critical Path Sequence and schedule Risks
Prompt
Act as a project planning engineer. Transform the unstructured task list provided below into a structured dependency map using standard project scheduling relationships.
Rules:
- Classify each relationship into Finish-to-Start (FS), Start-to-Start (SS), Finish-to-Finish (FF), or Start-to-Finish (SF).
- Identify the exact predecessor task number for every entry.
- Highlight tasks that form the critical path where delays would break the target end date.
- Call out any circular dependencies or missing prerequisite tasks.
Output format:
1. Task Sequence Table (Columns: ID, Task Name, Predecessor ID, Dependency Type, Lag/Lead If Any)
2. Critical Path Sequence (ordered list of core blocking tasks)
3. Schedule Risks (bulleted list of fragile handoffs or unstated prerequisites)
My raw task list is below:Example output
Paste your messy list of tasks and deadlines into Gemini, Claude, or ChatGPT. Follow up by asking the model to reformat the table into CSV format so you can import it directly into MS Project, Asana, or Jira.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Level team capacity using schedule float
Balance team workloads across sprints by shifting non-critical tasks into available schedule slack. Use this when some teammates are overbooked while critical path float remains.
Sequence parallel project workstreams to cut delivery time
Rearrange sequential tasks into safe parallel tracks to shorten schedules without overburdening resources. Use this during sprint planning or critical path reviews.
Calculate critical path and task float
Identify sequence bottlenecks and calculate total float to see which delayed tasks directly shift your final delivery date.
Evaluate schedule compression using crashing and fast tracking
Assess schedule acceleration tradeoffs across cost, risk, and dependencies. Use this when facing hard completion deadlines to avoid unplanned rework and budget overrun.
Turn a delayed project schedule into a recovery plan
Re-sequence critical paths, reallocate resources, and eliminate wishful scheduling when deadlines slip. Use it after a major project delay.
Audit a RACI chart for split accountability
Identify dangerous governance flaws, duplicate owners, and delivery bottlenecks in an existing RACI matrix. Use this before launching high-stakes projects.