Firstp1ck Serial fiction
When to use
Use for web novels, episodic prose, multi-volume continuity, or an installment whose ending needs stronger forward interest.
Inputs and assumptions
Identify the installment length, current arc, open promises, reader knowledge, and any explicitly named platform constraints. Do not assume a commercial platform or scraping requirement.
Portable workflow
- Read the latest checkpoint and the actual preceding installment.
- Identify what this installment gives the reader and what it asks them to anticipate.
- Advance at least one meaningful line of change. Do not replace progress with repeated status descriptions or recap.
- Choose an ending appropriate to the scene: decision, revelation, reversal, partial resolution, or earned cliffhanger.
- Track unresolved threads by setup, current state, and intended payoff. Keep future plans separate from events.
- For a new arc or volume, carry over only relevant state and reintroduce it through current pressure.
- Save the installment and accurate continuation notes using the project workflow.
Safety and side effects
No automatic publishing, schedule creation, market scraping, or chapter spamming. The author approves major arc changes.
Scripts, references, and dependencies
Use formats and continuity guidance. No mandatory external services.
Verification
Check local payoff, non-repetitive progression, earned hooks, and consistency of abilities, injuries, relationships, timelines, and knowledge.
Pi adapter
Use /writer new book "The Ninth Gate" --format web-novel, then /writer new chapter or /writer continue.