brieflisted

# brief Produce an interactive HTML brief as the medium for an intermediate operator-agent discussion. The brief is a single self-contained `.html` file. Where the artifact has decisions to make, it carries inline controls (radios, checkboxes, sliders, free-text fields). Whether or not it has decisions, it always ends with a sticky "Copy execution prompt" button: the operator reviews the artifact, optionally commits to choices and notes, and pastes a clean execution prompt into a fresh context window where another agent acts on it. The pattern exists because plans, specs, design explorations, annotated diffs, decision matrices, and navigable reports are spatial information that markdown flattens. HTML preserves dimensionality (side-by-side comparison, collapsible detail, jump links, tabs, swatches, severity tags) and lets the operator interact with the artifact (toggle options, expand sections, scrub a slider) before the next agent runs. The export-button feedback loop is the second half of the pattern: whatever the operator did in the UI returns to the agent as a focused prompt, instead of leaving ambiguity in prose. ## When this skill applies This skill is the **default format** for any intermediate operator-agent discussion artifact. The pattern's value is spatial layout, interactivity, and the export-button feedback loop into the next prompt. Trigger whenever **any** of these are true: - **Intermediate discussion document.** The artifact is a plan, spec, draft propos