Notion Spec To Implementation — Agent Skill by OpenAI

From the author

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

— the description by Notion Labs, Inc

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a systematic approach to bridging the gap between high-level product specifications and technical execution. It guides the agent through locating and parsing Notion documents, creating structured implementation plans, generating granular tasks within existing databases, and maintaining ongoing progress tracking. By following defined templates and linking artifacts, it ensures that project requirements remain synchronized with development activities.

What it does

Searches and retrieves product specifications from Notion workspaces.
Parses requirements, constraints, and acceptance criteria from raw spec documents.
Generates structured implementation plans using predefined templates.
Creates linked tasks in Notion databases with appropriate metadata and sizing.
Updates specifications to include links to implementation plans and tasks.
Facilitates ongoing progress tracking and milestone reporting.

When to use it

When you need to translate a new PRD or feature spec into a concrete development plan.
When you need to break down complex features into manageable, sized tasks.
When you want to ensure traceability between product requirements and task execution.
When you need to maintain consistent progress updates for a project in Notion.

Advantages

Reduces manual overhead in project planning and task creation.
Ensures consistent documentation standards across implementation artifacts.
Maintains clear traceability between high-level specs and granular tasks.
Provides a repeatable process for different types of technical projects.

Usage examples

“Find the 'User Authentication' spec in Notion and create an implementation plan for it.”: The agent searches for the spec, parses the requirements, creates a new implementation plan page in Notion, and links it back to the original spec.
“Break down the 'API Rate Limiting' spec into tasks in our engineering database.”: The agent identifies the task database, creates sized tasks with acceptance criteria, and links them to the spec and the implementation plan.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/openai/notion-spec-to-implementation/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip notion-spec-to-implementation.zip -d .agents/skills

Documentation by Notion Labs, Inc

Spec to Implementation

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

Quick start

Locate the spec with Notion:search, then fetch it with 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.

Tool-call guardrails

Notion tool availability can vary by workspace. If a Notion MCP call returns Tool <name> not found, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use Notion:search and Notion:fetch where sufficient.
Use one literal search query per Notion:search call and include filters: {} when no narrower filter is needed. Run separate searches for alternate phrasings instead of putting or in a single query string.
Only send Notion page, database, or data-source URLs/IDs to Notion:fetch; external connected-source search results are not fetch targets.
Create plans and task pages with explicit parent and pages fields. For task databases, fetch first and use the returned collection://... data source ID.
To append an implementation section to a spec, fetch the current section text first, then use Notion:notion-update-page with command: "update_content", properties: {}, and exact old_str / new_str content. For property-only edits, use command: "update_properties" with content_updates: []; the current deployed schema expects both top-level fields even when one is unused.

Workflow

0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:

Enable the bundled Notion app for this plugin or session.
Complete the Notion auth flow if prompted.
Start a new session if the tools still do not appear.

After the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.

1) Locate and read the spec

Search first (Notion:search); if multiple hits, ask the user which to use.
Fetch the page (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:search → 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.

4) Link artifacts

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).

Files

ATTRIBUTION.mdAdded by AutoGineer1.0 KiB
LICENSE.txt1.0 KiB
SKILL.md4.4 KiB
agents/openai.yaml339 B
assets/notion-small.svg1.5 KiB
assets/notion.png8.3 KiB
evaluations/README.md4.3 KiB
evaluations/basic-spec-implementation.json2.3 KiB
evaluations/spec-to-tasks.json2.4 KiB
examples/api-feature.md13.7 KiB
examples/database-migration.md2.6 KiB
examples/ui-component.md2.1 KiB
reference/milestone-summary-template.md455 B
reference/progress-tracking.md8.8 KiB
reference/progress-update-template.md419 B
reference/quick-implementation-plan.md479 B
reference/spec-parsing.md6.9 KiB
reference/standard-implementation-plan.md3.2 KiB
reference/task-creation-template.md596 B
reference/task-creation.md7.8 KiB

evaluations/basic-spec-implementation.json

{
  "name": "Create Implementation Plan from Spec",
  "skills": ["spec-to-implementation"],
  "query": "Create an implementation plan for the User Authentication spec page",
  "expected_behavior": [
    "Step 1: Uses Notion:search to find 'User Authentication spec' with keywords like 'User Authentication' or 'auth spec'",
    "Step 2: If not found or ambiguous, asks user for spec page URL/ID",
    "Step 3: Fetches spec page using Notion:fetch with URL/ID from search results",
    "Step 4: Parses spec using patterns from reference/spec-parsing.md to extract requirements, acceptance criteria, constraints",
    "Step 5: Identifies functional requirements (user stories, features, workflows) and non-functional requirements (performance, security)",
    "Step 6: Creates implementation plan following structure from reference/templates.md",
    "Step 7: Includes sections: Overview, Linked Spec, Requirements Summary, Technical Approach, Implementation Phases",
    "Step 8: Breaks work into logical phases with Goal, Tasks checklist, Estimated effort per phase",
    "Step 9: Identifies dependencies and risks from spec content",
    "Step 10: Links plan back to original spec page using <mention-page url='...'>",
    "Step 11: Creates plan page using Notion:notion-create-pages with appropriate title (e.g., 'Implementation Plan: User Authentication')",
    "Step 12: Places plan appropriately (asks user or suggests under project/spec parent)"
  ],
  "success_criteria": [
    "Spec is found using Notion:search before attempting to fetch (or user is asked for URL if not found)",
    "Spec is fetched using Notion:fetch with correct URL/ID from search results",
    "Plan includes clear overview and spec link with mention-page tag",
    "Requirements are extracted from actual spec content (not generic) using spec-parsing patterns",
    "Work is broken into multiple phases (typically 3-5) following template structure",
    "Each phase has Goal, Tasks (as checkboxes), and Estimated effort",
    "Dependencies and risks sections are included with specific details from spec",
    "Plan follows Implementation Plan structure from reference/templates.md",
    "Success criteria or acceptance criteria from spec are referenced in plan",
    "Uses correct tool names and sequence: Notion:search → Notion:fetch → Notion:notion-create-pages"
  ]
}

Requirements and compatibility

Written for: OpenAI Codex

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Marketing Plan
Corey Haines· Community
Generates a comprehensive, executable 12-month marketing plan structured by the AARRR framework for fractional CMOs and founders.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository59k
Revops
Corey Haines· Community
Expert guidance for designing and optimizing revenue operations, lead lifecycle management, and marketing-to-sales handoff processes.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Ab Testing
Corey Haines· Community
A comprehensive framework for planning, executing, and analyzing statistically rigorous A/B tests and growth experimentation programs.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Pricing
Corey Haines· Community
Expert guidance on SaaS pricing strategy, packaging, monetization, and auditing pricing pages for human and AI-agent readability.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Community Marketing
Corey Haines· Community
A strategic framework for building and managing online communities to drive product growth, brand loyalty, and user engagement.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k
Paywalls
Corey Haines· Community
Expert guidance for designing and optimizing in-app upgrade flows, paywalls, and feature gates to maximize conversion.
Business and productivityClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository59k

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download notion-spec-to-implementation.zip