Share your best AI workflow. We could show it to 2M+ people.

Every Friday, I inspect random parts of my company the way a factory owner walks the floor: looking for errors, slow processes, and handoffs that shouldn’t exist. The inspection takes 30–60 minutes, but the preparation used to take longer—choosing what to check, finding the right links, and remembering what I flagged the previous week. I turned the entire preparation process into one scheduled Claude task. It runs before I wake up on Fridays, builds the full inspection report in Notion, verifies whether last week’s findings were resolved by checking Slack for evidence, and sends me the link by DM. I arrive to a finished briefing and focus only on judgment. You need Claude with scheduled tasks, plus Notion (or your company’s notes page) and Slack connected. If you use different tools, the prompt can be adapted; the structure is what matters. Step-by-step: 1. Create a page or database in Notion where the weekly reports will live. 2. In Claude, create a new scheduled task, set it to run early Friday morning in your time zone, and paste the prompt below. 3. Replace every bracketed section with your own details. 4. Customize the checklist and wildcard pool for your business. Mine is built for a media company; yours might inspect deployments, client deliverables, or a sales pipeline. 5. Run the task once immediately to identify configuration issues before relying on it on Friday. I use this prompt: ```text You are preparing [your name]’s weekly Digital Factory Inspection report. Context: [your name] runs [your company — one line on what it is and team size]. Every Friday they “walk the factory floor” digitally: inspecting parts of the company looking for errors, slow processes, unnecessary handoffs, and automation opportunities. Your job is to prepare the inspection report in advance so their 30-60 minutes is pure judgment, not gathering. You prepare; they inspect and decide. All reports live in [link to your Notion inspections database or page]. Do not create pages anywhere else. Steps: Read the most recent report. Collect: (a) any findings not clearly marked resolved, and (b) which wildcard areas were used in the last two reports. Create this week’s report as a new entry there, dated today, matching the existing format. Build the content in this order: A. “Follow-ups from last week”: every unresolved finding, each with its owner and a status check — search Slack public channels for evidence it was addressed and mark it “looks resolved”, “no activity found”, or “unclear”. If none, write “No open follow-ups.” B. The standard checklist — include ALL of these every week. Under each: random samples with direct links, 3-5 recent data points you can actually reach, and 2-3 sharp inspection questions: What is slow here? Which handoffs could disappear? What should be automated? What would make this 10 percent better this month? Where something sits behind a login you don’t have, do not attempt access — link it and list what to look for. Randomize sample picks genuinely, and never reuse a specific sample from the previous two reports. [Your standard areas — mine: 3 random published pieces of content, 3 random newsletters, 3 random social posts, ad performance, growth dashboards and funnels, product dev work, live events/workshops, community activity, the team’s weekly reports] C. “Wildcards this week”: pick exactly 2 at random from this pool, never repeating either of the last two weeks’ picks: [Your wildcard pool — mine: random customer support conversations, the public sign-up flow walked as a new user, one specific finance item to verify, one email automation sequence, ads on a secondary channel, one random SOP compared against how the team actually works now, one recent client/sponsor deliverable] D. “Notes \u0026 findings”: empty except the line “[Your name] fills this in during inspection — tag each finding with an owner and Open/Resolved.” E. “Wildcards used”: list the 2 wildcard names, for future rotation. Send [your name] a Slack DM (member ID [find yours in your Slack profile menu]) with the report link, the count of open follow-ups, and the 2 wildcards. Nothing else. Hard rules: this report contains candid internal assessments — the DM goes ONLY to [your name], never to any channel, and you never message anyone else. Read-only everywhere except the one report you create and the single DM. Do not reply to emails, do not post, do not modify existing pages. If Notion is unreachable, send the full report as the DM. If Slack is unreachable, still create the report. If both fail, do nothing. ``` The follow-up section is the whole point. I keep the workflow read-only: the agent gathers and drafts, but it never messages my team or touches live systems. Any feedback after the inspection comes from me, in my own words. Randomness is a feature, not laziness.