← ClaudeAtlas

grizzly-initlisted

Set up a new Grizzly writing project. Use when the user wants to start using Grizzly on a novel, when no NOVEL.md exists in the project, or when the user asks to onboard an existing manuscript. Creates NOVEL.md, VOICE.md, STANDARDS.md and the codex scaffold through a guided interview.
HarishDvs/Grizzly · ★ 1 · AI & Automation · score 74
Install: claude install-skill HarishDvs/Grizzly
# Grizzly Init — Project Setup Wizard Creates the project state files through a short interview plus analysis of the author's own writing. Do the steps in order. Don't skip the voice derivation; it is the highest-leverage step in the whole suite. ## Step 1 — Locate the project Ask where the manuscript lives (or will live) and confirm the filename pattern for chapters. All state files go at the project root. If state files already exist, stop and ask whether to update instead (route to grizzly-voice for VOICE.md). ## Step 2 — The interview (NOVEL.md) Ask, in one batch, only what the template needs: 1. Title, one-to-two-sentence premise, current status. 2. Genre and subgenre. 3. **Format: serial or traditional novel.** Explain why it matters in one line (serials need per-chapter hooks and a shorter payoff cadence). 4. POV scheme and tense. 5. **Benchmark titles:** 2-4 published works the author wants their scenes measured against for amplitude. If they hesitate, ask what they read and admire in-genre. 6. Anything the assistant must never do in this project (the never-do list). Fill `templates/NOVEL.md` and write it to the project root. Show it; let the author correct before saving. ## Step 3 — Voice derivation (VOICE.md) Ask for 2-3 passages of the **author's own prose**, 300+ words each, that they consider their best representative work. Published or not doesn't matter; AI-assisted passages do (decline them politely; the spec must be derived from the author's ha