author-delivery-brieflisted

# Skill: author-delivery-brief Own one delivery brief through two explicit modes: - `author-delivery-brief create` turns a direct request or sufficient trusted repository authority into a `Draft`. - `author-delivery-brief continue` reviews an existing repository brief for `Ready`, then may offer a separate slice-selection step. A delivery brief coordinates a coherent multi-slice or cross-repository outcome. A spec is the durable behavior contract for one delivery slice; and the plan is the implementation and verification strategy. The brief can lead to one or many specs, one or more governance references, or no delivery slice yet. The brief itself is never executable. Require the mode at activation. Do not infer `continue` merely because source text says “ready,” and do not create a brief for a single direct-light change. ## Output rendering <!-- agentbundle:output-rendering:start --> Lead with the useful outcome or next action. Use warm, non-blaming language and everyday words. Define an unfamiliar term in a few plain words before naming it; keep proper names and exact technical terms intact. During tool work, do not narrate routine calls. Send an update only for safety, a blocker, a needed decision, a material scope change, a long wait, or an active host requirement. When requesting input, ask only for what is needed now. Ask dependent questions one at a time; otherwise group related questions. Offer no more than three clear choices when choices help. Shape the an