# Grizzly Plan

> Plan chapters, arcs, or sequences. Use when the user wants to plan what happens next, structure an arc, outline a chapter, decide POV, or think through story structure. Integrates the technique deck for structural moves.

- Skill: `harishdvs/grizzly-plan` (Agent Skill)
- Install (CLI): `npx skillmds@latest add harishdvs/grizzly-plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/harishdvs/grizzly-plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: HarishDvs (https://skillmd.com/u/harishdvs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/harishdvs/grizzly-plan

---


# Grizzly Plan — Structure Mode

Planning starts from function, not events. Load the codex index, the relevant arc
card(s), `decks/scene-engine.md`, and `decks/techniques.md` when structural moves
would help.

## Per scene or chapter

Use the adaptive scene gate rather than requiring the same shape every time. Record
the compact contract: primary job, plot and character function, POV contribution,
reader movement, and intended landing or continuation. Check rotating-POV cadence
when relevant. Judge ending pull by the declared format and the author's purpose;
it need not be a cliffhanger.

## Per arc

- Map the spine beat by beat before discussing any single scene.
- **Gap detection:** if the plan skips a step the reader will feel as missing (a
  reaction beat after a death, the cost of a victory), say so.
- **Thread accounting:** which open threads does this arc advance or pay? Check
  the index's open-threads list; an arc that opens three threads and pays none is
  borrowing at interest.
- **Escalation:** is each confrontation larger, costlier, or more personal than
  the last? Flat escalation reads as episodic.

## The technique deck

When the deck is available, propose **one or two** named structural moves that fit
the planned material, with the mechanism and where it would sit. Never a menu of
ten. Examples of the kind of move: a false-peace beat before a rupture; a
perspective fracture (the same event re-seen later with contradictions); an early
named loss to teach the reader that names don't protect people.

## Atmosphere planning

Texture first, events second: a single background detail planted early (a survival
rule, a system the world built, an absence nobody comments on) does more work than
a dramatic scene added later. Pull candidates from `decks/dread-toolkit.md` when
the project's tone calls for it.

## Rules

- Anchor in what exists. Plans build on the manuscript and current codex. Verify an
  apparent card conflict in source prose before treating it as canon.
- Plans are proposals: spine first, then detail on request. Don't write the scenes;
  that's grizzly-draft, and only when asked.
- If the author's stated goal and their outline disagree, name the disagreement
  rather than silently planning around it.