notion-spec-to-implementation

notion-spec-to-implementation is a skill for Codex from seaworld008/Commonly-used-high-value-skills. It costs 24 tokens per session (1,266 once invoked), scanned A, original, MIT.

A workflow that turns a Notion product requirements document, or PRD, into an implementation plan, linked engineering tasks, and status updates.

In plain words
What is it for?
Use it to parse a feature specification, create execution plans and tasks, link the related pages, and track progress in Notion.
Why use it?
It connects product requirements to the work needed to deliver them and keeps those records synchronized.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Codex.

Good fit Use it to parse a feature specification, create execution plans and tasks, link the related pages, and track progress in Notion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/seaworld008/commonly-used-high-value-skills/notion-spec-to-implementation
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add seaworld008/Commonly-used-high-value-skills --skill notion-spec-to-implementation
Clone the repo
git clone --depth 1 https://github.com/seaworld008/Commonly-used-high-value-skills

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for notion-spec-to-implementation

README.md
[![agentmods](https://agentmods.dev/badge/skills/seaworld008/commonly-used-high-value-skills/notion-spec-to-implementation/github.svg)](https://agentmods.dev/skills/seaworld008/commonly-used-high-value-skills/notion-spec-to-implementation)
Your own site
<a href="https://agentmods.dev/skills/seaworld008/commonly-used-high-value-skills/notion-spec-to-implementation"><img src="https://agentmods.dev/badge/skills/seaworld008/commonly-used-high-value-skills/notion-spec-to-implementation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for notion-spec-to-implementation

Your own site · 80×15
<a href="https://agentmods.dev/skills/seaworld008/commonly-used-high-value-skills/notion-spec-to-implementation"><img src="https://agentmods.dev/badge/skills/seaworld008/commonly-used-high-value-skills/notion-spec-to-implementation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,266 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.01266
Opus 5 $0.00012 $0.00633
Sonnet 5 $0.00005 $0.00253
Haiku 4.5 $0.00002 $0.00127

Measured 9d ago against content hash 9a98edca0bfa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

notion-spec-to-implementation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

openclaw-skills/notion-spec-to-implementation/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spec to Implementation

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

When to Use

Use this skill when the user wants to:

  • turn a Notion PRD or feature spec into an execution plan
  • create linked implementation tasks from a spec
  • keep spec, plan, and tasks synchronized over time
  • move from product definition to engineering delivery inside Notion

Use a different skill when:

  • the main task is documenting research or summaries → use notion-research-documentation
  • the main task is capturing a meeting or decision artifact → use notion-knowledge-capture

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.

Usage

Typical artifact chain:

spec page
-> implementation plan page
-> task database entries
-> recurring status updates

Default output should include:

  • requirements summary
  • assumptions and open questions
  • phases or milestones
  • concrete tasks with acceptance criteria
  • relations between spec, plan, and task records

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.
  • Separate hard requirements from inferred implementation detail; do not silently invent acceptance criteria.

Read the full file on GitHub · 124 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 124 lines · 24 tokens per session scan A 9a98edca0bfa

Subscribe to this mod's changes

notion-spec-to-implementation is a skill published in the GitHub repository seaworld008/Commonly-used-high-value-skills (70 stars, last pushed 5d ago), licensed MIT. It adds 24 tokens to every session and 1,266 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.