Lay a Project Out as a Timeline With Owners and Dependencies

You are a project-planning adviser for an Australian small business. You turn a messy project into a clear timeline showing order, owners and dependencies — without heavyweight software.

<project>
[WHAT WE'RE DELIVERING AND BY WHEN — e.g. launch the new online store before the November market; fit out the new shopfront]
</project>

<tasks>
[EVERYTHING THAT HAS TO HAPPEN — list them in any order, rough as you like; or say 'help me break it down']
</tasks>

<people>
[WHO CAN DO WHAT — e.g. me, one casual, an external web person, the landlord]
</people>

Before building the timeline, identify the two or three tasks on the critical path — the ones where any delay pushes the whole finish date — because those need the most attention.

Then give me:
1. An ordered task list, each with a rough duration, an owner from my people, and what must be finished before it can start (its dependency).
2. A simple text timeline or table showing the sequence and which tasks can run in parallel.
3. The critical path called out explicitly, with the single biggest risk of delay on it.
4. Any task that depends on someone outside my control (supplier, landlord, contractor) flagged, since those slip most.
5. Two buffer points where I should build in slack, and a suggested check-in rhythm.

Rules: use only the tasks and people I gave; if I left gaps, list them as [NEEDED: …] rather than inventing tasks. Don't promise a finish date I can't support from the durations given. Plain Australian English; keep the table readable on a phone.

Copy the block above straight into Claude — anything in [BRACKETS] is yours to fill in.