Notion Spec To Implementation

Bridges the gap between product specs in Notion and actual implementation work. Takes your PRD or feature doc, extracts requirements and assumptions, then generates a proper implementation plan with phases, dependencies, and granular tasks, all linked back to the original spec. The workflow is methodical: search and fetch your spec, parse it for requirements, create a plan page (quick or detailed), spin up sized tasks in your database, and keep everything synced with progress updates. Works through the Notion MCP, so you need that configured first. Most useful when you're staring at a dense spec and need to turn it into trackable work without manually copy-pasting context into a dozen task cards.

skills.sh installs: 350
GitHub stars: 33.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add davila7/claude-code-templates --skill notion-spec-to-implementation --agent claude-code

Installs into .claude/skills of the current project.

Files

Spec to Implementation

Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.

Quick start

Locate the spec with Notion:notion-search, then fetch it with Notion:notion-fetch.
Parse requirements and ambiguities using reference/spec-parsing.md.
Create a plan page with Notion:notion-create-pages (pick a template: quick vs. full).
Find the task database, confirm schema, then create tasks with Notion:notion-create-pages.
Link spec ↔ plan ↔ tasks; keep status current with Notion:notion-update-page.

Workflow

0) If any MCP call fails because Notion MCP is not connected, pause and set it up:

Add the Notion MCP:
- codex mcp add notion --url https://mcp.notion.com/mcp
Enable remote MCP client:
- Set [features].rmcp_client = true in config.toml or run codex --enable rmcp_client
Log in with OAuth:
- codex mcp login notion

After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.

SKILL.md on GitHub