LinkedIn Content Planner (linkedin-content-planner)

The linkedin-content-planner skill creates a balanced, conversion-focused 7-day LinkedIn editorial schedule. Built specifically for founders, technical leaders, and growth operators, it eliminates random posting by mapping specific daily themes, content formats, hook formulas (H1-H20), optimal time slots, and strategic outbound comment targets.

When to use this skill

Ideal Use Cases:

• Planning a coherent weekly content roadmap aligned with company milestones, product launches, or hiring pushes.
• Ensuring a healthy balance between technical deep dives, founder vulnerability, tactical playbooks, and contrarian perspectives.
• Systematizing daily outbound engagement so you comment on prospect profiles before releasing your own daily post.
• Transitioning from sporadic, reactive posting to a predictable audience acquisition engine.
• Managing multiple executive profiles across a founding team without topic cannibalization.

Disambiguation ('Not for X, use Y'):

• Not for writing the individual post copy itself -> use linkedin-post-writer.
• Not for drafting the comments for your target profiles -> use linkedin-comment-drafter.
• Not for repurposing a single podcast or blog -> use linkedin-repurposer.
• Not for interviewing the founder for stories -> use linkedin-interviewer.
• Not for reviewing post engagement analytics -> use linkedin-engager-analytics.

The 7-Day Founder Mode Content Architecture

A founder’s audience gets fatigued by unvarying self-promotion or non-stop personal vulnerability. The 7-day architecture balances four key pillars:

1. Pillar 1: Domain Authority (35%) — Technical breakdowns, architecture decisions, industry data.
2. Pillar 2: Founder Scars (25%) — Honest post-mortems, cash burn management, hiring mistakes.
3. Pillar 3: Tactical Playbooks (25%) — Actionable frameworks, curated toolsets, how-to workflows.
4. Pillar 4: Contrarian Philosophy (15%) — Debunking industry dogma, anti-consensus bets.

Day-by-Day Cadence Overview:

Algorithmic Timing & Cannibalization Prevention

To maximize distribution on LinkedIn, posting schedules must obey algorithmic timing rules:

1. The 18-to-24 Hour Cooldown Rule:
   • Posting twice within 12 hours causes LinkedIn’s algorithm to throttle reach on the earlier post to make room for the new one.
   • Maintain a minimum of 18 hours between standalone posts.
2. Geographic Distribution Windows:
   • US Tech / B2B: 07:45 AM – 08:45 AM EST (Catches East Coast morning commuters and West Coast early risers simultaneously).
   • European Audiences: 08:00 AM – 09:00 AM GMT / CET.
   • Weekend Engagement: 09:00 AM – 10:30 AM local time. Saturday posts achieve lower raw impression counts but yield 2x higher long-form read completion rates.

The 5-3-1 Outbound Commenting Strategy

Posting in a vacuum suppresses algorithmic reach. The planner schedules a 15-minute daily "Warm-Up" ritual immediately before your post goes live:

• 5 Comments on Peer Creators: Establish visibility in active comment sections and trigger reciprocal visits.
• 3 Comments on Target Prospect / ICP Profiles: Provide additive value on posts by ideal buyers to build familiarity.
• 1 Comment on an Industry Influencer: Engage with a high-traffic post to drive secondary profile traffic from thousands of viewers.

How It Works Step-by-Step

When executing linkedin-content-planner, the workflow progresses through 5 phases:

1. Strategic Discovery:
   • Ingest the user's primary business goal for the week (e.g. Developer beta signups, enterprise demo bookings, recruiting senior talent).
   • Review available material in references/story-bank.md to identify unused founder stories and recent metrics.
2. Calendar Slotting:
   • Assign topics to the 7 calendar days following the 4-pillar distribution.
   • Match each day with its ideal hook formula from references/hook-formulas.md.
3. Outbound Target Mapping:
   • Generate specific criteria or profile targets for the 5-3-1 outbound commenting sessions.
   • Align the outbound topics with the themes of your own upcoming posts.
4. Production Schedule & Asset Specs:
   • Specify required assets for each post (e.g. architecture diagram, screenshot, first-comment link destination).
   • Ensure external links are tagged for comment #1 placement.
5. Approval Staging & Export:
   • Present the comprehensive 7-day plan in structured markdown.
   • Stage the scheduled items into the automation calendar once approved.

Pre-Publication Weekly Audit Checklist

Before finalizing any 7-day schedule, verify:

• Are all 4 content pillars represented across the week?
• Is there at least an 18-hour gap between every scheduled post?
• Does every single post have an assigned hook formula (H1–H20)?
• Are all outbound links relegated to Comment #1?
• Is there an allocated 15-minute outbound commenting block before each publishing window?

Approval Gate

Before locking in the weekly editorial calendar or scheduling posts, the user must approve the plan:

[CONTENT PLAN APPROVAL GATE]
Plan Scope: 7-Day Editorial Roadmap (Week of Nov 3 - Nov 9)
Pillars Balanced:
- Domain Authority: 2 posts (Monday, Thursday)
- Founder Scars: 2 posts (Tuesday, Saturday)
- Tactical Playbook: 1 post (Wednesday)
- Contrarian: 1 post (Friday)
- Retrospective: 1 post (Sunday)

Total Outbound Targets: 35 strategic comment opportunities scheduled

Approval Token: e49081bb-3112-4aa8-9f20-998877661122
Status: PENDING REVIEW.
Type 'APPROVE e49081bb-3112-4aa8-9f20-998877661122' to confirm schedule.

Examples

Example Prompt: Seed-Stage AI Infrastructure Startup

User Prompt: "Build a 7-day content plan for our seed-stage developer tooling startup. We want to show our engineering chops, talk about surviving on a small budget, and drive developers to our open-source repo."

### 7-Day Founder Content Plan

#### Monday — Domain Authority & Macro Thesis
- **Topic:** Why vector search without metadata filtering causes silent model hallucination.
- **Format:** Technical text teardown with query benchmark comparisons.
- **Hook (H10 Data-Reveal):** "We tested 120,000 RAG queries across 4 production vector databases. 64% of retrieval errors weren't embedding drift—they were missing metadata filters."
- **Posting Window:** 07:45 AM local time.
- **Comment Targets:** 5 engineers discussing RAG pipelines on LinkedIn; 3 VP Eng prospects.
- **First Comment Asset:** Link to open-source GitHub benchmark repository.

#### Tuesday — Founder Scars & Post-Mortem
- **Topic:** Spending $45k on AWS credits before realizing our staging cluster was left running 24/7.
- **Format:** Narrative founder confession with cost-reduction checklist.
- **Hook (H11 Confession):** "I made a $45,000 infrastructure mistake last quarter. Nobody warned us about unmetered cross-AZ data egress fees."
- **Posting Window:** 08:15 AM local time.
- **Comment Targets:** 5 startup founders discussing cloud cost management.

#### Wednesday — Tactical Playbook
- **Topic:** The 4-step checklist for building deterministic AI background workers.
- **Format:** Structured bulleted playbook.
- **Hook (H13 Tactical Listicle):** "4 architectural rules that kept our automated background agents at 99.9% task completion without human intervention:"
- **Posting Window:** 07:30 AM local time.
- **Comment Targets:** 5 AI product managers and tech leads.

#### Thursday — Behind-the-Scenes Architecture
- **Topic:** How we decoupled our job queue using SQLite and Redis instead of complex message brokers.
- **Format:** System breakdown with ASCII flow diagram.
- **Hook (H18 Behind-the-Curtain):** "Most teams immediately deploy Kafka or RabbitMQ for job queuing. Here is why our entire platform runs on SQLite and in-memory Redis:"
- **Posting Window:** 08:30 AM local time.
- **Comment Targets:** 5 backend infrastructure creators.

#### Friday — Contrarian Take
- **Topic:** Why hiring prompt engineers is a waste of capital for early-stage teams.
- **Format:** Debate opener with empirical software engineering reasoning.
- **Hook (H15 Counter-Narrative):** "'Every startup needs a Chief Prompt Officer' is the silliest hiring trend of 2026. Here is why software engineers with solid unit tests write 10x better prompt logic:"
- **Posting Window:** 08:45 AM local time.
- **Comment Targets:** 5 trending AI influencer posts.

#### Saturday — Culture & Reflection
- **Topic:** Why we enforce mandatory 'No Slack After 6 PM' for our 6-person remote engineering team.
- **Format:** Personal narrative on async productivity.
- **Hook (H1 Anaphora):** "We don't expect replies on Saturday. We don't expect replies after 6 PM. We don't expect replies during lunch. Here is why our shipping velocity tripled:"
- **Posting Window:** 09:15 AM local time.
- **Comment Targets:** 3 remote work advocates.

#### Sunday — Retrospective & Engagement Bomb
- **Topic:** The hardest engineering problem your team solved this month.
- **Format:** Short reflection closing with a diagnostic question.
- **Hook (H9 Question-Bomb):** "What is the single most expensive bug your engineering team pushed to production this year—and what did it teach you?"
- **Posting Window:** 10:00 AM local time.
- **Comment Targets:** Active commenters from your Wednesday and Thursday posts.