What problem does it solve? Teams and solo writers often start a blog, newsletter, or brand site without a settled premise, so every piece drifts in audience, voice, and coverage. This Skill runs a structured interview to pin down one publication's readers, promised change, voice, coverage, conventions, and evidence of a finished piece, then preserves the confirmed premise as a single current file at docs/publications/<slug>.md. ## Core Features & Use Cases - Guided premise interview: Draws out readers, reading situations, promised change, coverage, and success signals through open questions, without inventing meaning or pushing leading choices. - Voice recommendation through prose: Proposes a short illustrative sample paragraph once readers and purpose are known, then revises the actual sentences based on user reactions until a voice is accepted. - Premise preservation and revision: Writes or updates one file per medium using the publication template, keeping confirmed meaning, delegated choices, assumptions, and intentional unknowns clearly separated. - Use Case: A team wants to launch a developer blog. The Skill interviews them about who reads it and what change each post promises, proposes a voice sample, and writes the confirmed premise to docs/publications/blog.md so later piece briefs stay consistent. ## Quick Start Ask the assistant to use define-publication to settle the readers, purpose, voice, coverage, and conventions of your new publication and save the premise to docs/publications.
