Official agent skill

Notion Spec To Implementation

by JetBrains in JetBrains/skills

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

OfficialMITAuto-check passedAgent Workflows

Install Notion Spec To Implementation

skills CLI
$ npx skills add JetBrains/skills --skill notion-spec-to-implementation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install JetBrains/skills notion-spec-to-implementation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/notion-spec-to-implementation .claude/skills/notion-spec-to-implementation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
notion-spec-to-implementation
GitHub stars
366
Used in
5 other repos
Token cost
~904 tokens
SKILL.md length
370 words
Files
19 (incl. assets)
Skills in repo
76
Repo updated
First seen
Licence
MIT

At a glance

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

  • Works in 6 steps: If any MCP call fails because Notion MCP… → Locate and read the spec → Choose plan depth → …
  • Implementing PRDs/feature specs and creating Notion plans + tasks from them
  • SKILL.md covers Quick start, Workflow and References and examples
  • Calls codex; reaches mcp.notion.com

What it does

Notion Spec To Implementation is an agent skill from JetBrains/skills, published by the product's own GitHub organization. Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 23 other files, including assets (for example `agents/openai.yaml`, `evaluations/README.md` and `evaluations/basic-spec-implementation.json`).

It sits in Agent Workflows, covering PRD writing and Planning. It works with Notion and Model Context Protocol. The repository describes itself as: Curated agent skills collection verified by JetBrains. The licence is MIT.

When your agent uses it

  • Implementing PRDs/feature specs and creating Notion plans + tasks from them
  • Tasks that involve PRD writing
  • Tasks that involve Planning

Example prompts

  • “/notion-spec-to-implementation”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. If any MCP call fails because Notion MCP is not connected, pause and set it up
  2. Locate and read the spec
  3. Choose plan depth
  4. Create tasks
  5. Link artifacts
  6. Track progress

What it can do on your machine

Read from SKILL.md and the folder at commit e0f258b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • codex

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • mcp.notion.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Notion Spec To Implementation loads about 904 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 370 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~904

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from JetBrains/skills at commit e0f258b, republished under its MIT licence (© JetBrains). 370 words, ~904 tokens.

Download SKILL.mdSave it as .claude/skills/notion-spec-to-implementation/SKILL.md (or your agent's skills folder). This skill also uses 18 other files; get the full folder from GitHub.
name
notion-spec-to-implementation
description
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
metadata.short-description
Turn Notion specs into implementation plans, tasks, and progress tracking
metadata.author
OpenAI
metadata.source
https://github.com/openai/skills/tree/main/skills/.curated/notion-spec-to-implementation

Spec to Implementation

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

Quick start

  1. Locate the spec with Notion:notion-search, then fetch it with Notion:notion-fetch.
  2. Parse requirements and ambiguities using reference/spec-parsing.md.
  3. Create a plan page with Notion:notion-create-pages (pick a template: quick vs. full).
  4. Find the task database, confirm schema, then create tasks with Notion:notion-create-pages.
  5. 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:
  1. Add the Notion MCP:
    • codex mcp add notion --url https://mcp.notion.com/mcp
  2. Enable remote MCP client:
    • Set [features].rmcp_client = true in config.toml or run codex --enable rmcp_client
  3. 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.

1) Locate and read the spec
  • Search first (Notion:notion-search); if multiple hits, ask the user which to use.
  • Fetch the page (Notion:notion-fetch) and scan for requirements, acceptance criteria, constraints, and priorities. See reference/spec-parsing.md for extraction patterns.
  • Capture gaps/assumptions in a clarifications block before proceeding.
2) Choose plan depth
  • Simple change → use reference/quick-implementation-plan.md.
  • Multi-phase feature/migration → use reference/standard-implementation-plan.md.
  • Create the plan via Notion:notion-create-pages, include: overview, linked spec, requirements summary, phases, dependencies/risks, and success criteria. Link back to the spec.
Show full SKILL.md (140 more words)Show less
3) Create tasks
  • Find the task database (Notion:notion-search → Notion:notion-fetch to confirm the data source and required properties). Patterns in reference/task-creation.md.
  • Size tasks to 1–2 days. Use reference/task-creation-template.md for content (context, objective, acceptance criteria, dependencies, resources).
  • Set properties: title/action verb, status, priority, relations to spec + plan, due date/story points/assignee if provided.
  • Create pages with Notion:notion-create-pages using the database’s data_source_id.
  • Plan links to spec; tasks link to both plan and spec.
  • Optionally update the spec with a short “Implementation” section pointing to the plan and tasks using Notion:notion-update-page.
5) Track progress
  • Use the cadence in reference/progress-tracking.md.
  • Post updates with reference/progress-update-template.md; close phases with reference/milestone-summary-template.md.
  • Keep checklists and status fields in plan/tasks in sync; note blockers and decisions.

References and examples

  • reference/ — parsing patterns, plan/task templates, progress cadence (e.g., spec-parsing.md, standard-implementation-plan.md, task-creation.md, progress-tracking.md).
  • examples/ — end-to-end walkthroughs (e.g., ui-component.md, api-feature.md, database-migration.md).

© JetBrains, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 18 other files (assets) in notion-spec-to-implementation of JetBrains/skills.

  • SKILL.md
  • LICENSE.txt
  • agents/openai.yaml
  • assets/notion-small.svg
  • assets/notion.png
  • evaluations/README.md
  • evaluations/basic-spec-implementation.json
  • evaluations/spec-to-tasks.json
  • examples/api-feature.md
  • examples/database-migration.md
  • examples/ui-component.md
  • reference/milestone-summary-template.md
  • reference/progress-tracking.md
  • reference/progress-update-template.md
  • reference/quick-implementation-plan.md
  • reference/spec-parsing.md
  • … and 3 more

Open the folder on GitHubat commit e0f258b

Used in 5 other repositories

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in JetBrains/skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Notion Spec To Implementation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Notion Spec To Implementation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Notion Spec To Implementation this skillJetBrains/skills3665 repos~904Automated safety check: PassMIT
Discoveranombyte93/prd-taskmaster605—~2.4kAutomated safety check: PassMIT
Handoffanombyte93/prd-taskmaster605—~5kAutomated safety check: PassMIT
Upload Artifactclosedloop-ai/claude-plugins122—~1.4kAutomated safety check: NotesApache-2.0
Speckdlbs/kandev912—~2.1kAutomated safety check: PassAGPL-3.0
Integration Orchestratorrampstackco/claude-skills945—~5.3kAutomated safety check: PassMIT

Similar skills

  • Discover

    anombyte93/prd-taskmaster

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery.

    605 GitHub stars~2.4k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Handoff

    anombyte93/prd-taskmaster

    Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff.

    605 GitHub stars~5k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Upload Artifact

    closedloop-ai/claude-plugins

    Upload a file as a ClosedLoop document (PRD, implementation plan, feature, or template).

    122 GitHub stars~1.4k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • Spec

    kdlbs/kandev

    Create or update Kandev product requirements and system-design documents before implementation.

    912 GitHub stars~2.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Integration Orchestrator

    rampstackco/claude-skills

    Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's…

    945 GitHub stars~5.3k tokensUpdated 3 days ago
    Agent WorkflowsAuto-check passed
  • Codex with ChatGPT Planning Loop

    XiaoDuoYa/codex-with-chatgpt

    Uses ChatGPT in the browser as the planning and review brain for a Codex session, with Codex keeping all execution and ChatGPT reading the workspace through a bridge.

    7.2k GitHub stars~11k tokensUpdated 9 days ago
    Agent WorkflowsAuto-check: notes

More from JetBrains/skills

All 76 skills in this repo
  • Playwright

    JetBrains/skills

    Official

    A skill your agent uses when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli…

    366 GitHub starsUsed in 11 repos~986 tokens
    Auto-check passed
  • Skill Creator

    JetBrains/skills

    Official

    Guide for creating effective skills. An agent skill from JetBrains/skills.

    366 GitHub starsUsed in 122 repos~4.7k tokens
    Auto-check passed
  • Transcribe

    JetBrains/skills

    Official

    Transcribe audio files to text with optional diarization and known-speaker hints.

    366 GitHub starsUsed in 4 repos~776 tokens
    Auto-check passed
  • Imagegen

    JetBrains/skills

    Official

    A skill your agent uses when the user asks to generate or edit images via the OpenAI Image API (for example: generate image, edit/inpaint/mask, background removal or replacement, transparent…

    366 GitHub starsUsed in 3 repos~2.5k tokens
    Auto-check passed
  • Speech

    JetBrains/skills

    Official

    A skill your agent uses when the user asks for text-to-speech narration or voiceover, accessibility reads, audio prompts, or batch speech generation via the OpenAI Audio API; run the bundled CLI…

    366 GitHub starsUsed in 3 repos~1.9k tokens
    Auto-check passed
  • Screenshot

    JetBrains/skills

    Official

    A skill your agent uses when the user explicitly asks for a desktop or system screenshot (full screen, specific app or window, or a pixel region), or when tool-specific capture capabilities are…

    366 GitHub starsUsed in 6 repos~2k tokens
    Auto-check passed

Questions about Notion Spec To Implementation

What does Notion Spec To Implementation do?

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them. Notion Spec To Implementation is an agent skill from JetBrains/skills, published by the product's own GitHub organization. Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

When should I use Notion Spec To Implementation?

Notion Spec To Implementation fits situations like: implementing PRDs/feature specs and creating Notion plans + tasks from them; tasks that involve PRD writing; tasks that involve Planning.

How do I install Notion Spec To Implementation in Claude Code?

Run `npx skills add JetBrains/skills --skill notion-spec-to-implementation -a claude-code`. Or copy the skill folder (notion-spec-to-implementation in JetBrains/skills) into .claude/skills/notion-spec-to-implementation in your project. Claude Code loads it when a task matches its description.

How do I install Notion Spec To Implementation in Codex?

Run `npx skills add JetBrains/skills --skill notion-spec-to-implementation -a codex`. Or copy the skill folder (notion-spec-to-implementation in JetBrains/skills) into .agents/skills/notion-spec-to-implementation in your project. Codex loads it when a task matches its description.

Can I use Notion Spec To Implementation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JetBrains/skills --skill notion-spec-to-implementation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/notion-spec-to-implementation, .gemini/skills/notion-spec-to-implementation, .github/skills/notion-spec-to-implementation and .opencode/skills/notion-spec-to-implementation in your project.

What does Notion Spec To Implementation need to run?

Going by SKILL.md and its folder, Notion Spec To Implementation needs the command-line tools its instructions call (codex).

Does Notion Spec To Implementation access the network?

SKILL.md names 1 domain. In commands or code: mcp.notion.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Notion Spec To Implementation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Notion Spec To Implementation use?

Notion Spec To Implementation is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Notion Spec To Implementation use?

About 904 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Notion Spec To Implementation?

Skills that share tags, products or a category with Notion Spec To Implementation: Discover (anombyte93/prd-taskmaster, 605 stars), Handoff (anombyte93/prd-taskmaster, 605 stars), Upload Artifact (closedloop-ai/claude-plugins, 122 stars) and Spec (kdlbs/kandev, 912 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Notion Spec To Implementation?

JetBrains (a GitHub organization, an official publisher) maintains it in JetBrains/skills, which has 366 GitHub stars. The repository holds 76 skills in this directory. The repository was last updated on June 29, 2026.

Source: JetBrains/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.