academic-book-projectlisted

Initialize, inspect, and coordinate a persistent academic book workspace with minimal human approval by default. Use when the user asks to start, continue, plan, manage, validate, export, or check an academic book or chapter. Routes discovery, evidence, authoring, and review while preserving phase order, exception stops, and human final authority.
jakkzz/agent-skills · ★ 0 · AI & Automation · score 73

Install: claude install-skill jakkzz/agent-skills

# Academic Book Project Use this skill as the workflow router. Durable state lives in files, never only in chat. ## Start 1. Locate `BOOK_STATE.yaml` from the current directory upward. If none exists there, the core may discover one unique workspace within six directory levels below the nearest repository/current directory. If multiple nested books exist, require an exact `--root`; never guess. 2. If no parent or unique nested workspace exists, ask whether to initialize. Prefer the human `/book-init` command; otherwise run: ```bash python3 "$SKILL_DIR/../../scripts/bookctl.py" --json --root <target> init \ --title <title> --field <field> --audience <audience> ``` 3. Read `BOOK_STATE.yaml`, `book-brief.md`, `style-guide.md`, `glossary.yaml`, the current chapter's `CHAPTER_STATE.yaml`, and its current artifact. 4. Run `book_status` or `bookctl status` before proposing work. `BOOK_STATE.yaml`, `CHAPTER_STATE.yaml`, `approvals.yaml`, `source-map.yaml`, and `glossary.yaml` contain JSON-compatible YAML. Preserve that machine-readable format. ## Required phase order `brief → research-plan → source-selection → outline → sample → draft-v1 → review → revision-plan → draft-v2 → verification → final` Never skip a phase. `approval_mode` controls interruption frequency: - **`minimal` (default):** require human approval only for the chapter `brief` mandate and the complete `final` packet. After brief approval, complete every intermediate artifact, run its deterministic