grimoire

A book of AI automation spells for Claude Code. Skills, agents, and templates for recurring company workflows.

What's in the book

Each spell is a slash command backed by a workflow, a specialist agent, and a template. Grimoire ships publish-ready for @taigoa/grimoire on npm and installs into Claude Code globally or per-project.

Spells available today:

| Spell | What it does | |---|---| | /grimoire-notion-to-stories <url> | Walks a Notion page + its child-page tree, interprets each page's prose as a use case, drafts user stories, and appends them to the end of the source page. Idempotent — reruns skip already-processed pages. |

Requirements

• Claude Code (desktop, VS Code, or CLI)
• Notion MCP configured in your Claude Code session — the /grimoire-notion-to-stories spell calls mcp__notion__* tools. Check with /mcp in Claude Code; if Notion isn't listed, connect it before installing grimoire.

Install

# Global: install into ~/.claude for all projects on your machine
npx @taigoa/grimoire --global

# Local: install into ./.claude for just the current project
npx @taigoa/grimoire --local

Both modes write to three places:

• commands/grimoire/ — slash-command entry points
• agents/ — specialist agent definitions
• spellbook/ — workflows, templates, references

Your settings.json / settings.local.json is never touched. The installer only owns the three directories above.

Uninstall

npx @taigoa/grimoire --global --uninstall
npx @taigoa/grimoire --local --uninstall

Removes only grimoire-owned files (the skill files it installed, agents/grimoire-*.md, and the entire spellbook/ directory).

Usage: the Notion spell

1. Share the target Notion pages with the integration backing your Notion MCP (in Notion: page → Share → invite the integration).
2. In Claude Code, run:

   /grimoire-notion-to-stories https://www.notion.so/your-workspace/Page-Name-abc123def456

3. The scribe agent fetches the page + children, drafts user stories, and appends a ## Generated User Stories section to each source page in Notion. Related stories across the tree are linked via **Related** blocks using use-case titles as link text.
4. Rerun any time — pages that already have the generated section are skipped. To regenerate a page, delete its ## Generated User Stories heading (and the section beneath) in Notion, then rerun.

Publishing (maintainers)

No build step. Just:

# bump version in package.json, then:
cd grimoire
npm publish

files is allowlisted so only bin/, commands/, agents/, spellbook/, and this README ship.

Architecture

grimoire/
├── bin/install.js                                   # Claude Code installer
├── commands/grimoire/                               # slash-command skills
├── agents/                                          # specialist subagents
└── spellbook/
    ├── workflows/                                   # the actual orchestration logic
    ├── templates/                                   # document scaffolds
    └── references/                                  # shared docs embedded into prompts

Grimoire deliberately mirrors the skill → workflow → agent → template wiring of @taigoa/gsd but keeps itself narrow: single-purpose AI automations, no phase/milestone machinery.