submission

# Submission ## Overview Get a finished manuscript out the door. This skill checks submission readiness, drafts the submission package (query letter, pitch, synopsis, blurb, comp titles), builds the manuscript in submission format, and keeps a tracker of where the book has gone. Package files live under `submission/` in the story project. The author sends every submission themselves; this skill prepares materials and records outcomes. ## Prerequisites A story project with a complete or near-complete draft. Verify `story.md` exists in the project root and read its `status`, `genre`, `sub-genre`, `premise`, `author` (or `authors` for a co-written book), and `contact` fields. If `status` is not `complete` or `revising`, tell the user the package can be drafted now but the readiness check will fail until the draft is finished. ## When to Use - Checking whether a manuscript is ready to submit - Drafting or revising a query letter, pitch, synopsis, blurb, or comp list - Building a Shunn-format manuscript for agents or magazines - Writing a retailer or back-cover description for self-publishing - Recording queries sent and responses received - NOT for self-publishing production (ISBNs, retailer metadata, print interiors, launch, rights): use the `publishing` skill. This skill still drafts the blurb and retailer description it uses - NOT for revising the manuscript itself (use `revision-continuity`) - NOT for reader feedback rounds (use `feedback-triage`) ## Hard Rules - ...