Daily Writing Prompts Template 1
Daily-writing engine: [character] wants [goal], but [specific obstacle] forces [choice with cost].
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
Effective daily prompts are specific enough to begin immediately, varied enough to exercise different skills, and small enough that a writer can respond in minutes while still discovering material worth developing later.
Daily-writing engine: [character] wants [goal], but [specific obstacle] forces [choice with cost].
Constraint engine: Set the scene in [place/time], require [unusual constraint], and make [ordinary object/detail] matter to the outcome.
Reversal engine: Begin with [expected situation]. Reveal [new fact] that changes what the character thinks the problem is.
Relationship engine: Put [character A] and [character B] in conflict over [shared concern], while each is hiding [different fact].
Source-ledger and revision-history audit for Daily Writing Prompts: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].