What is notion-spec-to-implementation?

A workflow for turning a Notion product requirements document (PRD) or feature specification into an implementation plan, tasks, and status updates.

It helps find a Notion spec, identify unclear requirements, create linked plan and task pages, and keep their status current.

It connects the original requirements to the work needed to build them, reducing manual planning and progress tracking.

notion-spec-to-implementation — Skill for Codex by Haohao-end

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 Haohao-end/openagent --skill notion-spec-to-implementation

Clone the repo

git clone --depth 1 https://github.com/Haohao-end/openagent

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/haohao-end/openagent/notion-spec-to-implementation/github.svg)](https://agentmods.dev/skills/haohao-end/openagent/notion-spec-to-implementation)

Your own site

<a href="https://agentmods.dev/skills/haohao-end/openagent/notion-spec-to-implementation"><img src="https://agentmods.dev/badge/skills/haohao-end/openagent/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/haohao-end/openagent/notion-spec-to-implementation"><img src="https://agentmods.dev/badge/skills/haohao-end/openagent/notion-spec-to-implementation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 825 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.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.00825
Opus 5	$0.00019	$0.00413
Sonnet 5	$0.00008	$0.00165
Haiku 4.5	$0.00004	$0.00082

Measured 10d ago against content hash 6e22c4c6df44, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

notion-spec-to-implementation — 100% identical, 0 lines differ
notion-spec-to-implementation — 100% identical, 0 lines differ

api/internal/core/skills/catalog/notion-spec-to-implementation/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 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.

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.

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.

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.

Read the full file on GitHub · 59 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

10d ago First seen · 59 lines · 39 tokens per session scan A 6e22c4c6df44

Subscribe to this mod's changes

notion-spec-to-implementation is a skill published in the GitHub repository Haohao-end/openagent (806 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 825 once invoked, about $0.0002 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-08-30.

Planning Project management agent ai celery deepseek docker flask

openspec-archive-change

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

creativedswork/dscode · 31 tokens

github-project-management

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.

amangit1314/repo-rag · 25 tokens

things-mac

Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.

elizaOS/eliza · 67 tokens

sn-team-harness

Use when a user asks what SenseNova Team Harness is, wants an introduction or overview, is getting started, or is deciding whether it fits — a self-hosted workspace where people and local AI agents collaborate on conversations, projects, work items, and artifacts. Covers its core concepts (Workspace, Project…

OpenSenseNova/SenseNova-Skills · 94 tokens

goal

Set and track project goals. Triggered by "/goal" to define objectives, track milestones, or review progress.

x-cmd/x-cmd · 25 tokens

omh-agent-board

This is a Hermes-native agent-board workflow skill.

rlaope/oh-my-hermes · 67 tokens