Weekly Content Brief

If the pain bank exists, it contains real pain signals harvested from Reddit, classified by TAYA Big 5 categories (Cost/Price, Problems/Negatives, Versus/Comparisons, Reviews, Best-of Lists). Each entry has a recurrence count — higher recurrence means more people independently expressed the same pain. Prioritize entries with recurrence >= 2 as angle candidates. Aim for Big 5 category diversity across the 3 angles (not all from the same category).

Read the content flywheel to avoid duplicating already-posted seeds: ~/Documents/DT Vault/1-projects/content-flywheel.md

List ~/Documents/DT Vault/1-projects/tiktok/briefs/ to see angles from the last 3 briefs. Don't repeat an angle already suggested recently.

Step 3: Generate 3 Ranked Video Angles

Load references/voice-rules.md before writing any hooks or talking points.

The Audience

Mid-level engineers (dev or ops background) trying to break into DevOps/SRE roles. They see tools on job postings and want to understand them well enough for interviews and on the job. They're motivated by career progression — getting hired, getting promoted, getting paid more. They don't need to be talked down to. They need the mental model that connects what they know to what they don't.

Content Pillars (start here, not from git activity)

1. Mental models over tool memorization — knowing WHY beats knowing HOW
2. Building an online presence that attracts jobs to you
3. Grace and kindness on the learning journey — the world is hard enough

How to Use Git Activity

Git activity is EVIDENCE, not the angle. The angle comes from the audience's pain point.

BAD: "I rewrote 7 community posts" (work report — audience doesn't care about your workflow) GOOD: "You're reading docs for tools you'll never use on the job" (audience pain → your rewrite is the proof)

BAD: "My homelab broke at 2 AM" (cool story about you) GOOD: "What happens when prod goes down and you're 8,000 miles away?" (career fear → your homelab story is the illustration)

For each angle, ask: "What is the viewer getting from this?" If the answer is "insight into Darrell's week," rewrite it. If the answer is "a mental model, career strategy, or emotional permission they needed," ship it.

How to Use Pain Bank Signals

Pain signals are the audience's actual words — use them to find the angle, then connect to git activity for evidence.

The pain bank entry's raw quotes are hook material. The recurrence count tells you how widespread the pain is. The Big 5 category tells you what type of content to make.

BAD: Pick a pain signal and give generic advice (that's what every other creator does) GOOD: Pick a pain signal, find where your git activity THIS WEEK proves you have a real answer, and build the angle from that intersection

If a high-recurrence pain signal doesn't connect to this week's git activity, save it — it'll connect eventually. Don't force it.

Ranking Priority

1. Audience value — does this help someone get hired, get promoted, or stop beating themselves up?
2. Dual audience — lands for devs AND ops people (never assume which side)
3. Flywheel alignment — drives Skool signups or consulting credibility
4. Recency — git activity from this week makes it feel genuine, not manufactured

Angle Structure

Angle [N]: [Audience-facing punchline — max 8 words]

Hook: [First 1-2 sentences on camera. Starts with THEIR pain, fear, or question — not your activity. Mid-story or direct question. Creates "wait, what?" reaction.]

Talk about:

• [The audience problem or misconception this addresses]
• [Your specific experience/story as proof — this is where git activity shows up]
• [The takeaway they can apply to their own career]

Evidence: [Which git activity or real work makes this authentic this week]

Flywheel: [Skool signup / consulting credibility / community discussion]

Step 4: Add Raw Material Footer

After the 3 angles, append:

This Week's Raw Material

• [one bullet per repo/item with activity - anonymize client names]

Audit trail so Darrell can see what fed the brief.

Step 5: Write Output File

Create directory if missing: mkdir -p ~/Documents/DT\ Vault/1-projects/tiktok/briefs/

Write to: ~/Documents/DT Vault/1-projects/tiktok/briefs/YYYY-MM-DD.md Use today's date for filename. See examples/sample-brief.md for full file format.

Step 6: LLM Wiki Ingest

After writing the brief, run the ingest workflow:

1. Fan out cross-references: Run qmd search "main angle topics" --json -n 5 to find related vault pages. Add [[briefs/YYYY-MM-DD]] backlinks to the 2-3 most relevant pages (e.g., related client work, field guides, origin stories).
2. Append to log.md: Add an entry to ~/Documents/DT Vault/log.md: ## [YYYY-MM-DD] ingest | Content Brief — <top angle one-liner>
3. Re-index: Run qmd update && qmd embed to update the search index.

Step 7: Confirm

Print to stdout: Brief written to ~/Documents/DT Vault/1-projects/tiktok/briefs/YYYY-MM-DD.md Angles: 1. [one-liner] 2. [one-liner] 3. [one-liner]

Scheduler Note

No interactive prompts. Runs autonomously. Cron: 0 19 * * 0 (Sundays 7pm) Register: "Schedule weekly-content-brief every Sunday at 7pm, read-only execution."