notion-doc

Generate Notion-style PRD documents from design and planning markdown files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/oskar-dragon/claude-code --skill notion-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notion-doc
Source: https://github.com/oskar-dragon/claude-code/tree/main/plugins/notion-doc/skills/notion-doc
Command: npx skills add https://github.com/oskar-dragon/claude-code --skill notion-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Convert scattered design and planning documents into a single, structured Notion-style PRD so teams have a consistent, scannable project document for planning, engineering, and stakeholder communication. It reduces manual synthesis work and ensures the output follows a canonical template.

Core Features & Use Cases

  • Synthesize multiple source docs into a single PRD using the Qogita Notion template, preserving key decisions, open questions, and technical specs.
  • Produce canonical output written to docs/notion_prds/<project-name>.md derived from the primary input filename and create the target directory if missing.
  • Guided gap handling: prompts for missing info (impact estimates, API/DB changes, test cases) and follows format/diagram guidelines from included references.
  • Use Case: Turn a brainstorming markdown file plus a technical design doc into a concise PRD for an upcoming sprint planning session.

Quick Start

Use the notion-doc skill to generate a Notion-style PRD from the design doc at docs/ml-pricing-design.md.

Frequently Asked Questions about notion-doc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert design docs and brainstorming notes into a structured PRD?

To convert design docs into a structured PRD, this Skill reads supplied markdown source files and synthesizes the content into a canonical Notion-style project document. It automatically writes the generated PRD to the docs/notion_prds/<project-name>.md directory.

What is the best way to generate a Notion-style PRD from multiple markdown planning files?

Generating a Notion-style PRD from multiple planning files involves synthesizing scattered markdown documents into a single template. This Skill consolidates key decisions, open questions, and technical specs into a scannable document for stakeholder communication.

Does generating a PRD from markdown require a specific template format?

Generating a PRD from markdown uses the referenced Qogita Notion PRD template format. The Skill automatically applies this canonical structure and its diagram guidelines to ensure the output follows consistent internal documentation standards.

How does this PRD generation process handle missing information like API changes or test cases?

PRD generation handles missing information through guided gap handling, prompting you to supply missing details like impact estimates, API or DB changes, and test cases. This ensures the final project specification remains complete before writing.

Can I use this tool to create PRDs for sprint planning from technical design documents?

You can use this tool to create PRDs for sprint planning by processing technical design documents and brainstorming notes. It reduces manual synthesis work by outputting a concise, structured markdown document ready for engineering team reviews.

What are the limitations when converting project specs into a canonical PRD template?

A limitation when converting project specs into a canonical PRD template is that the source files must be in markdown format. Additionally, the output directory is strictly set to docs/notion_prds/, which is automatically created if missing.