What problem does it solve? Drafting a blog post, newsletter issue, or page of copy without a settled brief leads to vague theses, unclear readers, and endless rewrites. This Skill turns a topic and rough direction into a confirmed brief at docs/briefs/<slug>/brief.md before any prose is written. ## Core Features & Use Cases - Decision-by-decision briefing: Presents a one-sentence thesis, title candidates, and a section outline for the user to correct, asking at most one consequential question at a time with a recommended answer. - Project-grounded context: Reads docs/publications/, GLOSSARY.md, docs/decisions/, and PRODUCT.md so the brief follows the publication's premise, settled terminology, and confirmed writing criteria. - Feedback capture: Records confirmed reusable writing rules and accepted examples into docs/decisions/ via the bundled feedback guidance, keeping piece-only exceptions in the brief. - Use Case: You want to write a blog post about automating smoke tests for an Expo app. The Skill proposes a thesis, title candidates, and an outline, settles the reader and three to five checkable reader questions with you, then writes the brief that drafting will follow. ## Quick Start Ask the assistant to use define-piece to settle the thesis, reader, scope, and outline for your next blog post and record the confirmed brief.