All skills
danjdewhurst avatar

/premise-workshop

@da9f811

This skill should be used when the user asks to "brainstorm a story idea", "I have an idea for a story", "what if", "develop a premise", "is this idea strong enough", "workshop my logline", "premise", "story concept", "what should I write", "short story or novel", "novella or novel", "name my book", "title ideas", or has a spark (an image, a character, a setting, a question) and wants to turn it into a tested premise before starting a story project. NOT for the controlling idea or theme of an existing story (use theme-craft).

Use this Skill: https://skilld.dev/gh/danjdewhurst/story-skills/premise-workshop

This session only. Nothing lands on disk.

referencesform-choice.md

≈931 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Form Choice

The idea's scope decides its natural length. A premise stretched past its scope sags in the middle; one squeezed below it reads as a summary.

Count the moving parts

Moving part Short forms Middle forms Novel
POV characters 1 1-2 1 or more
Plot threads (MICE threads, see ../../plot-structure/references/mice-quotient.md) 1, maybe 2 nested 2-3 3 or more
Significant locations 1-2 2-4 Any
Story time span Hours to days Days to months Any
Named cast 1-3 3-6 Any
Changes the story dramatises One One major, one minor Several, interlocking

If most parts land in one column, recommend that form. If they straddle, say so and give the trade-off: cut a thread to shorten, or add a complicating thread to lengthen.

The forms

The form field in story.md takes one of these values; story init --form <form> sets it and a default target-words when none is given.

form Rough length What it does well Watch out for
flash Up to about 1,500 words One moment, one image, one turn Needing backstory to land
short-story About 1,000-7,500 One change, a single effect (see ../../plot-structure/references/short-story-form.md) Subplots, large casts
novelette About 7,500-17,500 One change with room for a second character's pressure Being a long short story with padding
novella About 17,500-40,000 A contained situation, one strong arc, intensity A novel's worth of threads
novel About 40,000-200,000; genre norms vary Multiple arcs, subplots, world, time A single-situation premise that cannot generate 60+ scenes
serial Episodes, each with its own question Ongoing situations, cliffhangers, reader habit A story that only pays off at the end; see the genre-craft serial reference
picture-book Up to about 1,000 words, text shared with art One emotional truth, read-aloud rhythm, page turns Describing what the art will show
chapter-book Roughly 4,000-15,000 for early readers Short chapters, simple plots, a series-able lead Vocabulary and sentence length above the reader

The bands are rough conventions; SFWA award categories set the novelette and novella lines that many short-fiction markets use. Genre norms for novels are in ../../submission/references/word-count-norms.md. story validate warns when target-words sits outside the form's usual range; take the warning to the user rather than silently changing either.

serial sets no book-level target-words: set target-words on each episode chapter instead.

Questions that decide it

  1. Where does the story end? If the ending is one scene after the inciting situation resolves, it is short. If each answer opens a new question, it is long or serial.
  2. How much world must the reader learn? A world that needs teaching needs pages. Short forms need a world readers already know, or one revealed in a single strange rule.
  3. What does the user want to finish? A first project, a market (magazine, anthology, agent, retailer), or an experiment? A short story finished beats a novel abandoned. Ask; do not assume.
  4. Who is the reader? Picture books and chapter books have audience conventions that override scope; see ../../genre-craft/references/mg-ya.md for middle grade and YA.

Changing form later

Form is a planning decision, not a contract. If drafting shows the idea is bigger or smaller, edit form and target-words in story.md, then run story validate . and story report ..

Source: SKILL.md on GitHub

No alerts3d3 checks · Risk SAFE
  • Gen Agent Trust Hub3d

    This skill facilitates the development of story premises, from initial sparks to tested loglines and project initialization. It utilizes a local CLI tool called 'story' for metadata management and name collision checking. The skill demonstrates strong security awareness by providing specific instructions to sanitize user-provided text before it is used in shell commands, protecting against command injection attacks.

  • Socket3d

    No alerts

  • Snyk3d

    Risk: LOW · No issues

Signed by skilld at da9f811. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 4 days ago

README badge

README badge for danjdewhurst/story-skills/premise-workshop