SkillRepo
Sign InSign Up
Catalog
openai/notion-spec-to-implementation

openai

notion-spec-to-implementation

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

global
short-description:Turn Notion specs into implementation plans, tasks, and progress tracking
0installs0uses—~834
v1.0Saved Apr 5, 2026

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.

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.

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).
Files18
18 files · 80.2 KB

Select a file to preview

Overall Score

82/100

Grade

B

Good

Safety

85

Quality

88

Clarity

84

Completeness

78

Summary

This skill guides AI agents to convert Notion specification documents into structured implementation plans, tasks, and progress tracking within Notion itself. It uses the Notion MCP to search for specs, parse requirements, create multi-phase implementation plans, break work into sized tasks, and maintain progress updates—enabling coordinated feature development from spec to delivery.

Detected Capabilities

Search Notion for specification pages using full-text searchFetch and parse Notion page content to extract requirementsCreate new Notion pages in specific databases using data_source_idUpdate existing Notion pages with new content and linksParse structured requirements (functional, non-functional, acceptance criteria)Generate implementation plans with phases, timelines, and deliverablesCreate task breakdowns with dependencies and sequencingLink artifacts bidirectionally (spec ↔ plan ↔ tasks) using mention-page tagsTrack progress with status updates, blockers, and milestone summariesHandle MCP client setup and OAuth login for Notion integration

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

spec to implementationcreate implementation planbreak down specificationtask database creationfeature planninglink spec tasksprogress trackingimplementation phases

Risk Signals

INFO

Notion MCP dependency requires external service setup and OAuth login

SKILL.md section 0, agents/openai.yaml dependencies
INFO

Skill references multiple external URLs (mcp.notion.com) for MCP installation

SKILL.md section 0, agents/openai.yaml
WARNING

No validation or sanitization documented for user-provided spec URLs or database IDs

SKILL.md steps 1, 3, 5
WARNING

Skill relies on correct data_source_id extraction from Notion API responses without error handling guidance

SKILL.md step 3, reference/task-creation.md
WARNING

No documented handling for rate limiting or Notion API failures during bulk task creation

examples/api-feature.md bulk task section

Referenced Domains

External domains referenced in skill content, detected by static analysis.

mcp.notion.com

Use Cases

  • Turn PRD or feature spec into implementation plan with phases and milestones
  • Break down technical specification into actionable tasks in a task database
  • Create linked implementation artifacts (spec → plan → tasks) for team coordination
  • Track implementation progress and update plan/tasks as work advances
  • Plan database migrations or API redesigns with detailed task sequencing
  • Manage multi-phase features with dependencies and risk tracking

Quality Notes

  • Excellent documentation: skill provides five detailed reference templates (spec-parsing, quick-plan, standard-plan, task-creation, progress-tracking) covering the entire workflow
  • Strong pedagogical approach: three complete end-to-end examples (UI component, API feature, database migration) demonstrate real-world usage patterns and expected outputs
  • Well-structured workflow: five-step process is clear and actionable, with each step having specific tool calls and expected outcomes
  • Good error handling guidance: Section 0 explicitly addresses MCP setup failures and provides recovery steps including OAuth login and codex restart
  • Comprehensive evaluation framework: evaluations/ folder contains test scenarios with specific success criteria, making skill quality measurable
  • Reference materials are well-organized: task naming conventions, granularity guidelines, and sequencing patterns guide agents toward quality task design
  • Scope is clearly bounded: skill focuses specifically on Notion-based planning, not code execution or deployment
  • Minor gap: No documented guidance for handling API rate limits or retry logic when creating many tasks in bulk
  • Minor gap: No explicit error handling or fallback patterns documented if task database schema is not as expected
  • Excellent use of templates: markdown templates for plans and tasks are copy-paste ready and include placeholder guidance
Model: claude-haiku-4-5-20251001Analyzed: Apr 5, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Add openai/notion-spec-to-implementation to your library

Get Started Free

Command Palette

Search for a command to run...