30 Claude Prompts That Build Gantt Charts

You are a content marketing lead planning a themed campaign. <context> I need a content campaign schedule, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Campaign theme and goal: [E.G. THOUGHT LEADERSHIP, LEADS] - Duration: [E.G. 8 WEEKS] - Start date: [YYYY-MM-DD] - Content types: [BLOG, VIDEO, EMAIL, SOCIAL, LEAD MAGNET] - Team: [WRITER, DESIGNER, EDITOR] </inputs> <task> Build a Gantt chart with sections for Strategy (theme, keywords, editorial calendar), Production (each content piece as tasks: draft, edit, design, publish), Distribution (email, social, paid, partners), and Measurement (weekly review, end-of-campaign report). Use after: dependencies so drafts precede design and publish, stagger publish dates across the campaign, add a launch milestone and a wrap-up report milestone, and mark the cornerstone/lead-magnet piece as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Draft -> edit -> design -> publish sequence for each piece; distribution follows each publish. - Include weekly measurement checkpoints and a final report milestone. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note the production lead time needed before the first publish date. </format>

You are a campaign manager building the marketing plan around a product launch. <context> I need a launch campaign timeline, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Product and launch date: [NAME, YYYY-MM-DD] - Audience and channels: [WHO, WHERE] - Budget split: [ORGANIC / PAID] - Assets available: [WHAT EXISTS ALREADY] - Team: [WHO OWNS WHAT] </inputs> <task> Build a Gantt chart with sections for Tease (teaser content, waitlist, sneak peeks), Build-Up (creative production, ad setup, PR outreach, influencer briefs), Launch Week (email blast, social, paid go-live, PR embargo lift, community push), and Sustain (retargeting, testimonials, recap content). Work backward from the launch date, phase activities across tease/build-up/launch/sustain, add a launch-day milestone and a campaign-end milestone, and mark ad-creative approval and PR embargo as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Creative and ad setup complete before launch week; PR embargo lifts on launch day. - Include a teaser phase before launch and a sustain phase after; launch-day milestone included. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note the asset-production tasks that gate the launch date. </format>

You are an integrated marketing manager coordinating a multi-channel campaign. <context> I need a coordinated timeline showing every channel side by side, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Campaign objective: [AWARENESS / LEADS / SALES] - Channels: [EMAIL, SOCIAL, PAID, SEO, PR, EVENTS] - Duration and start: [WEEKS, YYYY-MM-DD] - Key offer or message: [DETAILS] - Team owners per channel: [WHO] </inputs> <task> Build a Gantt chart with one section per channel (Email, Social, Paid, SEO/Content, PR). Within each, schedule the channel's activities across the campaign so I can see overlaps and gaps. Add cross-channel milestones for kickoff, mid-campaign push, and wrap-up, sequence prerequisite tasks with after: dependencies, and mark the hero asset that all channels reuse as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - One section per channel so parallel activity is visible at a glance. - Shared milestones align the channels; hero asset produced before channels activate. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note where channels are overloaded on the same week. </format>

You are an SEO strategist scheduling a site-wide SEO project. <context> I need a phased SEO project timeline, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Site and current state: [DOMAIN, TRAFFIC BASELINE] - Primary goal: [RANKINGS / TRAFFIC / LEADS] - Scope: [TECHNICAL, CONTENT, LINKS] - Start date: [YYYY-MM-DD] - Team / resources: [WHO] </inputs> <task> Build a Gantt chart with sections for Audit (technical crawl, content audit, keyword research, competitor analysis), Technical Fixes (site speed, crawlability, schema, redirects), Content (pillar pages, cluster articles, on-page optimization), Off-Page (digital PR, link building, outreach), and Measurement (monthly reporting, ranking checks). Sequence with after: dependencies so the audit precedes fixes, run content and links in parallel, add milestones for audit-complete and first-content-live, and mark the technical fixes as crit since they gate ranking gains. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Audit precedes all execution; technical fixes precede or overlap content. - Include monthly reporting checkpoints and an audit-complete milestone. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note the realistic lag before ranking improvements show up. </format>

You are a lifecycle marketer building and launching an email nurture sequence. <context> I need a project timeline to build, test, and launch an automated email sequence, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Sequence purpose: [ONBOARDING / LEAD NURTURE / WINBACK] - Number of emails: [E.G. 6] - ESP / tool: [E.G. HUBSPOT, KLAVIYO] - Start date: [YYYY-MM-DD] - Team: [COPY, DESIGN, DEV] </inputs> <task> Build a Gantt chart with sections for Planning (goal, audience, flow map, triggers), Copy (draft each email, review, finalize), Design (templates, build in ESP), QA (link/render tests, seed sends, logic check), and Launch (activate, monitor, optimize). Use after: dependencies so copy precedes design precedes QA, add milestones for flow-approved and go-live, and mark the automation/logic build in the ESP as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Copy -> design -> build -> QA sequence; automation logic tested before go-live. - Include a seed-send/QA task and a post-launch optimization task. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note how to add an A/B test task to the launch phase. </format>

You are a general contractor scheduling a home renovation. <context> I need a renovation schedule showing trades in the right order, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Project scope: [E.G. KITCHEN + BATH REMODEL] - Property: [ROOMS / SQFT AFFECTED] - Start date: [YYYY-MM-DD] - Permits required: [YES / NO, WHICH] - Hard deadline: [DATE OR NONE] </inputs> <task> Build a Gantt chart with sections for Pre-Construction (design, permits, materials ordering), Demolition, Rough-In (framing, plumbing, electrical, HVAC), Inspections, Finishes (drywall, paint, flooring, cabinets, fixtures), and Close-Out (final inspection, punch list, cleanup). Sequence trades in correct construction order with after: dependencies, place inspection milestones after rough-in and at close-out, model long material lead times as tasks, and mark permits and long-lead materials as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Trades sequenced correctly (rough-in before inspection before finishes); no impossible overlaps. - Include inspection milestones and model permit + material lead times explicitly. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note which lead-time items to order before demolition even starts. </format>

You are a construction project manager scheduling a commercial build-out. <context> I need a construction schedule for a commercial project, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Project type and size: [E.G. 5,000 SQFT OFFICE FIT-OUT] - Start date: [YYYY-MM-DD] - Target completion: [DATE] - Key subs: [MECHANICAL, ELECTRICAL, PLUMBING, ETC] - Permits / approvals needed: [LIST] </inputs> <task> Build a Gantt chart with sections for Pre-Construction (permits, submittals, procurement, mobilization), Structure/Envelope, MEP Rough-In (mechanical, electrical, plumbing, fire), Inspections, Interior Build (framing, drywall, ceilings, flooring, millwork), and Commissioning & Handover (testing, punch list, occupancy). Sequence with after: dependencies in correct construction order, add inspection and substantial-completion milestones, model procurement lead times, and mark permits, long-lead equipment, and inspections as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Correct trade sequencing with rough-in before inspection before closing walls. - Include a substantial-completion milestone and an occupancy/handover milestone. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note the procurement and inspection items most likely to be on the critical path. </format>

You are a facilities and operations manager planning an office move. <context> I need an office relocation timeline that keeps the business running, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Company size: [HEADCOUNT] - Move-out and move-in dates: [YYYY-MM-DD] - New space status: [READY / NEEDS FIT-OUT] - IT setup needs: [NETWORK, PHONES, SERVERS] - Planning start: [YYYY-MM-DD] </inputs> <task> Build a Gantt chart with sections for Planning (new lease, floor plan, budget, vendor selection), New-Space Prep (fit-out, furniture, IT/network install), Logistics (moving company, packing plan, insurance), IT Cutover (network provisioning, phone/internet transfer, server migration, testing), Move Weekend (pack, transport, unpack, verify), and Settle-In (address changes, snags, welcome). Sequence with after: dependencies so IT provisioning finishes before cutover, add milestones for space-ready and move-complete, and mark internet/network provisioning and lease dates as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - IT/network provisioning has long lead time and gates the cutover; minimize business downtime. - Include a move-weekend block and a space-ready milestone. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note the single task (usually internet install) that most threatens the move date. </format>

You are a production planner scheduling a manufacturing run. <context> I need a production schedule for a batch/run, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Product and batch size: [WHAT, HOW MANY UNITS] - Start date: [YYYY-MM-DD] - Ship-by date: [DATE] - Key stages: [E.G. MATERIALS, ASSEMBLY, QC, PACK] - Constraints: [LINE CAPACITY, SHIFTS, SUPPLIER LEAD TIMES] </inputs> <task> Build a Gantt chart with sections for Procurement (raw materials, components, incoming QC), Setup (line changeover, tooling, first-article approval), Production (assembly stages, in-line QC), Finishing (final QC, packaging, labeling), and Fulfillment (palletize, ship). Sequence with after: dependencies to respect line flow, model supplier lead times as explicit tasks, add milestones for materials-in, first-article-approved, and ship-ready, and mark material lead times and first-article approval as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Materials and incoming QC precede setup; first-article approval gates full production. - Include a ship-ready milestone and respect the ship-by date. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note how a material delay cascades to the ship date. </format>

You are a maintenance planner scheduling a planned facility shutdown (turnaround). <context> I need a shutdown/turnaround schedule that minimizes downtime, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Facility / equipment: [WHAT IS BEING SERVICED] - Shutdown window: [YYYY-MM-DD to YYYY-MM-DD] - Work scope: [INSPECTION, REPAIRS, UPGRADES] - Crews / contractors: [WHO] - Safety / permit requirements: [LOCKOUT, PERMITS] </inputs> <task> Build a Gantt chart with sections for Pre-Shutdown (planning, parts procurement, permits, contractor scheduling), Shutdown & Isolation (safe shutdown, lockout/tagout, isolation), Execution (inspection, repairs, replacements, upgrades in dependency order), Testing & Restart (reassembly, testing, commissioning), and Ramp-Up (restart, verify, return to service). Sequence with after: dependencies, compress execution to minimize downtime, add milestones for isolation-complete and back-online, and mark permit/lockout and long-lead parts as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Isolation/lockout precedes any physical work; parts procured before shutdown starts. - Include an isolation-complete milestone and a back-online milestone; keep downtime minimal. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note which parallel work would shorten the downtime window. </format>

You are a study coach building a structured exam-prep schedule. <context> I need a study plan leading up to a certification exam, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Exam / certification: [E.G. PMP, AWS, CPA] - Exam date: [YYYY-MM-DD] - Study start date: [YYYY-MM-DD] - Hours per week available: [NUMBER] - Topics / domains to cover: [LIST] </inputs> <task> Build a Gantt chart with sections for Foundation (syllabus review, resource setup, baseline test), Content Study (one task per topic/domain, sized to weight), Practice (practice questions, timed quizzes per domain), Review (weak-area review, full-length mock exams), and Final Prep (last review, rest day). Work backward from the exam date to fit the weekly hours, add milestones for halfway-check and mock-exam-1, and mark the highest-weight domains and the final mock exam as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Topic durations scaled to exam weighting and the weekly hours available. - Include at least two full-length mock exams and a light rest day before the exam. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note how to compress the plan if I fall a week behind. </format>

You are a career coach structuring a focused job search. <context> I need a job-search plan with clear weekly actions, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Target role and industry: [DETAILS] - Current status: [EMPLOYED / SEARCHING FULL-TIME] - Start date: [YYYY-MM-DD] - Target offer-by date: [DATE OR NONE] - Hours per week available: [NUMBER] </inputs> <task> Build a Gantt chart with sections for Prep (resume, LinkedIn, portfolio, target-company list), Skill/Interview Prep (skills gaps, mock interviews, story bank), Outreach (networking, applications, referrals — as recurring weekly tasks), Interviewing (screens, rounds, take-homes), and Closing (references, negotiation, decision). Sequence with after: dependencies so prep precedes outreach, run outreach as ongoing weekly tasks, add milestones for materials-ready and first-interview, and mark resume/portfolio readiness as crit since it gates applying. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Materials finished before outreach begins; outreach and interview prep run in parallel. - Include a weekly application/networking cadence and a negotiation task. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note a realistic weekly application target to hit the offer-by date. </format>

You are a running coach building a periodized marathon training plan. <context> I need a marathon training schedule, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Race date: [YYYY-MM-DD] - Current fitness: [E.G. RUNS 15 MILES/WEEK] - Goal: [FINISH / TIME TARGET] - Training start date: [YYYY-MM-DD] - Days per week available: [NUMBER] </inputs> <task> Build a Gantt chart with sections for Base Building, Build Phase, Peak Phase, Taper, and Race Week. Within each phase schedule the weekly training blocks (easy runs, long runs, speed/tempo, rest, cross-training) as tasks, progressively increasing long-run distance, add milestones for longest-run and taper-start, place a taper before the race, and mark the peak long runs and the taper as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Weekly mileage progresses safely (roughly 10% rule) with recovery weeks built in. - Include a proper taper before race week and a longest-run milestone ~3 weeks out. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note how to shift the plan if I miss a training week to injury. </format>

You are a writing coach planning a long-form writing project. <context> I need a writing schedule to finish a book or thesis, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Project and target length: [E.G. 60,000-WORD BOOK / THESIS] - Number of chapters/sections: [NUMBER] - Start date: [YYYY-MM-DD] - Deadline: [YYYY-MM-DD] - Writing hours per week: [NUMBER] </inputs> <task> Build a Gantt chart with sections for Planning (outline, research, structure), Drafting (one task per chapter/section, sized to length), Revision (self-edit per chapter, full read-through), Feedback (send to readers/advisor, incorporate notes), and Finalize (proofread, formatting, submission). Work backward from the deadline to fit the weekly hours, sequence with after: dependencies, add milestones for outline-done, first-draft-complete, and final-submission, and mark the full first-draft and advisor feedback as crit. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Chapter durations scaled to word count and the weekly writing hours available. - Include a feedback/review loop and buffer before the final deadline. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note where to add buffer for the inevitable revision overrun. </format>

You are a language tutor designing a 90-day learning sprint. <context> I need a 90-day language learning schedule, returned as a self-contained Mermaid gantt chart I can render instantly as an artifact. </context> <inputs> - Language and current level: [E.G. SPANISH, BEGINNER] - Goal by day 90: [E.G. HOLD A 10-MIN CONVERSATION] - Start date: [YYYY-MM-DD] - Study time per day: [MINUTES] - Preferred methods: [APP, TUTOR, IMMERSION, FLASHCARDS] </inputs> <task> Build a Gantt chart with sections for Month 1 (foundations: alphabet/sounds, core vocab, present tense, basic phrases), Month 2 (expansion: past/future tenses, listening, speaking practice), and Month 3 (fluency push: conversation practice, immersion, review), plus a Habits section for daily recurring practice. Schedule skills progressively with after: dependencies where they build on each other, add milestones for first-conversation and mid-point-assessment, and mark speaking practice as crit since it's the goal. </task> <constraints> - Valid Mermaid gantt syntax: gantt, title, dateFormat YYYY-MM-DD, axisFormat. - Skills build progressively (grammar before conversation); daily practice runs throughout. - Include a mid-point assessment milestone and a day-90 goal milestone. </constraints> <format> Return the Mermaid gantt code in a ```mermaid code block as a ready-to-render artifact, then note how to add weekly tutor sessions as a recurring task. </format>