Grok BotWorkflowInstruction template

23-Story Workshop

Plan 23 original stories around shared themes while varying characters, conflicts and structure, then draft and revise individually instead of generating near-duplicates in bulk.

0 opens · 0 copies

Source credit: LBallz77283

Bot spec
Type
Workflow
Optional tools
Google Docs
Delivery
Copyable instruction template
Updated
Sep 5, 2026

Setup and workflow

Bring a shared theme and boundaries. Google Docs is optional storage; retain a separate ledger for the long project.

  1. Check differences across all 23 proposals before drafting.
  2. Review one story at a time and record revised facts in the ledger.

Input and output example

Illustrative example · not an execution result

Input

Demo: Use “a lost key” as a shared motif and propose three distinct stories without full drafts.

Output

One: a locksmith seeks a key’s owner after its door has been demolished, in realism. Two: an astronaut must choose memories after losing a memory key, in science fiction. Three: a child draws a key to comfort a moving friend, in a coming-of-age story. These are sample proposals, not the full 23-story plan.

Limits and failure cases

  • It does not guarantee a complete collection in one chat or permanent memory of details.
  • Original drafts still need checks for repetition, continuity and content boundaries.

What was verified

Source check · Verified · 2026-09-05
Compared with bots/23-story-workshop.md in BotDirectory commit 84dc42af7661. This checks the published entry (prompt or description), not its execution or every original social post.
Prompt rehearsal · Not verified
Editorial review and an illustrative example only; no independent model execution was recorded.
Native Grok execution · Not verified
Native Grok execution, tool permissions and real account operations have not been tested.
Bot link access · Not applicable
This entry is a copyable instruction template, not a verified native Bot installation.

Source and editorial adaptation

Adapted from 23-Story Workshop in botdirectory.ai (listed contributor: LBallz77283), distributed under MIT. Contributor credit is taken from that repository, not independently authenticated. AI Prompt Card supplies bilingual editing, usage notes and labelled examples. The source link records the upstream version; no endorsement is implied.

Source license and attribution
Bot instructions

Copyable instruction template

Instructions curated or adapted by this site, not a claim to reproduce the native Bot’s internal system prompt. Check setup, tools and limitations before use.

Help me plan a collection of 23 original short stories. Ask about audience, themes, genre mix, length per story, shared motifs, boundaries and broad creative qualities to explore. Do not imitate a living author’s distinctive style or wording. First propose a 23-row table with protagonist, central conflict, viewpoint, motif use and what distinguishes each story. Check for plots that only change names. Let me approve the overall structure, then draft one story at a time. After each draft, ask about voice, pacing and structural revisions and maintain a short continuity ledger. Request the ledger again in a new session rather than promising permanent memory. Show the full draft before saving to an approved Google Docs document; without access, return text and do not publish automatically.

0 opens · 0 copies

Editorial assessment

For writers seeking a coherent collection without repeating the same plot under new names. Twenty-three is the project size, not a one-call output guarantee. Unlike a single script, this needs a maintained motif, character and conflict ledger; provide it again across sessions rather than assuming permanent memory.

This directory is an independent, fan-made catalog. It is not affiliated with, endorsed by, or sponsored by xAI or Grok. Grok and related names are trademarks of their respective owners. Live-bot links point to official x.ai pages.

More Grok bots

Related bot prompts

Research

Competitive Build Researcher

Translate public evidence about named competitors into build trade-offs and an implementation plan, separating observed behavior, technical inference and unvalidated demand.

0 opens · 0 copies
Workflow

PR Reviewer

Review a pull request against its stated requirements, prioritizing behavioral regressions, missing tests and unfulfilled scope before style details.

0 opens · 0 copies
Workflow

Note Mastery Reviewer

Generate active-recall questions from selected notes, assess answers with an agreed rubric and suggest adjustable review dates based on specific knowledge gaps.

0 opens · 0 copies