How it works

Foe: Paper Golem, documents, slides or sheets to produce.

Paper Golem

1. Paper Golem

   The Paper Golem blocks the way.

   What really happensIt stands for documents, slides or sheets to produce.

   Scribe: Context 100/100.

2. Paper storm

   A storm of pages cuts across the party.

   What really happensDocuments pile up, and each one needs reading and formatting.

   Scribe takes 4. Scribe takes 4. Scribe: Context 92/100.

3. Notion Plugin for Codex

   The Notion relic is equipped in Codex.

   What really happensCodex loads the Notion plugin (version 0.1.7). It is not a Claude Code plugin. A connected Notion workspace is required.

   Paper Golem takes 15.

4. Notion Plugin for Codex

   A portal opens to the Notion app the relic is bound to.

   What really happensThe plugin's .mcp.json points at https://mcp.notion.com/mcp and uses the connected Notion app for its skills.

   Paper Golem takes 28.

5. Paper storm

   The Paper Golem uses Paper storm.

   Scribe takes 4. Scribe takes 4. Scribe: Context 84/100.

6. Notion Plugin for Codex

   Specs, notes, and meeting pages are read for the job.

   What really happensSkills cover research across Notion, meeting pre-reads, and reading specs before planning.

   Paper Golem takes 13.

7. Notion Plugin for Codex

   Plans, briefs, and captured decisions are written back as pages.

   What really happensnotion-spec-to-implementation, notion-research-documentation, notion-meeting-intelligence, and notion-knowledge-capture produce structured pages.

   Paper Golem takes 19.

8. Notion Plugin for Codex

   The golem drops a page the workspace can keep.

   What really happensYou get implementation plans, research briefs, meeting materials, or knowledge pages written in the connected workspace.

   Paper Golem takes 25. Paper Golem falls.

9. Victory

   The Paper Golem falls.