$ ~/registry/skill/openai-curated-notion-spec-to-implementation

SKILL

notion-spec-to-implementation

Name: notion-spec-to-implementation
Author: OpenAI

将 Notion 规格说明转为实施计划、任务拆解与进度跟踪。

星标

★ 25,304

来源

GitHub

更新于

2026-09-02

// 安全评估需留意

仅提示词，不执行代码
开源可审计
社区验证· 22.0k

总评

该技能本身是开源的 prompt-only 工作流说明，无内置密钥、无自带远程端点，也不直接执行代码，整体风险较低。需注意的是它会引导用户接入 Notion MCP 并对 Notion 工作区执行搜索、读取、创建和更新操作，因此实际数据访问与外发边界取决于所连接的 Notion 权限范围。

凭证密钥需留意

材料声明该技能本身不需要环境变量或 API 密钥；但 README 明确引导用户通过 `codex mcp login notion` 进行 OAuth 登录 Notion MCP，因此会涉及 Notion 账户授权令牌。未见要求收集无关凭证或明示凭证外传，风险主要在于 Notion 授权范围本身。

网络外发需留意

技能自身未声明独立远程端点，但 README 指导添加远程 MCP `https://mcp.notion.com/mcp` 并通过其访问 Notion。按其用途，规范内容、计划、任务和状态更新会传输到 Notion 服务；未发现外发到无关或不明主机的迹象。

代码执行低风险

系统检查项已标明为 prompt-only。文档主要描述工作流与对 Notion MCP 工具的调用顺序，没有提供本地脚本执行、任意命令运行或额外系统能力申请；`codex mcp add/login` 属于连接外部 MCP 的配置指引，而非该技能自身执行代码。

数据访问需留意

该技能意图通过 Notion MCP 执行 `notion-search`、`notion-fetch`、`notion-create-pages` 和 `notion-update-page`，因此会对用户已授权的 Notion 工作区内容进行读取与写入。材料未显示其可访问本地文件系统或超出 Notion 范围的资源，但应关注 OAuth 授权后可见页面、数据库与写权限的实际边界。

来源供应链低风险

来源为 GitHub 上的 openai/skills 开源仓库，且有约 2.2 万 star，具备较强社区可见性和可审计性，这些都是显著的降风险因素。许可证未声明、维护状态未知会带来一定治理信息缺口，但在当前材料下未见闭源投递、可疑分发源或明显供应链红旗。

安全建议

仅在需要时连接 Notion MCP，并在 Notion 侧授予最小必要工作区/页面权限。
在使用前确认该技能将创建或修改哪些 Notion 页面、数据库和关系字段，避免误写生产空间。
优先在测试或隔离的 Notion 空间中试运行，验证搜索、建页和更新行为是否符合预期。
定期审查并撤销不再需要的 Notion OAuth 授权与 MCP 连接。

审计模型: gpt-5.4 · 2026-06-16

// 安装

复制安装指令，让 AI 自动完成配置 · 推荐新手

请帮我安装 askskill 上的 "notion-spec-to-implementation" 技能：
1. 下载 https://raw.githubusercontent.com/openai/skills/main/skills/.curated/notion-spec-to-implementation/SKILL.md
2. 保存为 ~/.claude/skills/notion-spec-to-implementation/SKILL.md
3. 装好后重载技能，告诉我可以用了

// 下载

下载 SKILL.md机读安装清单 ↗

// 文档

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.

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

OpenAI装→

// 功能相似

MCP 工具

notion-autopilot

将 Notion 任务库升级为自动提醒、汇总与批量处理的智能任务系统

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.

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

// 文档

Spec to Implementation

Quick start

Workflow

0) If any MCP call fails because Notion MCP is not connected, pause and set it up:

1) Locate and read the spec

2) Choose plan depth

3) Create tasks

4) Link artifacts

5) Track progress

References and examples

// 同源资产

figma-generate-design

figma

aspnet-core

chatgpt-apps

cli-creator

cloudflare-deploy

// 功能相似

notion-autopilot

notion-knowledge-capture

notion-research-documentation

notion-mcp

review-plan

StoriesOnBoard - structured specifications for AI Agents

// 文档

Spec to Implementation

Quick start

Workflow

0) If any MCP call fails because Notion MCP is not connected, pause and set it up:

1) Locate and read the spec

2) Choose plan depth

3) Create tasks

4) Link artifacts

5) Track progress

References and examples

// 同源资产

figma-generate-design

figma

aspnet-core

chatgpt-apps

cli-creator

cloudflare-deploy

// 功能相似

notion-autopilot

notion-knowledge-capture

notion-research-documentation

notion-mcp

review-plan

StoriesOnBoard - structured specifications for AI Agents