From grizzly
Create, update, or bootstrap the project codex (chapter cards, arc cards, character cards). Use when a chapter is finished or edited, when continuity cards need updating, when the user asks to card a chapter, or to onboard an existing manuscript into the codex.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grizzly:grizzly-cardsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The codex is the project's memory: extractive cards that let any session answer
The codex is the project's memory: extractive cards that let any session answer
continuity and planning questions without reloading the manuscript. Templates live
in templates/codex/. The index (codex/_Index.md) is the orientation map; keep
it current with every card change.
_Index.md, and update any arc card whose spine this
chapter extends.When a chapter's events change in any session, its card updates in the same session. No exceptions; a stale card is worse than no card because it is trusted. Sync direction is always chapter → card. Also check: did the edit alter anything another card states (a character fact, a thread payoff)? Update those too, and the index's open-threads list.
Every Opens entry should eventually appear in some chapter's Pays off. The
index keeps the running list of open threads. When asked, produce a thread-debt
report: every opened thread not yet paid, with the chapter it was planted in. This
list is the project's anti-plot-hole device.
For onboarding a manuscript that already has chapters:
codex/ should live. Scaffold it from the templates if absent.Preserve-line marking during bootstrap: ask once per arc (not per chapter) whether the author wants to flag untouchable lines, to keep the pass moving.
npx claudepluginhub harishdvs/grizzly --plugin grizzlyProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.