Menu

Individual skill

book-outline

Phase 2: Outlining. Build the chapter-by-chapter outline with genre structure, create the book bible, validate structure with book-architect, and get author approval.

plugins/epicsagas/Velith/skills/book-outline/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Phase 2: Outlining

Goal: an outline detailed enough that each chapter can be drafted in full context without inventing structure, and a bible that keeps twenty chapters telling one story or making one argument.

Read `PRD.md`, `STYLE.md`, `ideation.md`, `sources/INDEX.md`, the genre skill, and `${CLAUDE_PLUGIN_ROOT}/skills/loom/quality-bar.md`.

## Process

1. **Invoke `book-architect`** with the project directory. It produces `outline.md` (draft) and `bible.md` (initial), then validates its own structure and writes the score and issues into `outline.md`'s `## Validation` section.
2. **Review the validation.** If the score is below 8/10 or any Critical issue remains, have book-architect revise once. If still below, surface the issues to the author instead of iterating blindly.
3. **Author checkpoint.** Present: the structural shape (one paragraph), the chapter list with one-line purposes, the pacing map, the top three risks the architect flagged, and the bible summary. Ask for approval or changes. Required stop.
4. On approval, add `## Approval` to `outline.md` with the date and any author notes. The router treats an outline without this section as unapproved.

## What a chapter spec must contain