Discover
anombyte93/prd-taskmaster
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery.
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
$ npx skills add JetBrains/skills --skill notion-spec-to-implementation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JetBrains/skills notion-spec-to-implementation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "notion-spec-to-implementation" agent skill from https://github.com/JetBrains/skills/tree/main/notion-spec-to-implementation into .claude/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JetBrains/skills/tree/main/notion-spec-to-implementationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JetBrains/skills --skill notion-spec-to-implementation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JetBrains/skills notion-spec-to-implementation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/notion-spec-to-implementation .agents/skills/notion-spec-to-implementation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "notion-spec-to-implementation" agent skill from https://github.com/JetBrains/skills/tree/main/notion-spec-to-implementation into .agents/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JetBrains/skills --skill notion-spec-to-implementation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JetBrains/skills notion-spec-to-implementation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/notion-spec-to-implementation .cursor/skills/notion-spec-to-implementation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "notion-spec-to-implementation" agent skill from https://github.com/JetBrains/skills/tree/main/notion-spec-to-implementation into .cursor/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JetBrains/skills.git --path notion-spec-to-implementation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JetBrains/skills --skill notion-spec-to-implementation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JetBrains/skills notion-spec-to-implementation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/notion-spec-to-implementation .gemini/skills/notion-spec-to-implementation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "notion-spec-to-implementation" agent skill from https://github.com/JetBrains/skills/tree/main/notion-spec-to-implementation into .gemini/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JetBrains/skills notion-spec-to-implementationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JetBrains/skills --skill notion-spec-to-implementation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/notion-spec-to-implementation .github/skills/notion-spec-to-implementation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "notion-spec-to-implementation" agent skill from https://github.com/JetBrains/skills/tree/main/notion-spec-to-implementation into .github/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JetBrains/skills --skill notion-spec-to-implementation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JetBrains/skills notion-spec-to-implementation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JetBrains/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/notion-spec-to-implementation .opencode/skills/notion-spec-to-implementation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "notion-spec-to-implementation" agent skill from https://github.com/JetBrains/skills/tree/main/notion-spec-to-implementation into .opencode/skills/notion-spec-to-implementation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-spec-to-implementation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
notion-spec-to-implementationTurn 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.
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.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e0f258b. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
codexFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
mcp.notion.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from JetBrains/skills at commit e0f258b, republished under its MIT licence (© JetBrains). 370 words, ~904 tokens.
.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.Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.
Notion:notion-search, then fetch it with Notion:notion-fetch.reference/spec-parsing.md.Notion:notion-create-pages (pick a template: quick vs. full).Notion:notion-create-pages.Notion:notion-update-page.codex mcp add notion --url https://mcp.notion.com/mcp[features].rmcp_client = true in config.toml or run codex --enable rmcp_clientcodex mcp login notionAfter 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.
Notion:notion-search); if multiple hits, ask the user which to use.Notion:notion-fetch) and scan for requirements, acceptance criteria, constraints, and priorities. See reference/spec-parsing.md for extraction patterns.reference/quick-implementation-plan.md.reference/standard-implementation-plan.md.Notion:notion-create-pages, include: overview, linked spec, requirements summary, phases, dependencies/risks, and success criteria. Link back to the spec.Notion:notion-search → Notion:notion-fetch to confirm the data source and required properties). Patterns in reference/task-creation.md.reference/task-creation-template.md for content (context, objective, acceptance criteria, dependencies, resources).Notion:notion-create-pages using the database’s data_source_id.Notion:notion-update-page.reference/progress-tracking.md.reference/progress-update-template.md; close phases with reference/milestone-summary-template.md.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
SKILL.md and 18 other files (assets) in notion-spec-to-implementation of JetBrains/skills.
Open the folder on GitHubat commit e0f258b
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Notion Spec To Implementation this skillJetBrains/skills | 366 | 5 repos | ~904 | Automated safety check: Pass | MIT | |
| Discoveranombyte93/prd-taskmaster | 605 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Handoffanombyte93/prd-taskmaster | 605 | — | ~5k | Automated safety check: Pass | MIT | |
| Upload Artifactclosedloop-ai/claude-plugins | 122 | — | ~1.4k | Automated safety check: Notes | Apache-2.0 | |
| Speckdlbs/kandev | 912 | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Integration Orchestratorrampstackco/claude-skills | 945 | — | ~5.3k | Automated safety check: Pass | MIT |
anombyte93/prd-taskmaster
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery.
anombyte93/prd-taskmaster
Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff.
closedloop-ai/claude-plugins
Upload a file as a ClosedLoop document (PRD, implementation plan, feature, or template).
kdlbs/kandev
Create or update Kandev product requirements and system-design documents before implementation.
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…
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.
JetBrains/skills
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…
JetBrains/skills
Guide for creating effective skills. An agent skill from JetBrains/skills.
JetBrains/skills
Transcribe audio files to text with optional diarization and known-speaker hints.
JetBrains/skills
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…
JetBrains/skills
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…
JetBrains/skills
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…
Works with
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.
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.
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.
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.
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.
Going by SKILL.md and its folder, Notion Spec To Implementation needs the command-line tools its instructions call (codex).
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.
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.
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.
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.
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.
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.