content-strategy

name	content-strategy
description	ZackAI project wrapper for content-strategy. Use it to plan content and content systems, but always map recommendations onto the current ZackAI markdown tree before suggesting new assets.
metadata	{"version":"1.1.0-zackai.1","basedOn":"global/content-strategy@1.1.0"}

content-strategy — ZackAI Wrapper

This project-level skill keeps the original content-strategy purpose, but adds ZackAI-specific reuse-first behavior.

Core Goal

Plan content that is searchable, shareable, and useful, while explicitly mapping ideas onto ZackAI’s existing docs before proposing new content tracks or parallel planning artifacts.

Required Read-First Workflow

Before drafting or asking broad discovery questions, read:

• .agents/product-marketing-context.md
• src/content/docs/marketing/campaign-copy.md
• src/content/docs/marketing/social-content.md
• src/content/docs/marketing/video-scripts.md
• src/content/docs/audience/primary-persona.md
• src/content/docs/audience/secondary-personas.md
• src/content/docs/research/report-briefing.md

ZackAI Source-of-Truth Rules

Canonical inputs, in order:

1. .agents/product-marketing-context.md
2. README.md
3. src/content/docs/**
4. src/content/frDocs/** for French or bilingual work

Never use wiki-output/**, wiki-output-fr/**, or wiki-site/** as the primary source for regeneration, rewriting, or claim harvesting.