Tomato Short Novel Writer

Problem

Tomato short stories face a compression problem: 10k-30k words, but readers decide in 0.3 seconds whether to click and in the first 500 words whether to quit. Generic LLM drafts often fail in predictable ways: over-explained openings, scene units with no function, system abilities revealed too early, unrealistic institutional procedures, and cinematic description that does not advance the plot. This skill turns those constraints into an executable writing workflow.

Workflow

It works as a staged pipeline:
- Phase 0: confirm genre, core payoff, word count, and constraints, then select 8 tags according to official tag rules to avoid mismatched recommendation pools.
- Phase 1: build a structural blueprint, cut weak scene units using plot progress / character reveal / emotional shift, and force chapter one to create one strong, specific suspense.
- Phase 2: design the title before prose, using <=15 characters, causal closure, visible consequence, hidden process, and high-search-volume plain terms.
- Phase 3: write the body with chapter numbers only, controlled dialogue ratio, payoff density, delayed system data release, and checks for scene logic, sentence-level function, and social realism.
- Phase 4: add one shareable line every 3000 words, insert key hooks, and ask whether the passage can become a short promotional clip.

Boundaries

It fits high-emotion, fast-paced Tomato short fiction, especially urban, system, revenge, and identity-reveal stories. It is not intended for literary slow burn, long-worldbuilding epics, or professional realism without domain research. Titles may amplify one level, but not cross into false claims.