Starting points for delegated work—answers, tools, and follow-ups depend on what you have connected and your plan. Nothing here is a guarantee of a specific integration; it is the shape of work FAi is built for. For guides, FAQs, and documentation, see Resources.
Browse by category
Showing all 106 examples
Hey FAi, can you check the top 20 trending stocks, get all the prices, and rank them by how close they are to the 52-week high? Then create a note for me and add a task and reminder to review tomorrow before the market opens.
Summarize my unread messages from this week that look urgent, draft short replies for the two that only need a yes or no, and block time on my calendar for reviewing the vendor proposal next Tuesday afternoon.
Research three credible sources on how teams our size adopt AI assistants without self-hosting. Give me a tight summary with links, then save it to my notes under a clear title so I can share it.
Look at my calendar for tomorrow, flag anything that overlaps or looks tight on travel time, and draft a one-page brief for my first external meeting including who is on the invite and the stated goal.
Take our Q1 launch goals and turn them into a checklist in my tasks app with due dates, owners where I named them, and a reminder two days before the first milestone.
Compare the two project specs I linked in Notion, list the three biggest gaps or contradictions, and suggest one paragraph I can paste into the status email.
Every Friday at 4pm, pull threads where I'm @mentioned or on threads I started that got replies this week. Summarize in five bullets: what moved, what's blocked, and who owes me something. Put the digest in a note titled 'Week of [date] — inbox digest' and add one task: archive or reply to the top three.
Read the last 30 messages in the #acme-escalation channel. Build a timeline: symptom, what we tried, current owner, next customer-facing commitment. Draft a 120-word update I can paste to the customer success lead with tone: calm, accountable, no jargon.
Find public pricing pages for our three closest competitors in the APAC region. Table: plan name, seat price, annual discount, trial length, and whether SSO is included. Flag anything that undercuts us on the mid tier. Save as a note with sources dated today.
From our Q3 metrics note and the product roadmap doc, draft a 10-slide board outline: narrative arc, one stat per slide, and suggested speaker per slide. Include a 'risks & mitigations' slide with two bullets each. Output as bullet outline only, no full sentences on slides.
Using the incident channel transcript and the status-page updates, write a blameless postmortem: timeline (UTC), root cause hypothesis, what worked in response, three action items with owners and due dates. Create a doc from the template we used last time if you can find it.
I have three interviewer notes for the senior PM role. Extract strengths, concerns, and level calibration (L5 vs L6). Give me a single recommendation paragraph and three behavioral follow-ups for the final round. Redact names in the summary if notes contain them.
List vendor contracts in the legal folder expiring in the next 90 days. For each: renewal notice window, auto-renew flag if mentioned, and who the business owner is from the last email thread. Sort by urgency. Add calendar reminders 14 days before each notice deadline.
In CRM, find opportunities in commit forecast that have no activity in 14 days or no next step. For each account owner, draft a one-line nudge I can send in Slack asking for a concrete next meeting date. Cap at 15 accounts.
Between tag v2.3.0 and v2.4.0, summarize merged PR titles grouped by area: API, UI, infra. User-facing tone, no internal ticket numbers. Include 'breaking changes' if any PRs are labeled breaking. Output markdown suitable for the changelog page.
Write five LinkedIn posts and three X posts for next Tuesday's feature launch. Constraints: no superlatives, one concrete customer outcome per post, include a single CTA to the docs page. Vary length: two short, two medium, one long for LinkedIn.
Compare department spend vs budget for last month from the finance export. Call out the top three variances over 5% with a plain-English hypothesis (seasonality, timing, one-off). Suggest one question for each department head. Keep under one page.
Given the Figma link and our design principles doc, walk the home screen flow and return: accessibility issues (contrast, focus order), copy issues (unclear CTAs), and three prioritized fixes. Format as a table with severity P0-P2.
I'm flying SFO→LHR overnight Wednesday. Block recovery time Thursday morning, move non-critical 1:1s to Friday, and draft an OOO line for Thursday that still points people to the on-call rotation. Respect my focus blocks.
Here's a transcript of a 45-minute podcast on enterprise AI adoption. Extract: five takeaways, two quotes worth sharing, and three actions for our internal wiki. Save the summary to my notes with timestamp links if the transcript has them.
In #all-hands-archive, find decisions that mention 'headcount' or 'hiring freeze' from the last quarter. Summarize decisions and effective dates. If anything contradicts an earlier message, flag the conflict explicitly.
Using the donation export and our tone guide, draft personalized thank-you emails for donors over $500 this month. Reference their city if present, keep under 120 words, include tax language from last year's template.
From the auth spec section on passkeys, generate 12 Gherkin-style scenarios covering happy path, edge cases, and rollback. Mark which need security review. Put them in a new doc linked from the epic.
Build a one-pager for resellers: who we help, typical deal size, objection handling for 'we already have Microsoft', and three proof points with logos we can name publicly. Export as markdown and as bullet talking points for a call.
Compare last year's remote work policy PDF to the draft in the wiki. List every substantive change in plain language, and note anything that might confuse managers. Suggest a 3-bullet all-hands script for HR.
Summarize open P1/P2 tickets for the platform team, what's been tried, and what's still unknown. Include links. Post to #platform-oncall and add a calendar event for the secondary with the same summary in the description.
Review the PR agency's draft quotes attributed to our CEO. Flag anything that overclaims performance, mentions customers without approval, or could read as financial guidance. Suggest safer alternates that keep the punch.
Take the onboarding strings in the sheet and propose UK English variants for spelling and idioms, German informal 'du' tone where appropriate, and JP polite-neutral phrasing. Keep character counts within 10% of English for buttons.
For invoices 30+ days overdue from the AR report, draft a three-email sequence: polite, firmer, final before escalation. Include placeholders for invoice ID and amount. Schedule sends Monday/Wednesday/Friday mornings in my timezone.
From yesterday's product review recording summary, extract decisions, open questions, and owners. Create tasks with due dates: decisions this week, research next week. Link each task back to the timestamp if available.
Pull active reqs for engineering: time-in-stage averages, drop-off after take-home, and diversity stats if fields exist. Compare to Q2. Give me three interventions to try this month with expected effort (S/M/L).
Fill the enterprise security questionnaire using our SOC2 report and last pen test summary. Where we don't have evidence, answer honestly and propose a remediation timeline. Export as a table Question | Answer | Evidence link.
Attendee list + Q&A log from the webinar. Segment into hot/warm/cold based on questions asked. Draft three email variants for each segment with different CTAs: book demo, read doc, join community. Schedule sends for tomorrow morning.
For a backend engineer starting Monday, produce a reading order: services, critical paths, where configs live, and three 'good first issues' with context. Link to runbooks. Keep under two pages.
Cluster last quarter's NPS comments by theme. For each theme: frequency, example quotes (anonymized), and whether it maps to an existing roadmap item. Recommend one quick win we could ship in two weeks.
Collect open questions tagged #ask-leadership from the last two weeks. Group duplicates, prioritize by vote count if available, and build a 30-minute AMA agenda with timeboxes. Send the agenda Friday and add prep tasks for me.
Using the funder's PDF rubric and our impact metrics sheet, outline a 8-page grant: problem, approach, outcomes, budget narrative, and sustainability. Flag missing data I need to pull from finance.
Identify accounts with declining usage vs 90-day baseline and no CSM touch in 30 days. For the top five, draft a short outreach email that opens with a specific observation from their usage pattern, not a generic check-in.
We are sunsetting /v1/widgets in 180 days. Draft a migration guide outline, a customer email, and a changelog entry. Include code snippets for the new endpoint and a timeline graphic description for the blog.
From OKR progress and last month's KPI sheet, draft five talking points for Monday's all-hands: two wins, one challenge, one customer story, one ask. Keep language accessible to non-engineers. No acronyms on first use.
Write an 8-page memo on how regulated banks in the EU are adopting hosted AI for internal knowledge search. Sections: regulatory framing, vendor landscape, case studies with citations, and implications for our roadmap. Academic tone, footnote style references inline.
We are replacing our billing subsystem. Inputs: Jira epic list, architecture ADR, and vendor SOW PDF. Produce a phased plan (0-30, 31-90, 91+ days) with dependencies, rollback criteria, and a RACI. Highlight external dependencies in red.
Build a Monday morning briefing: macro indicators our board cares about (rates, sector index), our KPI deltas vs plan, competitor news from the last 7 days, and three questions I should anticipate in the board prep call. Max 2 pages.
From Mixpanel export and five recent sales call notes, map stages: awareness → trial → activation → expansion. For each stage: friction signals, content gaps, and one experiment idea. Output as Mermaid diagram description plus bullet analysis.
Given screenshots of the billing screen in FR and DE, list truncation issues, currency formatting problems, and strings that still read English. Prioritize by user impact. Create tickets with repro steps.
Reporter background + list of likely questions about our Series B. Draft answer frameworks: 3 sentences each, with bridge phrases back to our message on trust and hosted deployment. Include two 'no comment' pivots that still sound cooperative.
Parse my voice memo from the site visit: stakeholders, budget signals, technical blockers, and next step. Create CRM tasks for each stakeholder with due dates. If budget is mentioned, update the opportunity amount with source note.
Pull tickets that breached SLA last month by tier. Root-cause tag each: staffing, tooling, customer behavior, or unclear scope. Recommend two process changes with before/after metrics to track.
Model dilution for a 15M raise at two pre-money valuations using the latest cap table export. Show pro-rata participation for top three investors. Output a table and a paragraph for the board email.
After today's partial outage, author a new runbook: symptoms, dashboards to check, mitigation steps, escalation path, and comms templates for status page. Assume on-call may be junior; no unexplained acronyms.
Assemble an internal ethics review for the new 'auto-send email' feature: user consent flow, data retention, abuse scenarios, and kill switch. Format as sections matching our ethics committee template from last year.
Draft a 90-day joint plan with CloudCo: co-branded webinar, two blog swaps, shared case study outline, and lead routing SLAs. Include success metrics and owner column for us vs them.
Scan the diligence folder and build an index: folder path, doc type, freshness date, and whether it matches the checklist the bank sent. Flag duplicates and missing items with suggested owner to produce them.
Aggregate anonymized peer feedback for my direct report from the 360 forms. Themes: superpowers, growth areas, surprises. Suggest three development goals for the next quarter with measurable signals.
Crawl the public marketing site and list WCAG failures by page: missing alt text, contrast failures, keyboard traps. Sort by severity. Pair each with a rough fix estimate in hours.
Monthly investor update: traction, revenue vs plan, burn, hires, asks. Tone confident but candid. Include one customer quote and one risk we're watching. Under 400 words.
I have 40 sessions bookmarked at the conference and 12 booth meetings. Build a conflict-free schedule maximizing priority talks, 30-minute gaps for meals, and walking time between halls. Export to calendar with color coding by track.
Review our top 20 macros against recent tickets. Update wording for clarity, add branching for two new product areas, and retire three macros that no longer apply. Output diff-style before/after for each change.
Summarize the queue-sharding design doc for reviewers who didn't read the 40 pages: goals, non-goals, tradeoffs, failure modes, rollout plan. Add five sharp questions reviewers should ask in the meeting.
Rewrite the homepage hero for a calmer, more precise voice per our style guide. Remove hype adjectives, shorten sentences, keep value props. Provide A/B headline options with character counts.
Update the battlecard against Vendor X with their latest pricing blog, feature release notes, and G2 complaints. Sections: where we win, landmines to avoid, proof points, and a one-minute talk track.
From the warehouse export, compute gross margin by SKU for the top 20 SKUs. Flag SKUs where shipping cost erodes margin below 15%. Suggest bundle or price actions without sounding predatory in customer comms.
Draft a communication plan for merging two teams: timeline, FAQ, how reporting changes, and office hours. Anticipate five hard questions from ICs and draft answers. Keep tone humane and specific.
For the new public API, enumerate assets, trust boundaries, top 8 threats in STRIDE style, and mitigations already in place vs gaps. Two-page max for security office hours.
Propose a 12-week content calendar aligned to product releases on the roadmap sheet. Mix formats: blog, video script outline, customer story. Include SEO primary keyword per week.
Build a minute-by-minute runbook for Saturday's database cutover: pre-checks, execution order, validation queries, rollback trigger, and stakeholder comms. Assign roles from the on-call roster.
Define a simple health score using usage, support tickets, NPS, and payment timeliness from exports. Weight it, explain assumptions, and list accounts that moved from green to yellow this month with drivers.
Given our feature description, suggest 5 prior art search queries and summarize the closest public references you find. No legal conclusions—just a research memo for counsel.
Analyze last 200 new-user survey responses. Tag themes, quantify prevalence, and connect themes to specific product surfaces. Recommend three roadmap bets and one quick fix for onboarding copy.
Next week I need 6 hours of deep work for the board deck. Propose which meetings to decline or shorten, with suggested reschedule slots. Preserve customer calls and the exec staff meeting.
Translate the top 15 FAQs into Spanish and French with consistent terminology for our product names. Flag strings that need legal review in finance and privacy sections.
Turn the Now/Next/Later board into a customer-safe narrative for the quarterly webinar: themes, customer value, what's explicitly not shipping. Avoid internal codenames.
Build a simple model: price per donut, COGS, waste rate, labor hours per batch. Sensitivity table for ±10% foot traffic. Output assumptions clearly for my cofounder who is non-financial.
Draft moderation guidelines for our Discord: allowed topics, escalation path for harassment, template replies for common violations, and when to involve legal. Align tone with brand voice doc.
Summarize 12 papers on retrieval-augmented generation for enterprise search published 2023-2025. Matrix: method, dataset, reported latency, limitations. Conclude with what we'd prototype first.
From the ward notes export (de-identified), summarize active patients by acuity, pending labs, and discharge blockers for the night team. Highlight medication interactions mentioned twice or more.
Draft a clean offer email to the listing agent: price, contingencies, close timeline, earnest money, and inspection window. Tone professional, no emotional language. Include a checklist of attachments I need from my broker.
Rewrite my syllabus for clarity: learning outcomes, late policy, AI use policy, and grading breakdown. Reading level grade 10. Flag any contradictory dates between schedule and assignments table.
Write two 30-second host-read ads and one 60-second story arc for our product. Include mandatory disclaimers for the regulated claim in footnote form. Keep words speakable at normal pace.
Given today's pick list SKUs and bin map CSV, suggest an efficient pick path that minimizes backtracking. Output ordered bin sequence and estimated walk time using rough distances.
We're launching "Project Aurora" — unified inbox for support + sales — on March 18. I need one executable artifact the whole org can follow. Context you should assume you can pull from connected systems: the launch checklist doc, the comms calendar, the feature flag matrix, the support macro repo, and the status page config. Deliverables in this order: 1) Launch narrative (150 words max): customer-facing promise, what changes in-product, what does not change. 2) Rollout phases with gates: internal dogfood → 5% → 25% → 100%. For each phase: entry criteria, exit criteria, metrics to watch (give exact metric names if they exist in our analytics naming doc), rollback trigger, and owner. 3) Comms pack: three Slack posts (engineering, company-wide, customer-facing beta group), one customer email for GA, and one changelog entry. Match tone from last launch. 4) Support readiness: top 15 predicted questions with suggested answers and links to docs sections. Tag each P0/P1/P2 by expected volume. 5) Exec dashboard: 8 bullets I can paste into the exec Slack channel twice daily during rollout: what to look for, what is noise vs signal. 6) Post-launch retro prompt: 6 questions for the retro doc template. Constraints: no fake customer names; if a data source is missing, leave a bracketed TODO with the exact field you need from me.
We're evaluating a payments processor for EU + US. I uploaded their security pack, SOC2 PDF, architecture diagram PNG, and the MSA draft. Produce: A) Executive summary (10 bullets): strengths, weaknesses, deal-breakers, and open questions. B) Security & compliance table: control area | what they claim | evidence pointer | our residual risk | question for their CISO. C) Commercial model critique: pricing table reconstructed from the proposal, with scenarios at 50k, 250k, and 1M monthly volume including FX and chargeback fees if applicable. D) Integration plan: phases, engineering weeks estimate range, dependencies on our billing service team, and a cutover weekend checklist outline. E) Decision memo: recommend proceed / proceed with conditions / pause, with the single most important condition called out. Write for a CFO + CTO joint read. If something is ambiguous in the MSA, quote the clause and propose redline language.
We had a data exposure incident. Facts so far: limited to export logs for 48 hours, subset of customer emails, no passwords, root cause under investigation. Draft a timed comms sequence: - T+0 internal Slack to company (facts only, no speculation) - T+30m customer email for affected accounts (honest, calm, actionable: what we know, what we don't, what to do) - T+2h blog/status page update framework - T+24h follow-up email if root cause confirmed Include holding lines for execs if reporters ask, and a Q&A for support macros. Avoid legal overreach—mark anything that needs counsel review with [LEGAL].
Build this week's board metrics narrative from the spreadsheets in the board folder: revenue, NRR, gross margin, burn, runway, headcount, and pipeline coverage. Output: 1) Headline 3 bullets: what improved, what degraded, what stayed flat. 2) Variance table vs plan and vs prior month for each metric; flag anything beyond 10% variance with a one-line driver hypothesis. 3) Forward look 60 days: risks to plan and mitigations already in motion. 4) Questions the board will ask with suggested answers grounded in the data—include the uncomfortable ones (concentration, churn, competitive). Keep numbers consistent—if two sheets disagree, surface the discrepancy explicitly and say which source you treated as canonical.
Write a 6-page strategy memo arguing we should narrow the product to mid-market teams (50-500 employees) for the next 18 months. Use: last 4 quarters win/loss notes, churn reasons tagged in CRM, competitive intel notes, and the roadmap. Structure: - Thesis and non-goals - Evidence from data (quant + qual) - Implications for roadmap (what we stop, what we double down) - GTM implications (pricing, packaging, sales motion) - Risks of narrowing and how we monitor them - Decision: go / no-go with success metrics at 90 days Tone: crisp, opinionated, no buzzwords. End with a one-page exec summary upfront.
We want to open entities in Ireland and Australia in the next 9 months for engineering + support. From the people strategy doc and budget file, produce: 1) Hiring sequence by month and role cluster 2) Total cost estimate bands: recruiter fees, relocation, tooling, travel for onboarding 3) Policy checklist: PTO, benefits parity, equipment shipping, IP assignment nuances 4) Comms plan for existing employees so this doesn't feel secretive 5) A FAQ for candidates comparing us to remote-first competitors If local law topics appear, bracket [LOCAL COUNSEL] instead of guessing.
Prepare my QBR deck for Anchor Manufacturing using their CRM, support tickets, usage telemetry, and the last two QBR notes. Slides I want: 1) Executive summary tailored to their stated goals last quarter 2) Adoption: modules used, seats active, feature depth vs peers (anonymized benchmark if we have it) 3) Support themes: top issues, MTTR trend, any recurring product gaps 4) Value narrative: time saved estimates using conservative assumptions—show math 5) Roadmap alignment: what they asked for vs what's coming 6) Risks: renewal risk signals and mitigations we already started 7) Ask: concrete next steps with owners and dates Appendix: raw tables. Keep the main deck under 18 slides.
I need a replication plan for an internal ML experiment documented in the lab notebook repo. Deliver: - Hypothesis restated in falsifiable form - Data lineage: sources, filters, leakage checks - Metric definitions exactly as we should compute in production - Ablations we skipped and why that might matter - Statistical power note (rough is fine): what sample size we'd need to detect a 2% lift - Human evaluation protocol for subjective outputs - Go/no-go criteria for promoting to shadow mode If the notebook is inconsistent, list contradictions with file references.
Yesterday's outage: checkout errors spiked for 22 minutes. Logs in the incident folder, traces sample, and deploy timeline attached. Produce: 1) Narrative timeline with UTC timestamps and confidence level per event (confirmed vs inferred) 2) Blast radius: regions, payment methods, % of sessions affected 3) Five whys that stops at a process fix, not a person 4) Corrective actions: preventive > detective > responsive, each with owner and due date 5) Customer impact statement suitable for follow-up email 6) Load test gap: what scenario we should add to CI Be blunt about monitoring holes.
Review our pricing page copy and packaging against the spreadsheet of plans. Tasks: - Identify confusing overlaps between tiers (where buyers will stall) - Propose clearer naming if two features sound like duplicates - Suggest anchoring: which tier should feel like the 'obvious' choice for our ICP - Rewrite the hero line and three bullets under each tier for scannability - Add an FAQ that preempts the top 8 pricing objections we saw in sales notes Keep everything honest—no fake discounts.
Plan a 10-city tour for enterprise prospects: 2-hour workshop + dinner. Constraints in the brief: budget cap, minimum 12 attendees per city, avoid holiday weeks, prefer Tue-Thu. Deliver: - City sequence that minimizes brutal travel (start/end at HQ coordinates) - Per-city runbook: venue requirements, AV, staffing roles, invite copy, reminder cadence - Lead capture and follow-up SLA within 24h - Success metrics: pipeline created, meeting conversion, content assets captured - Risk list: low registration, speaker illness, last-minute venue issues—mitigations Output as a project plan Gantt description + checklist.
Update the annual compliance training deck for a remote-first SaaS: data handling, insider risk, harassment, and AI usage. For each module: - learning objectives - 6 quiz questions with explanations for wrong answers - scenario dialogues that feel realistic for Slack-era work - attestation language Map each section to controls referenced in our SOC2 policies folder. Flag anything that conflicts with the employee handbook.
Our primary widget supplier in Region A just announced a 6-week delay. Using inventory on hand, open orders, and production schedule files, produce: - Shortage forecast by SKU week-by-week - Customer prioritization framework (strategic accounts, SLAs, penalties) - Mitigation options: alternate suppliers, partial shipments, substitute SKUs with customer messaging - Internal comms: sales vs support talking points (aligned, not contradictory) - Daily standup agenda for the war room for the next 14 days Assume we cannot share the supplier name externally.
I need to protect 90 minutes daily for deep work for the next month, but I cannot move: standing 1:1s, board prep blocks, or customer calls already on the calendar. Analyze my calendar patterns for the last 6 weeks: recurring meetings that could rotate time, meetings that could be email, and meetings with low attendance rates. Propose: - A concrete reschedule proposal message for each recurring meeting owner (polite, specific alternatives) - A 'focus block' proposal with auto-declined conflicting invites during those windows - A public team norm note I can post explaining why I'm doing this If you need my priority list of projects, ask one clarifying question only.
We closed a small acquisition. Employee roster, product overlap map, and customer overlap CSV are in the folder. Build a 30-60-90 integration plan: - People: reporting, titles, benefits harmonization milestones, retention bonuses risks - Product: what to merge vs sunset vs keep dual until parity - Customers: communication waves, migration risks, support staffing - Systems: SSO, billing, analytics alignment - Culture: rituals to merge without crushing their identity Include a RACI and a weekly exec checkpoint agenda for 12 weeks.
Draft the methodology section for an NIH-style grant: cluster-randomized trial of a digital intervention in primary care. Include: population, inclusion/exclusion, power calculation narrative, primary endpoint, secondary endpoints, analysis plan (ITT vs per-protocol), missing data handling, ethics/IRB considerations placeholder, and limitations. Cite placeholder references as [REF] where you want me to insert real citations later. Keep language precise—reviewers will nitpick.
Prepare App Store and Play Store submission assets from the build notes and screenshots folder. Deliver: - Release notes (customer-facing) for version 2.8.0 - Keyword list and rationale - Responses to likely review questions about account deletion and data export - Privacy nutrition label mapping from our privacy policy sections - A test account recipe for reviewers with seeded data Flag any screenshot that still shows internal codenames.
From LinkedIn export + CRM contacts + last year's conference attendee list, build a map of relationships to TargetCorp: who knows whom, strength of relationship if inferable from email frequency, and warm intro paths to two specific buyers. Output: - Path graph described in text (nodes and edges) - Suggested intro request messages tailored to each intermediary (short, respectful, specific ask) - A 15-minute prep brief for my first call with the economic buyer once introduced Redact personal emails in any example excerpts.
Design next month's DR drill scenario: primary region unavailable, partial data corruption in object storage, and elevated error rates on auth. Deliver: - Drill objectives and non-goals - Preconditions checklist - Script for the facilitator minute-by-minute for 90 minutes - Expected observer notes template - Success criteria and failure criteria - Retro agenda and output artifacts Assume participants have not done a DR drill before.
Help me assemble a small business permit application for a retail storefront: fire, health, signage, and zoning. From the municipal PDFs in the folder, produce: - A consolidated checklist with deadlines - A cover letter draft addressed to the clerk - A site plan narrative based on the measurements doc - A list of questions to ask the landlord before signing the LOI If forms conflict, tell me exactly which page contradicts which.
Draft a plain-language letter to study participants about a protocol amendment: extra blood draw at week 8, optional wearable device, unchanged risk profile per sponsor. Tone: respectful, transparent, no coercive language. Include a short FAQ and a single paragraph for caregivers. Provide a version at 6th grade reading level and note any terms that may still need translation support.
Convert the shooting script PDF into a one-day stripboard: scene order, location clusters, estimated setup times, golden hour constraints, and meal break compliance with union rules summary from the notes doc. Highlight continuity risks (wardrobe, props) called out in script notes.
Summarize the last 48 hours of mission logs for the lunar rover: commands sent, anomalies, power state, bandwidth usage, and science objectives completed vs planned. Output for the public blog in accessible language, plus a technical addendum for partners.
Using POS export for 90 days, compute contribution margin by menu item, popularity, and correlation with add-on sales. Recommend which items to feature, rename, bundle, or retire. Consider kitchen capacity notes from the chef's doc.
Build a weekend away-game pack: flight options with minimal jet lag for athletes, hotel block requirements (late checkout, nutrition), local hospital contacts, emergency roles, and a media schedule aligned to the league's rules PDF.
From the cue sheet and composer agreements folder, build a clearance tracker: track, rights holder, territory, term, fee, credit line, and any sync restrictions for paid ads vs organic. Flag gaps where a signature is missing.
Connect the apps you need from Integrations, then open the assistant from the app. For setup detail, see Assistant in the docs.