notion-spec-to-implementation

name	notion-spec-to-implementation
description	用于把 Notion 规格转成计划、任务和进度跟踪。
zh_description	用于将 Notion 规格文档转化为可执行实现计划。
version	1.0.0
author	seaworld008
source	in-house
source_url
tags	["implementation", "notion", "spec"]
created_at	2026-03-04
updated_at	2026-03-20
quality	3
complexity	intermediate
metadata	null
short-description	Turn Notion specs into implementation plans, tasks, and progress tracking

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.