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.
- License 许可
- MIT
- 最近更新
- 2026-09-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- notion-spec-to-implementation
- metadata
- { "short-description": "Turn Notion specs into implementation plans, tasks, and progress tracking" }
- description
- Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
02 资源文件 18
- 参考文档agents/openai.yaml339 B
- 资产文件assets/notion-small.svg1.5 KB
- 资产文件assets/notion.png8.3 KB
- 参考文档evaluations/basic-spec-implementation.json2.3 KB
- 参考文档evaluations/README.md4.3 KB
- 参考文档evaluations/spec-to-tasks.json2.4 KB
- 参考文档examples/api-feature.md13.7 KB
- 参考文档examples/database-migration.md2.6 KB
- 参考文档examples/ui-component.md2.1 KB
- 许可证LICENSE.txt1.0 KB
- 参考文档reference/milestone-summary-template.md455 B
- 参考文档reference/progress-tracking.md8.8 KB
- 参考文档reference/progress-update-template.md419 B
- 参考文档reference/quick-implementation-plan.md479 B
- 参考文档reference/spec-parsing.md6.9 KB
- 参考文档reference/standard-implementation-plan.md3.2 KB
- 参考文档reference/task-creation-template.md596 B
- 参考文档reference/task-creation.md7.8 KB
03 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:search, then fetch it withNotion: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; useNotion:searchandNotion:fetchwhere sufficient. - Use one literal search query per
Notion:searchcall and includefilters: {}when no narrower filter is needed. Run separate searches for alternate phrasings instead of puttingorin 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
parentandpagesfields. For task databases, fetch first and use the returnedcollection://...data source ID. - To append an implementation section to a spec, fetch the current section text first, then use
Notion:notion-update-pagewithcommand: "update_content",properties: {}, and exactold_str/new_strcontent. For property-only edits, usecommand: "update_properties"withcontent_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. Seereference/spec-parsing.mdfor 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:fetchto confirm the data source and required properties). Patterns inreference/task-creation.md. - Size tasks to 1–2 days. Use
reference/task-creation-template.mdfor 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-pagesusing the database’sdata_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 withreference/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).
04 同仓库更多 Skills
skill-installer
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
skill-creator
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
review-agent
Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.
plugin-creator
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.
openai-docs
Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.