A self-analysis + operating system built from a full sweep of past work activity (email, calendar, Notion, Drive, social planner, Meta ads, GitHub, OpenArt, Canva) as of 2026-07-11.
Privacy note: this repository is currently public. Everything committed here is deliberately sanitized (no names, case numbers, medical or financial details). Before filling in real contact addresses or personal specifics in
state/ortemplates/, make this repo private.
| File | Purpose |
|---|---|
ANALYSIS.md |
What the data shows: work patterns, biggest time sinks, blind spots |
OPERATING-SYSTEM.md |
The designed weekly workflow that fixes them |
.claude/skills/ |
Claude Code skills you can run in any session opened on this repo |
state/ |
Machine-readable state the skills read/write (cooldowns, open loops, scorecards) |
templates/emails/ |
Reusable templates for your recurring emails |
Open a Claude session on this repo and type the slash command:
| Command | What it does | When |
|---|---|---|
/weekly-review |
Pulls failed posts, ad spend, calendar holes, open loops → writes a scorecard, picks 3 priorities, enforces the finish-first rule | Sunday, 30 min |
/content-week |
Generates + schedules a full week of content through PLZ Social Planner, honoring cooldown ledgers, and verifies media is attached before calling it done | Thursday (your existing "Next week content" slot) |
/follow-up |
Checks every open loop (paperwork, suppliers, support tickets) for replies and drafts the next chaser automatically | Monday + Thursday, 10 min |
/funnel-audit |
Walks the money path end-to-end (content → capture → email → offer) and reports the first broken link | Monthly, or after any funnel change |
/recurring-emails |
Drafts your templated recurring emails from templates/emails/ with verified recipients — no more typo bounces |
As needed |
The analysis found that the constraint on scaling is not strategy, tooling, or content quality — those are all strong. The constraint is:
- No closing loop — systems get built, never finished or reviewed
- Manual repetition — the same emails, prompts, and ledgers redone by hand weekly
- Chasing overhead — every external dependency needs 2–4 manual reminders
- Zero feedback — no metrics ever collected, so effort can't compound
- Builder's trap — building new tools instead of shipping with existing ones
Each skill attacks exactly one of these. Details in ANALYSIS.md.