fiction-writer

Use when the user wants Dean Wesley Smith-style feedback on a scene's ending — Dent-zone length (800–1,500 words), the kicker line, and the "petered-out tail" check (writing past the natural cut point). Observational only; names where the energy peaks and where the prose drains past it. Trigger on "cliffhanger drill", "cut drill", "where should I end this scene", "did I write past the cliffhanger", "Dent check", "scene ending feedback".

Use when the user wants Dean Wesley Smith-style depth feedback on a scene they've written — observations on witness syndrome, opinion-tinting, sensory grounding, fake details, and character-specific perception. A learning drill, not a rewrite. Trigger on "depth drill", "depth feedback", "depth check", "is this in depth", "check depth on scene N", "Dean over my shoulder", "what's my depth like", "run depth on this scene".

Use when the user wants to scan a scene for placeholder nouns ("barn", "office", "car", "room") — the words that hand reader control over because every reader fills in their own image. Observational only — names the placeholders, never proposes replacements. Trigger on "fake detail drill", "fake details", "find placeholders", "kill fake details", "scan for vague nouns", "where am I being lazy with detail".

Use when the user wants Dean Wesley Smith-style feedback on the opening of a scene or chapter — five-senses grounding in the first 100 words, character-anchoring through opinion, the 400–500-word depth-before-action rule. Observational only; names what the opening is doing, never rewrites. Trigger on "opening drill", "check my opening", "is my opening grounded", "five senses check", "drill the opening of scene N", "Dean over my shoulder on the opening".

Use when the user wants to scan a scene for viewpoint glitches — the moments where prose drops out of the character's head. Catches the three documented glitch patterns ("he thought" / italicized thoughts / author-described settings) plus information the POV character couldn't possibly know. Observational; never rewrites. Trigger on "pov drill", "glitch check", "viewpoint check", "find glitches", "where am I out of character's head", "scan for pov glitches".

Use when a finished book needs to go out the door — building the ebook and print files, writing the sales copy, and filling the KDP, Draft2Digital and Notion Press forms. Trigger on "publish", "get this ready for KDP", "D2D upload", "Notion Press", "print edition", "paperback", "upload sheet", "back cover", "format for submission".

Use when the user wants to discuss a craft, business, or mindset workshop they're studying — pulls the distilled material into a structured conversation. Designed for periodic course-correction on business-of-publishing and writer-mindset topics that don't belong in writing-time tooling. Trigger on "discuss [topic]", "let's talk about [Dean's workshop X]", "study [topic]", "course correct on [topic]", "what does Dean say about [topic]", "I want to think through [topic]".

Use when the user wants the book-wide repetition count — phrases, tells, and openers that recur across scenes — or after any multi-scene edit pass. Trigger on "tic audit", "tic sweep", "repetition scan", "n-gram", "what am I overusing", "run the lint", "prose lint", "AI tells", "before I compile, check repetition".