kai-proof-builder
Build a proof library where every asset has a source, a permission status, and a readiness verdict. The rule that makes this skill different from the viral "authority builder" prompt: proof is collected, never composed. If it can't be traced to a real source, it doesn't exist.
Phase 0: Load Product Context
Check if MARKETING.md exists in the project root (same directory as CLAUDE.md, README.md, package.json).
If it exists: Read it — skip product discovery questions. It has the product name, ICP, value prop, monetization, brand voice, current channels, and competitive landscape.
If it does NOT exist: Auto-explore the codebase to create it in the project root (next to CLAUDE.md). Do NOT ask the user what the product is. Read CLAUDE.md, README.md, PROJECT.md, package.json, landing pages, and any project files. Search for email/ad/analytics config. Then create MARKETING.md using the template from /kai-email-system. Present draft to user for confirmation.
Also load before starting:
harness/references/audit-data-provenance.md(data modes, source tiers, hard rules)knowledge/people/alex-hormozi-knowledge.md(Value Equation and proof mechanics — Phase 2 depends on it)memory/lessons.md(unsourced-claim history)