DoAny
Sign Up
N

notion-spec-to-implementation

Verified

by davila7 · Updated Apr 16, 2026

claude-opus-4-6
25.2Kin8.7Kout
$1.2619m 15s

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

notionproject-planningspecstask-managementimplementationprogress-tracking

See It In Action

1 turns·claude
can you turn the self-serve referral flow spec in notion into a linked implementation plan before launch review, add the tasks + flag any ambiguities first

Done — the implementation plan is live in Notion as a child of the spec.

Seeded input (Notion spec):

Generated output:

15 task subpages (3 phases, ~4 days total)

Phase 1 — Backend (2 days):

  1. Create referral_codes table schema + migration
  2. Build referral code generation API endpoint
  3. Add referred_by field to users table + migration
  4. Implement attribution tracking in sign-up flow
  5. Build reward grant service (credit ledger integration)
  6. Add fraud prevention: email blocklist + rate limiter

Phase 2 — Frontend (1.5 days): 7. Create Invite Friends page in Account Settings 8. Build referral code display + copy-to-clipboard component 9. Implement email share modal (pre-filled template) 10. Create /join/[CODE] landing page with attribution capture 11. Wire analytics events (4 events per spec)

Phase 3 — Launch prep (0.5 days): 12. Add feature flag (referral_program_enabled) 13. Run QA test plan (happy path + fraud scenarios) 14. Verify analytics dashboard + alerting 15. Document runbook (rollback, fraud response)

Blockers flagged at top of plan

  1. Qualifying event for reward — sign-up vs. first paid action. Needs Legal/Finance.
  2. Reward amount/form — assumed $10 credit on email verification as MVP default; needs confirmation.

Default assumptions (called out in clarifications section)

  • Web-only launch (mobile parity deferred)
  • P0 share surfaces: copy link + email (SMS/WhatsApp deferred)
  • Reward granted on email verification; fraud controls: email-domain blocklist + rate limit

The spec page was also updated with an Implementation section linking back to the plan.

Claude Sonnet 4.6

External Tools

ToolType
notionmcp

Permissions

ScopeDescription
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 response.

What does notion-spec-to-implementation output?

In the evaluated run it produced text response.

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

npx skills add https://github.com/davila7/claude-code-templates --skill notion-spec-to-implementation

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

Claude Code

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

It uses notion; channels commonly include text; permissions include 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 team keeps PRDs or feature specs in Notion and wants implementation plans generated directly from them. When you need to create linked execution artifacts such as plans, tasks, and progress updates in an existing Notion workspace. When tracking delivery status in Notion alongside the original spec is part of the workflow.

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

When the source spec and project tracking are not stored in Notion. When you only need a local or one-off implementation summary without creating or updating artifacts in an external workspace.

What it produces

Produces text response.

Install

npx skills add https://github.com/davila7/claude-code-templates --skill notion-spec-to-implementation

Invoke: Ask Claude Code to use notion-spec-to-implementation for the task.