ghostwrite

Ghostwrite

Write one bounded artifact in the voice of the human or team responsible for it. The skill turns validated evidence and a clear objective into useful public or internal prose without exposing the machinery that produced the evidence or inventing facts to make the draft feel complete.

This is the reusable authorship primitive behind briefs, release notes, trust reports, maintainer updates, newsletters, and social drafts. It can also package an accepted draft for a channel and prepare a provider-neutral handoff. It never publishes, posts, sends, or claims provider acknowledgement.

Writing standard

• Lead with the reader's problem, decision, or next action—not the evidence collection process.
• Turn evidence into concrete claims and examples; do not dump receipts, issue threads, graph traces, or machine packets into the body.
• Match the project's vocabulary and supplied writing context instead of defaulting to generic AI, launch, preview, or adoption language.
• Write as the responsible maintainer or operator. The surfaced artifact should not call itself agent-generated or narrate how a model worked.
• Prefer one sharp, useful artifact over several thin sections.
• Narrow the claim or return needs_more_evidence rather than filling a gap with plausible prose.

Runners and chain boundaries

draft composes admit, one writing turn and verify. admit binds a ready research or evidence packet by its native digest and optionally admits digest-bound brand-voice and taste-profile context. Only admitted claims and source digests may enter the draft. verify checks every material claim and every context binding before releasing it, and withholds anything it cannot bind. A skill that owns its own writing judgment composes admit and verify around its own writing turn, so its draft keeps the same guarantees.

package converts a validated draft bound to its evidence into a deterministic channel payload, bound to its digest, in not_sent state; a draft without an evidence binding, or with a claim citing a source it is not bound to, is held. handoff binds that payload's digest to the exact target and records whether delivery crosses outside the team, whether it then needs the delivering lane's approval, and the next actor. Neither runner grants external authority. Delivery belongs to message-send, a publication skill, or the relevant provider connector.