Fanfiction Prompts Template 1
Fanfiction engine: [character] wants [goal], but [specific obstacle] forces [choice with cost].
6 Fanfiction Prompts Templates
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.
Use the framework
How to personalize a template
A strong fanfiction prompt identifies a meaningful change or unanswered space without reproducing source text, gives the writer room to add original scenes and interpretation, and works best when adapted to the canon, characters, and community rules relevant to the chosen fandom.
- 1Choose the template closest to your actual purpose.
- 2Replace every bracketed field with specific information.
- 3Delete any sentence that does not belong in your situation.
- 4Read the result aloud for unnatural transitions or repeated phrasing.
- 5Verify names, dates, links, facts, and promises before sending or publishing.
Fanfiction Prompts Template 2
Constraint engine: Set the scene in [place/time], require [unusual constraint], and make [ordinary object/detail] matter to the outcome.
Fanfiction Prompts Template 3
Reversal engine: Begin with [expected situation]. Reveal [new fact] that changes what the character thinks the problem is.
Fanfiction Prompts Template 4
Relationship engine: Put [character A] and [character B] in conflict over [shared concern], while each is hiding [different fact].
Fanfiction Prompts Template 5
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].
Fanfiction Prompts Template 6
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 → [ ].