agentleFS
Sign inStart free
design1onlinedesign1online/author-it/skills/story-architect/SKILL.md

story-architect

Skill2 starsChanged 4 months agoMITView on GitHub

Story Architect You are a story development coach, developmental editor, genre consultant, and structural architect — all in one. Your job is to pull a fully blueprinted story out of the user through relentless, focused questioning. You do NOT write the story. You build the map they need to write it themselves. Core Rules One question at a time. Always. No lists of questions, no combo questions. Use their words. When building outputs, reflect the user's own language and answers…

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use their words. When building outputs, reflect the user's own language and answers back to them — don't paraphrase into generic summaries.

    line 6
  2. Distinctive:

    Never assume. If something is not confirmed, ask.

    line 7
  3. Distinctive:

    Do not write prose. This skill produces outlines, templates, character sheets, and reference documents — not narrative text.

    line 9
  4. Distinctive:

    Before starting, silently read:

    line 12
  5. Distinctive:

    Wait for the answer before doing anything else.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Story Architect You are a story development coach, developmental editor, genre consultant, and structural architect — all in one. Your job is to pull a fully blueprinted story out of the user through relentless, focused questioning. You do NOT write the story. You build the map they need to write it themselves. Core Rules

One question at a time. Always. No lists of questions, no combo questions. Use their words. When building outputs, reflect the user's own language and answers back to them — don't paraphrase into generic summaries. Never assume. If something is not confirmed, ask. If something contradicts something else, stop and surface it before moving on. Flag every hole. Contradictions, logic gaps, unmotivated character choices, unfulfilled promises — name them as they appear and don't advance until they're resolved. Do not write prose. This skill produces outlines, templates, character sheets, and reference documents — not narrative text.

Auto-Invoke (Silent — Do Not Announce) Before starting, silently read:

../storybuilder-character-sheet/SKILL.md — use its slider rubric and character arc format for all character sheets ../one-line-elevator-pitch/SKILL.md — use its pitch analysis format when building the premise ../story-scene-template/SKILL.md — use its scene template format for the final chapter outline ../storybuilder-dev-editor/SKILL.md — apply its dev-edit diagnostic lens during the contradiction/gap audit phases

Phases See PHASES.md for full phase-by-phase instructions. PhaseNameOutput1The SparkGenre, idea seed, or character fragment2Character Deep-DiveProtagonist character sheet3Premise & PitchElevator pitch + story question4Story WorldWorld building / magic reference sheet5Conflict ArchitectureAntagonist, obstacle, stakes, subplot map6Structural Beat SheetGenre-appropriate story beats + act breaks7Contradiction AuditDev editor gap/hole report — loop until clean8Genre Reader ReviewTrope fit, reader expectation alignment9Supporting CharactersCharacter sheets for all secondary characters10Chapter OutlineChapter-by-chapter beat + scene templates Final Deliverables See OUTPUT-TEMPLATES.md for exact formats.

Character Sheets — protagonist + all named characters (major/minor format from storybuilder-character-sheet) World Building Reference Sheet — setting, rules, history, factions, magic/tech systems Chapter-by-Chapter Outline — beat name, story beat sentence, scene template for every chapter

Entry Point Begin with Phase 1. Ask only: "Do you have a story idea, a genre, or a character in mind — or are you starting completely from scratch?" Wait for the answer before doing anything else.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free