06-reference

every chatgpt manage my workweek

Sun May 03 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·reference ·source: Every - Working Overtime ·by Katie Parrott
ai-project-manageragent-native-pmokrsnotionchatgpt-agentspersonal-ops

“I Let ChatGPT Manage My Workweek” - @KatieParrott

Why this is in the vault

First-person, single-operator account of building a personal AI project manager on top of ChatGPT + Notion + Google Calendar + Slack + Drive - with the actual setup recipe, prompt skeleton, weekly cadence, and a candid failure-mode list. This is the personal-scale mirror of 2026-04-09-every-four-ai-agents (Every’s company-scale Anton/Max/Strategy/Reporter stack) and the personal-scale mirror of RDCO’s own COO-agent setup. The interesting content isn’t the “AI can manage your work” claim - it’s the specific dependencies that make it work or break (database freshness, OKR document quality, single-task prompt discipline) and the explicit admission of what AI cannot fix (the operator’s own avoidance behavior). Source-fidelity caveat: Every’s email body did not render via Gmail (known empty plaintextBody gotcha); reconstructed from canonical URL via WebFetch.

Sponsorship

Mixed. Third-party paid: Intent (Augment Code), a spec-driven development platform with agents - standard Every paid placement, properly disclosed. Self-cross-promo (Every-internal products mentioned in editorial): Proof (Every’s editor, used here as the OKR document store), Plus One / Margot (Every’s personal-agent product, presented as alternative to ChatGPT for the same workflow), and Every Consulting (linked CTA). Per the sender-pattern note in the README, treat Every-internal product mentions as cross-promo regardless of disclosure framing - the editorial recommendation surface is not neutral when the alternative being recommended is owned by the publication.

The core argument

Parrott - 15 years a writer, self-described “garbage at project management” - built a ChatGPT-based agent to translate quarterly OKRs into a weekly operating rhythm. The setup is mechanical and reproducible:

Inputs the agent reads as context.

Tools the agent connects to.

Behavior contract (the load-bearing prompt rules).

The cadence.

Concrete decomposition example. “Stand up a reliable Vibe Check pipeline” became: Audit existing process - Draft process brief - Solicit feedback - Implement changes. The agent’s actual work was breaking quarterly chunks into weekly-sized actions with deadlines.

What worked, what broke

Worked:

Broke or limited:

Punchy framing she uses: deadlines used to feel like “weather systems: suddenly overhead, occasionally catastrophic, mostly outside my control.” The agent moves them onto the calendar. It does not move them out of your head.

Mapping against Ray Data Co

Strong mapping. This is the personal-scale recipe for the exact pattern RDCO is operating at COO scale - and the failure modes she names are the same ones we’ve already mitigated structurally.

  1. Architecture parity. Parrott’s stack (OKR doc + Notion board + Calendar + Slack/Drive, with prompt rules pinning sources of truth) is structurally identical to RDCO’s vault + Notion task board + Calendar + Discord/iMessage stack. The harness pattern is convergent: a few shared databases as the substrate, an agent that reads them and produces priority + status, the operator providing judgment. This is the second independent confirmation in 30 days that the pattern is industry-default - the first being 2026-04-09-every-four-ai-agents at company scale and 2026-05-03-every-context-window-codex-goes-to-work (Moretti’s ce:strategy + ce:product-pulse two-skill loop). Three convergent data points = the harness/skills pattern is the playbook, not a thesis.

  2. The Monday plan / Friday status cadence is the gap RDCO does not cleanly cover. We have /morning-prep (daily, calendar-aware) and /check-board (on-demand, task-oriented). We do not have a structured weekly Monday-plan + Friday-status loop. The closest is the autonomous loop’s idle-cycle behavior. Decision surface: worth considering a /weekly-plan (Monday) + /weekly-status (Friday) skill pair, scheduled via cron, that produces the one-page plan and the slipped-vs-shipped report Parrott describes. Low-risk to prototype; the inputs already exist (Notion task board has Critical Component checkbox per project_critical_component_field.md, vault has SOUL.md / project READMEs as the OKR analog). Verdict: queue this as a Notion task for /check-board to pick up - do not block on founder approval, it’s reversible additive skill work.

  3. Database-freshness failure mode is already mitigated for RDCO and we should keep that lead. Parrott’s biggest failure was Notion staleness because she had to dual-write (do the work, then update Notion). RDCO avoids this because most Ray-owned status writes go through the agent - /check-board updates Notion as it works, vault notes are written by skills, not transcribed by hand. Implication: the personal-PM pattern Parrott describes will degrade for any operator who has to dual-write. RDCO’s “agent owns the writes” architecture is the durable advantage. Worth surfacing in any future Sanity Check piece on “why personal AI PMs break.”

  4. The “me problem” is the unhobbling ceiling. Parrott names what’s actually irreducible: avoidance, self-doubt, choosing which idea to believe in. The agent can flag, remind, decompose - it cannot will. This connects to the founder’s feedback_calibrate_overconfidence.md (Ray defaults to overconfident from polished docs; founder’s lived reality is the ground truth). Same shape: the agent’s job is to reduce friction on execution, not to substitute for judgment. The harness is the floor, not the ceiling.

  5. Prompt rules are stealable. The behavior contract she wrote - “don’t invent statuses, ask one clarifying question, flag non-OKR requests, protect stated priorities from daily impulses” - is well-formed and worth lifting verbatim into a future RDCO prompt-pattern reference. Especially the “ask one clarifying question rather than guessing” rule, which RDCO already practices but doesn’t have written down as an explicit pattern.

  6. L5 north-star check. Per project_l5_north_star_strategic_direction.md, RDCO’s front-burner work is unhobbling the COO agent (toolset + visibility). A Monday-plan + Friday-status skill pair, the database-freshness lead, and the lifted prompt rules all reinforce the front-burner thesis. None of this pulls toward operating small bets - it deepens the harness.

Decision surface (founder review): None requiring immediate judgment. The /weekly-plan + /weekly-status skill pair is a reversible additive build - queue to Notion, let the autonomous loop pick it up.

Tracked-author candidates

Copy-paste caution

Body reconstructed from canonical URL via WebFetch (Every’s email body did not render). All quoted phrases are ≤15 words and attributed. Source-fidelity caveat surfaced in frontmatter and in “Why this is in the vault.” Original at every.to.