30 Claude Prompts That Build Workflows

You are a site reliability engineer who writes incident-response runbooks used under pressure. <context> I need an incident response workflow so when a production issue hits, the team detects, triages, communicates, and resolves it without confusion. The output is a self-contained runbook. </context> <inputs> - System and typical failure modes: [WHAT BREAKS] - Severity levels and definitions: [E.G. SEV1 = FULL OUTAGE] - On-call roles: [INCIDENT COMMANDER, RESPONDER, COMMS] - Alerting and comms tools: [E.G. PAGERDUTY, SLACK, STATUSPAGE] - Stakeholders to notify per severity: [WHO] - Post-incident requirements: [POSTMORTEM POLICY] </inputs> <task> Build an incident response workflow: a detection-and-declaration step with severity classification, role assignment (who becomes incident commander), an investigation-and-mitigation loop, a communication cadence tied to severity (internal and status-page updates), a resolution-and-recovery step, and a post-incident review trigger with a blameless postmortem template outline. Include an escalation ladder by time-elapsed. </task> <constraints> - Severity classification must map to concrete criteria and dictate the comms cadence. - Assign explicit roles at declaration; include the time-based escalation ladder. - The runbook must be numbered and unambiguous for use during a live incident. </constraints> <format> Return the runbook as a numbered workflow plus a severity-to-response table and a postmortem outline, then note the one step teams most often skip in the heat of an incident. </format>

You are a security incident responder who writes breach-response playbooks that hold up under regulatory scrutiny. <context> I need a security breach response workflow covering containment, investigation, notification, and recovery, with clear ownership and evidence handling. The output is a self-contained playbook. </context> <inputs> - Systems and data types at risk: [E.G. CUSTOMER PII, PAYMENT DATA] - Breach types to cover: [E.G. CREDENTIAL LEAK, RANSOMWARE, DATA EXFIL] - Response team roles: [SECURITY LEAD, LEGAL, COMMS, EXEC] - Regulatory obligations: [E.G. GDPR 72-HOUR, STATE LAWS] - Tools and logs available: [SIEM, EDR, AUDIT LOGS] - External parties: [FORENSICS, INSURANCE, COUNSEL] </inputs> <task> Build a breach response workflow: a detection-and-triage step confirming scope and severity, an immediate containment step, an evidence-preservation step with chain-of-custody notes, an investigation step to determine impact and affected records, a legal-and-regulatory notification decision (with deadline clocks), a customer and stakeholder communication step, and an eradication-and-recovery step. Include a post-incident hardening review. </task> <constraints> - Containment and evidence preservation must come before eradication; do not destroy evidence. - Include the regulatory notification deadline clock and who decides; name owners per step. - The notification decision must resolve clearly (notify / not required) with the criterion. </constraints> <format> Return the playbook as a numbered workflow plus a notification-decision tree with deadline clocks, then note the most time-sensitive first hour actions. </format>

You are a communications lead who designs outage-communication workflows that protect trust. <context> I need an outage communication workflow so customers get timely, honest updates during a service disruption across the right channels, without the team improvising messaging. The output is a ready-to-use flow with templates. </context> <inputs> - Product and typical outage impact: [WHAT USERS LOSE] - Channels available: [STATUS PAGE, EMAIL, IN-APP, SOCIAL, SUPPORT] - Severity tiers: [PARTIAL / MAJOR / FULL] - Who approves external messages: [ROLES] - Update cadence expectations: [E.G. EVERY 30 MIN FOR MAJOR] - Tools used: [E.G. STATUSPAGE, INTERCOM] </inputs> <task> Build an outage comms workflow: a trigger tied to incident severity, a first-response step (acknowledge within X minutes) with an approval gate, an update-cadence loop per severity across the chosen channels, a resolution message step, and a post-incident follow-up step. Provide short fill-in-the-blank message templates for acknowledgment, ongoing update, and resolution, each with placeholders. </task> <constraints> - Time-to-first-response and update cadence must scale with severity; specify both. - Include an approval gate for external messages; name the owner and channels per tier. - Templates must be honest and specific with placeholders, no vague reassurance. </constraints> <format> Return the workflow plus the three message templates, then note the biggest trust mistake companies make during outages and how the flow avoids it. </format>

You are an engineering manager who designs bug triage workflows that keep the backlog sane. <context> I need a bug triage and escalation workflow so incoming bugs get consistently prioritized, assigned, and escalated when they are urgent, without everything becoming a fire. The output is a self-contained flow. </context> <inputs> - Where bugs come in: [SUPPORT, USERS, MONITORING, QA] - Priority levels and criteria: [E.G. P0 = DATA LOSS, P1 = CORE BROKEN] - Teams and owners: [WHO TRIAGES, WHO FIXES] - SLAs per priority: [E.G. P0 SAME DAY, P3 BACKLOG] - Tools used: [E.G. LINEAR, JIRA, SENTRY] - Reproduction requirements: [WHAT A VALID BUG NEEDS] </inputs> <task> Build a bug triage workflow: an intake-and-validation step (required repro info), a prioritization decision tree assigning P0-P3 by concrete criteria, routing to the owning team, an SLA clock per priority, an escalation branch when a P0/P1 stalls or impact grows, a fix-and-verify step, and a close-with-communication step back to the reporter. Include a duplicate-and-cannot-reproduce handling branch. </task> <constraints> - Prioritization must use concrete criteria that classify every bug into P0-P3. - Include SLAs per priority and the escalation trigger; require valid repro info at intake. - Handle duplicates and non-reproducible reports explicitly. </constraints> <format> Return the workflow as a prioritization decision tree plus an SLA table, then note how to auto-route P0s to on-call. </format>

You are a crisis communications strategist who builds response workflows for reputation-threatening events. <context> I need a crisis communication workflow so when a PR issue breaks (bad press, viral complaint, exec misstep), the team assesses, aligns, and responds fast and consistently. The output is a ready-to-use playbook. </context> <inputs> - Business and likely crisis types: [E.G. PRODUCT SAFETY, DATA, EXEC CONDUCT] - Spokespeople and approvers: [WHO SPEAKS, WHO SIGNS OFF] - Channels: [PRESS, SOCIAL, INTERNAL, CUSTOMERS] - Severity tiers and triggers: [WHAT COUNTS AS A CRISIS] - Legal involvement rules: [WHEN LEGAL MUST REVIEW] - Monitoring tools: [E.G. SOCIAL LISTENING] </inputs> <task> Build a crisis comms workflow: a detection-and-assessment step scoring severity, an activation step convening the response team with roles, a holding-statement step (approved, fast), a fact-gathering and legal-review loop, a coordinated response step across channels with a single approved narrative, a monitoring-and-adjust loop, and a stand-down and debrief step. Provide a holding-statement template with placeholders. </task> <constraints> - Severity assessment must gate the level of response; specify the criteria. - Include the legal-review rule and a single-source-of-truth narrative to prevent mixed messaging. - The holding statement must be fast and approvable; name approvers per channel. </constraints> <format> Return the workflow plus the holding-statement template, then note the first three moves in the first hour of a crisis. </format>

You are a content operations manager who designs end-to-end editorial pipelines. <context> I need a blog production workflow that moves an idea from brief to published post on a repeatable schedule, with clear owners and no bottlenecks. The output is a self-contained pipeline doc. </context> <inputs> - Publishing cadence: [E.G. 2 POSTS/WEEK] - Team and roles: [STRATEGIST, WRITER, EDITOR, SEO, DESIGNER] - Stages I want: [E.G. IDEATION, BRIEF, DRAFT, EDIT, SEO, PUBLISH] - Tools used: [E.G. NOTION, GOOGLE DOCS, WORDPRESS] - Quality bar per stage: [WHAT MUST BE TRUE TO ADVANCE] - Distribution channels after publish: [LIST] </inputs> <task> Build a content pipeline with named stages, each showing the owner, the input, the work done, the exit criteria to advance, and a target duration. Include an ideation-and-prioritization step, a brief-approval gate, a draft-and-edit loop, an SEO-and-metadata step, a design/asset step, a publish step, and a distribution step. Add a lead-time estimate from idea to live and a WIP limit per stage. </task> <constraints> - Each stage needs explicit exit criteria, not just a name; include durations and a WIP limit. - Order stages so nothing advances before its input is ready; name one owner per stage. - Include the post-publish distribution step; no vague "promote it". </constraints> <format> Return the pipeline as a stage table plus a Mermaid flow, then note the stage most likely to bottleneck and how the WIP limit protects throughput. </format>

You are a social media operations lead who designs multi-platform content workflows. <context> I need a social content workflow that takes ideas through creation, approval, scheduling, and reporting across platforms on a weekly rhythm. The output is a ready-to-use process. </context> <inputs> - Platforms: [E.G. LINKEDIN, X, INSTAGRAM, TIKTOK] - Posting frequency per platform: [DEFINE] - Roles: [CREATOR, DESIGNER, APPROVER, ANALYST] - Content types: [E.G. THREADS, REELS, CAROUSELS] - Tools used: [E.G. BUFFER, CANVA, NOTION] - Brand and approval rules: [WHAT NEEDS SIGN-OFF] </inputs> <task> Build a social content workflow on a weekly cycle: a planning step tied to a content calendar, a creation step per content type, an asset/design step, an approval gate with brand rules, a scheduling step per platform with best-time notes, a publishing step, and a weekly reporting-and-learn step feeding next week's plan. For each step give the owner, the tool, and the deadline within the week. </task> <constraints> - Map the workflow to a weekly cycle with specific days for each step. - Include the approval gate and platform-specific scheduling; name owners and tools. - The reporting step must feed back into planning; specify the metrics reviewed. </constraints> <format> Return the workflow as a weekly-cycle table plus a content-calendar template outline, then note how to batch-create to cut weekly overhead. </format>

You are a video production manager who designs pipelines from concept to published video. <context> I need a video production workflow covering pre-production, shooting, editing, and publishing so videos ship on schedule with clear handoffs. The output is a self-contained pipeline. </context> <inputs> - Video types and length: [E.G. YOUTUBE 10-MIN, SHORTS, ADS] - Team and roles: [PRODUCER, EDITOR, SCRIPTWRITER, THUMBNAIL DESIGNER] - Output cadence: [E.G. 1 LONG-FORM/WEEK] - Tools used: [E.G. PREMIERE, FRAME.IO, YOUTUBE] - Review and approval points: [WHERE SIGN-OFF HAPPENS] - Distribution and repurposing plan: [WHERE IT GOES AFTER] </inputs> <task> Build a video pipeline across phases: pre-production (concept, script, shot list, approval gate), production (record with a checklist), post-production (rough cut, review loop, final cut, thumbnail and title), and publish (upload, metadata, schedule) plus repurposing into shorts and clips. Each step shows owner, input, output, review point, and target duration. Include a review-loop cap so edits do not spiral. </task> <constraints> - Each phase has explicit exit criteria and a review point; cap the number of edit review rounds. - Include the repurposing step; name owners and durations per step. - The script must be approved before shooting; enforce that gate. </constraints> <format> Return the pipeline as a phased table plus a Mermaid flow, then note where projects usually slip and how the review-round cap prevents it. </format>

You are a newsletter operations lead who designs reliable send-day workflows. <context> I need a newsletter production workflow that takes each issue from planning to send with QA, so nothing goes out with broken links or the wrong subject. The output is a ready-to-run process. </context> <inputs> - Cadence and send day/time: [E.G. THURSDAY 9AM] - Sections in each issue: [E.G. INTRO, MAIN, LINKS, CTA] - Roles: [WRITER, EDITOR, APPROVER] - Tools used: [E.G. BEEHIIV, MAILERLITE, NOTION] - QA checks required: [LINKS, RENDERING, SUBJECT, SEGMENTS] - Success metrics tracked: [OPEN, CLICK, UNSUBS] </inputs> <task> Build a newsletter workflow counted down to send day: a planning step, a drafting step per section, an editing pass, an approval gate, a build-in-tool step, a pre-send QA checklist (links, test send, rendering, subject line, segment selection), the scheduled send, and a post-send review step tracking the key metrics. For each step give the owner and the deadline relative to send day. </task> <constraints> - Deadlines are offsets from send day (e.g. send day minus 1); include the explicit pre-send QA checklist. - No issue sends without passing QA and approval; enforce both gates. - The post-send step must record metrics that inform the next issue. </constraints> <format> Return the workflow as a countdown-to-send table plus the pre-send QA checklist, then note the single check that catches the most embarrassing errors. </format>

You are a managing editor who designs editorial planning and review workflows. <context> I need an editorial calendar workflow that plans content ahead, assigns it, and moves each piece through a consistent review before publishing across content types. The output is a self-contained flow plus a calendar structure. </context> <inputs> - Content types managed: [E.G. BLOG, VIDEO, SOCIAL, EMAIL] - Planning horizon: [E.G. QUARTERLY THEMES, MONTHLY SLOTS] - Team and roles: [EDITOR, WRITERS, REVIEWERS] - Review stages: [E.G. STRUCTURAL, LINE, FACT-CHECK, FINAL] - Tools used: [E.G. NOTION, AIRTABLE, GOOGLE CALENDAR] - Status labels you use: [IDEA, ASSIGNED, IN REVIEW, SCHEDULED, PUBLISHED] </inputs> <task> Build two linked artifacts: (1) an editorial calendar structure (fields, statuses, and how items flow across the planning horizon) and (2) a review workflow where each piece passes named review stages, each with a reviewer, what they check, and the exit gate. Include an assignment step tying content to owners and dates, a status-transition map, and a re-work loop with mandatory feedback. </task> <constraints> - Define the calendar fields and every status with a clear transition rule between them. - Each review stage names the reviewer and their specific checklist; feedback on rework is mandatory. - No status jumps allowed; the transition map must be complete. </constraints> <format> Return the calendar structure as a field/status table and the review workflow as a stage table plus a Mermaid status-transition diagram, then note how to set up the calendar in your tool of choice. </format>

You are a revenue operations designer who builds lead routing and qualification workflows. <context> I need an inbound lead workflow that qualifies, scores, and routes every new lead to the right rep fast so nothing sits untouched. The output is a self-contained flow with routing rules. </context> <inputs> - Lead sources: [E.G. DEMO FORM, CONTENT, CHAT] - Qualification criteria: [E.G. ICP FIT, COMPANY SIZE, INTENT] - Scoring model or tiers: [HOW LEADS ARE RANKED] - Sales team structure: [SEGMENTS, TERRITORIES, ROUND-ROBIN] - SLA to first touch: [E.G. 5 MINUTES FOR HOT] - Tools used: [E.G. HUBSPOT, SALESFORCE, SLACK] </inputs> <task> Build an inbound lead workflow: a capture-and-enrichment step, a qualification decision tree separating MQL from unqualified with clear criteria, a scoring-and-tiering step, a routing step assigning leads to reps by segment/territory/round-robin, an SLA clock to first touch with an auto-reassign branch if missed, and a follow-up-cadence handoff. Include a disqualified branch with a nurture route. </task> <constraints> - Qualification criteria must classify every lead into a clear tier or disqualified. - Include the first-touch SLA and the auto-reassign branch when it is missed; name routing rules. - Disqualified leads go to nurture, not the trash; specify that route. </constraints> <format> Return the flow as a qualification decision tree plus a routing table, then note how to enforce the first-touch SLA with an alert automation. </format>

You are a sales operations lead who designs pipeline stage definitions and exit criteria. <context> I need a sales pipeline workflow with well-defined stages, entry/exit criteria, and required actions so forecasting is accurate and deals do not stall in limbo. The output is a self-contained stage playbook. </context> <inputs> - Sales motion: [E.G. SELF-SERVE, SMB, ENTERPRISE] - Stages I use or want: [E.G. QUALIFY, DEMO, PROPOSAL, NEGOTIATE, CLOSE] - Average deal size and cycle: [CONTEXT] - What must be true to advance each stage: [EXIT CRITERIA] - Tools used: [E.G. SALESFORCE, HUBSPOT] - Stall rules: [WHEN A DEAL IS AT RISK] </inputs> <task> Build a pipeline workflow defining each stage with: entry criteria, the rep's required actions, the exit criteria to advance, the expected duration, and the forecast probability. Include a definition of a qualified deal, required fields per stage for clean data, a stalled-deal rule with a re-engage or close-lost branch, and a won/lost step with a reason-code capture. </task> <constraints> - Every stage needs objective, verifiable exit criteria, not gut feel; specify required fields. - Include the stalled-deal rule and mandatory win/loss reason codes. - Probabilities and durations must be attached to each stage. </constraints> <format> Return the workflow as a stage-definition table plus a Mermaid pipeline flow with the stalled-deal branch, then note the exit criterion most often faked and how to enforce it. </format>

You are a revenue operations lead who designs clean sales-to-customer-success handoffs. <context> I need a deal handoff workflow so when a deal closes, customer success gets everything they need to onboard the account without the customer repeating themselves. The output is a self-contained flow with a handoff template. </context> <inputs> - What CS needs to know: [GOALS, STAKEHOLDERS, PROMISES MADE, TECH SETUP] - Roles: [AE, CSM, ONBOARDING, SALES ENGINEER] - Trigger: [DEAL MARKED CLOSED-WON] - Handoff format: [DOC, MEETING, BOTH] - Tools used: [E.G. SALESFORCE, GAINSIGHT, SLACK] - SLA to first CS contact: [E.G. WITHIN 24 HOURS] </inputs> <task> Build a handoff workflow triggered by closed-won: an AE handoff-doc completion step (with a required-fields template), a handoff-meeting step between AE and CSM, a CS account-setup step, a customer kickoff-scheduling step within the SLA, and an internal confirmation step that the handoff is complete. Include a branch for incomplete handoffs that blocks CS from starting blind, and capture any commitments the AE made during the sale. </task> <constraints> - The handoff doc must capture goals, stakeholders, promises made, and technical setup; make those fields required. - Include the SLA to first customer contact and the incomplete-handoff block. - Explicitly record sales commitments so CS honors them. </constraints> <format> Return the workflow plus the handoff-doc template (fields and sections), then note the single item most often lost in handoffs and how to guarantee it transfers. </format>

You are an outbound sales strategist who designs multi-touch prospecting cadences. <context> I need an outbound prospecting workflow with a structured multi-channel cadence so reps work leads consistently instead of ad hoc, with clear steps and timing. The output is a ready-to-run cadence. </context> <inputs> - Target persona and segment: [WHO WE PROSPECT] - Channels available: [EMAIL, LINKEDIN, CALL, VIDEO] - Cadence length and touches: [E.G. 14 DAYS, 8 TOUCHES] - Value props / hooks to test: [WHAT RESONATES] - Reply and meeting-booked handling: [WHAT TO DO ON RESPONSE] - Tools used: [E.G. APOLLO, OUTREACH, SALESLOFT] </inputs> <task> Build a prospecting cadence workflow: an enrollment step with entry criteria, a day-by-day sequence of touches specifying channel, action, and message angle per step, a reply-handling branch (positive, objection, not-now, no-response) with the next action for each, a meeting-booked exit that hands off to the next stage, and an end-of-cadence branch (recycle vs disqualify). For each touch give the timing and the goal. </task> <constraints> - The cadence must specify channel and timing for every touch across the sequence. - Include reply-handling branches for each response type; define enrollment entry criteria. - End-of-cadence must resolve to recycle or disqualify, not silence. </constraints> <format> Return the cadence as a day-by-day touch table plus a reply-handling decision tree, then note the touch most likely to book meetings and where to place it. </format>

You are a revenue operations designer who builds quote-to-cash process workflows. <context> I need a quote-to-cash workflow so a closed deal turns into an accurate quote, signed contract, invoice, and collected payment without revenue leaking or steps being skipped. The output is a self-contained process doc. </context> <inputs> - What we sell and pricing model: [SUBSCRIPTION, USAGE, ONE-TIME] - Discount approval rules: [WHO APPROVES WHAT DISCOUNT] - Contract and signature process: [TOOL, WHO SIGNS] - Billing and payment terms: [NET 30, ETC] - Roles: [AE, DEAL DESK, FINANCE, BILLING] - Tools used: [E.G. SALESFORCE CPQ, STRIPE, DOCUSIGN] </inputs> <task> Build a quote-to-cash workflow: a quote-creation step with pricing rules, a discount-approval gate by threshold, a contract-generation-and-signature step, an order-booking step that syncs to billing, an invoicing step with terms, a payment-collection-and-dunning loop for overdue invoices, and a revenue-recognition/handoff step. Each step names the owner, the system, and the control that prevents errors or leakage. </task> <constraints> - The discount gate must route by threshold to the right approver with no bypass. - Include the dunning loop for overdue invoices and a control at each step to prevent revenue leakage. - Booking must sync cleanly to billing; name owners and systems throughout. </constraints> <format> Return the workflow as a step table plus a Mermaid flow showing the discount gate and dunning loop, then note the two points where revenue most often leaks and the controls that plug them. </format>