DoAny
Sign Up
N

notion-spec-to-implementation

Verified

by openai · Updated Apr 16, 2026

claude-opus-4-6
4.1Kin5.4Kout
$0.523m 50s

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

notionplanningproject-managementspecstask-tracking

See It In Action

1 turns·claude
The project codebase is in your current working directory. Explore the files to understand the code before making changes. leadership okayed the referral onboarding spec in notion — can you turn it into the eng plan + task it out before sprint planning this afternoon

Got it — I've read through all the reference templates. This is a multi-phase experiment with cross-team touchpoints (analytics, copy, rollout), so I'll use the standard implementation plan template and break tasks down to 1-2 day chunks. Let me generate both artifacts now.

Both files are ready in your working directory:

  • referral-onboarding-implementation-plan.md — the full eng plan using the standard (multi-phase) template, covering attribution → experiment launch → stabilization/ramp, with requirements, risks, rollout strategy, and rollback triggers.
  • referral-onboarding-tasks.md — 7 tasks sized at 1–2 days each (~8.5 eng-days total), with acceptance criteria, dependencies, and estimates ready to drop into the Notion task DB.

A few things to nail down before or at sprint planning:

  • Confirm the attribution data contract with growth/backend — Task 1 blocks everything.
  • Validate that the experiment framework handles the logged-out → logged-in transition cleanly — worth a quick spike early in Phase 1.
  • Get final copy/assets from design queued so it doesn't gate Phase 2.
  • Assign the plan owner and fill in the TBDs in the plan metadata.

The critical path is T1 → T2 → T3 → T5 → T7, with T4 and T6 partially parallelizable. Should be shippable in roughly one sprint plus a ramp tail.

Claude Sonnet 4.6

External Tools

ToolType
notionmcp

Permissions

ScopeDescription
filesystem:read
network:outbound

SKILL.md

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

FAQ

What does notion-spec-to-implementation do?

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

When should I use notion-spec-to-implementation?

Use it when you need a repeatable workflow that produces text report.

What does notion-spec-to-implementation output?

In the evaluated run it produced text report.

How do I install or invoke notion-spec-to-implementation?

Ask the agent to use this skill when the task matches its documented workflow.

Which agents does notion-spec-to-implementation support?

Agent support is inferred from the source, but not explicitly declared.

What tools, channels, or permissions does notion-spec-to-implementation need?

It uses notion; channels commonly include text; permissions include filesystem:read, network:outbound.

Is notion-spec-to-implementation safe to install?

Static analysis marked this skill as medium risk; review side effects and permissions before enabling it.

How is notion-spec-to-implementation different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does notion-spec-to-implementation outperform not using a skill?

About notion-spec-to-implementation

When to use notion-spec-to-implementation

When a feature or PRD already exists in Notion and needs to be broken into an implementation plan and actionable tasks. When you want the agent to create linked planning artifacts and keep execution status updated in Notion. When your team uses Notion as the source of truth for specs, plans, and task tracking.

When notion-spec-to-implementation is not the right choice

When the spec is not stored in Notion or you do not want the agent modifying your Notion workspace. When you only need local analysis of a spec without creating plans, tasks, or status updates.

What it produces

Produces text report.