skilld
All skills
openai avatar

/notion-spec-to-implementation

@136d58a official
by openaiopenai/skills28k stars
1,891

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

Ask your Agent

Use this Skill: https://skilld.dev/gh/openai/skills/notion-spec-to-implementation

This session only. Nothing lands on disk.

SKILL.md

≈48 tokens always: the name and description. ≈799 when used: this file. ≈14k more on demand in 15 files.

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

Source: SKILL.md on GitHub

Third-party checks

2 warnings16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill provides templates and workflows to translate Notion specifications into actionable implementation plans and tasks. It includes a few security considerations regarding the ingestion of external data from user-controlled documents, which are standard for automation and parsing workflows.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: MEDIUM · 1 issue

  • Runlayer7mo

    6/17 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at 136d58a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Activeupdated 10 months ago

Capability

Other metadata
metadata
{
  "short-description": "Turn Notion specs into implementation plans, tasks, and progress tracking"
}

Topics

  • notion
  • project-management
  • task-tracking
  • prd
  • implementation-planning
  • workflow
  • notion-mcp

README badge

README badge for openai/skills/notion-spec-to-implementation

What it does

Converts a Notion spec document into a linked implementation plan with tasks and status tracking, using Notion MCP calls to search, fetch, create pages, and update progress. Targets teams using Notion for PRDs and feature specs who want to automate plan generation and task creation from written requirements.

Generated from the current SKILL.md.

Frequently asked

Does this skill work with Notion MCP?
Yes. It requires the Notion MCP to be installed and authenticated via OAuth. If the MCP is not connected, the skill includes setup steps to add it and log in.
Can I use this skill for any kind of spec, or only certain types?
The skill works for any spec stored in Notion. It includes both quick and full implementation plan templates, so you can adapt the depth to simple changes or multi-phase features.
What Notion operations does this skill perform?
It searches and fetches specs, creates plan and task pages, updates pages with links and progress, and manages relations between spec, plan, and task artifacts.
Does this skill automatically generate task acceptance criteria?
No. The skill provides templates and patterns (in reference/task-creation-template.md) to guide task content, but you compose the acceptance criteria based on the spec requirements.

Generated from the current SKILL.md. These answers refresh after source changes.