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.From its SKILL.md
npx -y skills add HarishDvs/Grizzly --skill grizzly-planAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.5 KB, as published. Nobody here has run it
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most plan spec skills give
Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06
- Ask one question at a timein 73 of 1360
- Write the spec using the templatein 22 of 1360
- Ask clarifying questions if neededin 19 of 1360, across 18 files
- Wait for user confirmation before proceedingin 19 of 1360
- Save plans to the plans directoryin 17 of 1360, across 13 files
- Check for product marketing context firstin 16 of 1360, across 5 files
- Read the plan file completelyin 16 of 1360
- Order tasks by dependencyin 16 of 1360
- Gather context from the conversationin 15 of 1360, across 9 files
- Explore the codebase instead of askingin 15 of 1360, across 13 files
- Wait for explicit user approvalin 14 of 1360, across 13 files
- Quiz the user on the breakdownin 13 of 1360, across 7 files
Said here and by no other author read
- Load the codex index and relevant arc cards
- Use the adaptive scene gate
- Record the compact contract per scene
- Map the spine beat by beat
- Propose one or two named structural moves
- Anchor plans in existing manuscript and codex
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.