timscheuerai/linkedin-funnel/content-strategy

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.

Define content strategy

Read AGENTS.md, index.md, identity/positioning.md, identity/proof.md, audience/ideal-follower.md, strategy/goals.md, strategy/pillars.md and strategy/funnel.md. Read the three stage pages when mapping the funnel.

Establish the job

Identify the intended reader, the problem the author can credibly address, the public material they can draw on and the next step they can actually offer. Distinguish an audience that spreads content from a qualified buyer. A missing offer can remain unresolved while educational content is planned.

Build the taxonomy

Propose or refine pillars around recurring reader needs and the author's experience. Each pillar needs a promise and a boundary; split overlapping pillars or explain the overlap. Topics are recurring questions within a pillar. Subtopics are specific angles supported by source material.

The empty scaffold offers four pillars, four topics each and four subtopics per topic. Use that as a starting point, not a requirement to manufacture 64 ideas. Mark suggested names as proposals until the user adopts them. Preserve an existing taxonomy unless revision is requested.

Connect content to conversion

For each topic, define its likely job:

• Top: make the right reader recognize a problem or perspective.
• Middle: explain a method, tradeoff or piece of evidence that earns trust.
• Bottom: make a relevant offer and a clear next step.

Specify inbound routes such as a direct reply, registration, signup or requested resource. If signal-based outbound is part of the brief, specify the signal source, buyer-fit check, exclusions, routing and intended conversation. A reaction is evidence of engagement, not consent or buying intent. Separate qualification from messaging and leave provider selection to the actual setup.

Define the events to measure and the attribution limits. Do not turn reach into claimed revenue. Write unverified targets as targets, not results.

File and apply

Update strategy pages with rationale and sources. For an authorized Notion taxonomy setup, follow strategy/notion-schema.md, use the configured data sources and page-body templates, and keep pillar option names synchronized between the two databases. Query before creating rows.

Return the proposed or adopted taxonomy, funnel paths and unresolved decisions. Planning outbound does not run enrichment or send messages.