# Novel in November

> A planner for writing a novel's first draft in 30 days - usually 50,000 words in November. Give it a premise and how you like to write; the page lays out a calendar heatmap with a word target for every writing day (they add up exactly to the goal), the story's turning points pinned to the right days, and - from the paid lane - one plotted scene and a prompt for every evening. Log words as you go; when the draft stalls mid-month, a second lane diagnoses what the story needs and re-plans the next three days.

URL: https://novel-in-november.skillsafe.ai/
API tutorial: https://novel-in-november.skillsafe.ai/api.html

## Free, in the browser
- Schedule: 30 days from a start date (November 1 by default), rest weekdays, weekends at 1x, 1.5x or 2x; targets rounded to tens with the last writing day absorbing the remainder, so they sum to the goal exactly.
- Turning points: four story shapes (three acts, seven points, mystery, four-part kishotenketsu); each beat lands on the first writing day whose running total reaches its share of the goal, never two on one day.
- Premise read: who the story follows, what they want, what stands in the way - all three = go, two = patch, fewer = rethink.
- Word log on each day of the calendar; heat by share of the day's target; pace tiles (written, expected by today, ahead or behind, words a day to finish, streak, projected total) and a running-total chart.
- A 15-minute sprint timer. Exports: Markdown plan, an .ics calendar with every writing day's target and scene, CSV of the days, JSON of everything. Saved novels live in the person's SkillSafe account (collection `novels`).

## Paid lanes (gpt-terra, metered per run)
- `plan` (verdict go | patch | rethink): logline, acts, one scene and a prompt for every writing day with turning points on their days; patch names what it assumed for the missing pillar; rethink plans only a discovery week and asks questions for week two.
- `unstick` (verdict keep_going | reroute | rewind): symptom, cause and what the story needs; for rewind, the earlier day to change on paper (write forward as if it were fixed - no editing in November); the next three writing days re-planned; a 15-minute sprint; a pace note from the page's numbers. The re-planned days fold back into the calendar with one button.
- The page re-checks every reply: a scene for every writing day and none on rest days, turning-point labels on the right days, the next days and the rewind day valid, word figures not on the page named, no internal field names in prose.

## Contract
- Run input: `task` (`plan` | `unstick`), `title`, `genre`, `premise`; `plan` adds `protagonist`, `want`, `obstacle`, `ending`, `template`, `goal`, `page_days` (JSON), `page_beats` (JSON), `page_flags` (JSON), `page_verdict`; `unstick` adds `stuck_note`, `last_passage`, `plan`, `page_pace` (JSON), `upcoming_days` (JSON), `page_flags` (JSON). See https://novel-in-november.skillsafe.ai/api.html
- Reply: one JSON object per task.

## Caveats
- Not affiliated with any writing-challenge organisation. Targets and pace are arithmetic; scenes are suggestions to write toward.

## Sources
- @danjdewhurst/plot-structure (plot arcs, act structure, turning points, pacing, story timeline) - the scene calendar.
- @jwynia/story-sense (diagnosing what a story needs, whatever its state) - getting unstuck.