Skip to content

drafting-workflow.md

Latest commit

 

History

History
72 lines (52 loc) · 3.01 KB

drafting-workflow.md

File metadata and controls

72 lines (52 loc) · 3.01 KB

Drafting Workflow

Use this reference when the user wants more than a one-off paragraph: planning, drafting, continuation, revision, or a full LOFTER publish pack.

Intake

Collect the smallest useful set of facts:

  • IP or original world
  • Characters, CP, or relationship focus
  • Hard boundaries, disliked tropes, rating limits, and canon sensitivity
  • Desired feeling in plain language, such as sweet, funny, tense, healing, painful, chaotic, domestic, or plot-heavy
  • Target length and whether this is a standalone post, chapter, or series
  • Known fandom tag customs, if the user already knows them

If the user has no idea, offer 3-5 directions with distinct emotional payoffs and difficulty levels. Avoid making them learn fandom writing terminology before starting.

Route

Map the user's desired feeling to a writing mode:

  • "I want something fast and funny": forum thread, chat log, comedy bit, group reaction
  • "I want sweetness and easy reading": daily sweet story, short vignette, soft confession, domestic scene
  • "I want plot and emotional payoff": canon drama, serial chapter, identity reveal, case/mission structure
  • "I want readers to react": viewing/reaction, public reveal, forum live thread, comment-bait ending
  • "I want a long-term collection": serial outline with recurring motifs, chapter hooks, and stable posting rhythm

Outline Before Drafting

For anything over roughly 1500 Chinese characters, produce:

  • One-sentence premise
  • Reader promise: why this is worth opening
  • Emotional curve: start, turn, peak, aftertaste
  • Scene beats or chapter beats
  • Character motivation and conflict
  • Ending hook or soft landing
  • Content notes and likely tags

Drafting Rules

  • Anchor every scene in who wants what, what changes, and what the reader should feel.
  • Use concrete action, dialogue, and small sensory detail before abstract explanation.
  • Keep names, pronouns, honorifics, timeline, and relationship status stable.
  • Do not overstuff canon keywords as metaphors. Let canon detail appear through action and setting.
  • Avoid generic seme/uke appearance templates. Base physical detail on canon or user-provided description.
  • Let characters misunderstand, avoid, joke, or deflect in their own voice instead of explaining every emotion.

Continuation

Before continuing, summarize the current state:

  • Completed plot so far
  • Current emotional temperature
  • Unresolved conflict
  • Character knowledge gaps
  • Required next beat
  • Continuity details to preserve

If a generated text grows beyond about 3000 Chinese characters, ask to save/update a local draft or use the project works-log.md before continuing.

Publish Pack

When asked to prepare for posting, return:

  • 3-5 title candidates with different tones
  • One short summary and one more hook-heavy summary
  • Content notes/warnings if needed
  • Collection name suggestion for a series
  • Tag set grouped by CP/character, IP/world, form, mood, and content
  • Comment prompt that invites real discussion without begging for engagement
  • Optional next-chapter hook for serial posts