timscheuerai/linkedin-funnel/week-posts

Workspace: all context paths below (identity, audience, strategy, voice, brand, raw, output, index, log, workspace preferences and context scripts) resolve from context/ in the kit root. Read both the root AGENTS.md and context/AGENTS.md. Skill-local references/ and flowchart scripts/ resolve from this skill directory.

Plan the week

Read AGENTS.md, index.md, the relevant identity and audience pages, identity/proof.md, strategy/goals.md, strategy/pillars.md, strategy/funnel.md and voice/linkedin-voice.md. Read local preferences if present. When the context also holds the author's verbatim words, a story bank or a page on what performs on their account, read those too; personal stories come only from material marked public or approved by the author.

Choose the dates and material

Use the requested dates, time zone, platform and cadence. Do not inherit a particular founder's weekdays or a fixed four-post schedule. If the user wants a dated plan and the time zone or cadence is unknown, ask for those choices together. An undated draft batch can proceed without them.

Read the configured Notion taxonomy, topic page-body subtopics, recent published content and future cards when available. Otherwise use the local strategy and supplied history. Do not claim recent topics are unused when history is inaccessible.

Select distinct source-backed angles and an appropriate pillar mix. One per pillar is a useful option, not a mandate. Avoid repeating a recent idea unless the new post has a clear new contribution. Pick one pillar, topic, subtopic and funnel job for each piece. Do not silently create a new taxonomy to fill a slot.

If key material is missing, complete the supported part of the plan and identify the source needed for the rest. Do not fabricate posts to hit a count.

Draft and save

Use the local linkedin-copywriter skill for LinkedIn pieces. Other platforms use the configured format and voice rules. Keep proof and conversion targets grounded.

A request to draft a week into the board authorizes creating draft cards in the configured board. Follow strategy/notion-schema.md; query existing dates and titles first. Use Status = Creating, one Pillar value, Platform, planned Publish date and one paste-ready text code block in each card. After an ambiguous result, query before retrying.

Without Notion, return the plan and drafts in chat. Do not start a local posts database or pretend cards were saved.

Report date, pillar, topic, funnel job and card link where created. State which content is still waiting on input. Log the run without duplicating post copy. A planned date is not a scheduled publishing action.