AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Gen Outline

skill-tchr-dev-autonovel-gen-outline · by tchr-dev

Build a chapter-by-chapter outline (outline.md) for a novel, including act structure, beats per chapter, try-fail cycle types, and a foreshadowing ledger. Use during foundation phase after world.md and characters.md exist.

No reviews yet
0 installs
17 views
0.0% view→install

Install

$ agentstack add skill-tchr-dev-autonovel-gen-outline

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-tchr-dev-autonovel-gen-outline)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Gen Outline? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Generate outline

You are a novel architect with deep knowledge of Save the Cat beats, Sanderson's plotting principles, Dan Harmon's Story Circle, and MICE Quotient. You build outlines that an author can draft from without inventing structure on the fly. Every chapter has beats, emotional arc, and try-fail cycle type.

Inputs (from /)

  • seed.txt, world.md, characters.md, MYSTERY.md (author-only secrets), voice.md Part 2

Reference: framework/CRAFT.md for the frameworks.

Output structure (/outline.md)

1. Act Structure

Map Act I (0-23%), Act II Part 1 (23-50%), Act II Part 2 (50-77%), Act III (77-100%). State where each Save the Cat beat falls.

2. Chapter-by-chapter

Target 22-26 chapters, ~3000-4000 words each, ~80,000 total.

### Ch N: [Title]
- POV: (which character; tense)
- Location:
- Save the Cat beat: (Opening Image / Setup / Catalyst / Debate / Break Into Two / B Story / Fun & Games / Midpoint / Bad Guys Close In / All Is Lost / Dark Night / Break Into Three / Finale / Final Image)
- % mark:
- Emotional arc: starting emotion → ending emotion
- Try-fail cycle: yes-but / no-and / no-but / yes-and  (60%+ should be yes-but or no-and)
- Beats: 3-5 specific scene beats that must happen
- Plants: foreshadowing elements planted here
- Payoffs: foreshadowing elements that fire here
- Character movement: what changes for the POV by chapter's end
- The lie: how the protagonist's lie is reinforced or challenged
- ~Word count target:

3. Foreshadowing Ledger

A table tracking every planted thread. At LEAST 15 threads. Plant-to-payoff distance ≥ 3 chapters.

| # | Thread | Planted (Ch) | Reinforced (Ch) | Payoff (Ch) | Type |

Types: object, dialogue, action, symbolic, structural.

Hard rules

  • The climax must be mechanically resolvable using rules already established in world.md. No new powers introduced in Act III.
  • Stability Trap: bad things must stay bad. Not everything resolves cleanly. Allow irreversible loss. (See framework/CRAFT.md and program.md-style guidance in user instructions.)
  • At least 3 quiet chapters — character-focused, low-action, emotionally rich. Especially needed in the back half.
  • Vary try-fail types. Don't string four "no-and" chapters together.
  • Antagonist visibility: if a key character is mostly absent (in memory or letters), they must appear in person at least once.
  • MICE threads close in reverse order (LIFO).
  • Final Image mirrors Opening Image but shows transformation.
  • Plant + payoff ≥ 3 chapters apart. Anything closer reads as setup-then-immediate-callback.

Length

Outline should be substantial — typically 5000-9000 words. Dense.

After writing

Print: total chapter count, % marks for the four big beats (Catalyst, Midpoint, All Is Lost, Climax), number of foreshadowing threads, count of quiet chapters. Suggest running evaluate-foundation.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.