AutoGineer
Generated banner for Notion Spec To Implementation
Generated logo for Notion Spec To Implementation

Notion Spec To Implementation

JetBrainsOfficialCreated by OpenAIDistributed by JetBrains

  • Skill
  • Workflow
  • Business and productivity
  • MIT
  • No issues found
Download ZIP

From the author

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

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a systematic approach to bridging the gap between high-level product requirements and execution. It guides the agent through locating and parsing Notion specifications, generating structured implementation plans, creating granular tasks within a database, and maintaining ongoing progress tracking. By standardizing the translation of PRDs into project management artifacts, it ensures consistency in documentation, task sizing, and status reporting.

What it does

  • Searches and retrieves product specifications from Notion.
  • Parses requirements, constraints, and acceptance criteria from raw specs.
  • Generates structured implementation plans based on project complexity.
  • Creates linked tasks in Notion databases with defined properties and templates.
  • Establishes bidirectional links between specs, plans, and individual tasks.
  • Provides templates for progress updates and milestone summaries.

When to use it

  • When you need to turn a new feature spec into a set of actionable development tasks.
  • When managing complex migrations or multi-phase feature rollouts.
  • When you need to ensure project documentation remains synchronized with task progress.
  • When you need to establish a consistent cadence for tracking project milestones.

Advantages

  • Reduces ambiguity by forcing a structured parsing of requirements.
  • Ensures all implementation artifacts are properly linked for traceability.
  • Standardizes task creation and sizing across different projects.
  • Maintains clear visibility into project status and blockers.

Usage examples

“Create an implementation plan and tasks for the 'User Auth' spec found in Notion.”
The agent searches for the spec, parses the requirements, creates a new implementation plan page, and populates the task database with linked items.
“Update the progress for the current database migration project.”
The agent reviews the linked tasks, updates status fields, and generates a milestone summary based on the progress tracking template.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/jetbrains/notion-spec-to-implementation/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip notion-spec-to-implementation.zip -d .agents/skills

Documentation by OpenAI

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

Files

examples/ui-component.md

Example: UI Component Implementation

User Request: "Implement the new search component from the design spec"

Workflow

1. Find Spec
Notion:notion-search
query: "search component design spec"

Found: "Global Search Redesign Spec"

2. Fetch & Parse Spec
Notion:notion-fetch

Requirements:

  • Instant search with debounced API calls

  • Keyboard navigation (↑↓ arrows, Enter, Esc)

  • Recent searches history

  • Result categories (pages, people, files)

  • Mobile responsive

  • Accessibility (ARIA labels, screen reader)

3. Create Implementation Plan
Notion:notion-create-pages

Plan phases:

  • Phase 1: Base component structure

  • Phase 2: API integration & debouncing

  • Phase 3: Keyboard navigation

  • Phase 4: Recent searches

  • Phase 5: Polish & accessibility

4. Create Tasks
Notion:notion-create-pages (7 tasks)

Tasks:

  1. Create SearchInput component

  2. Implement useDebounce hook

  3. Add keyboard navigation

  4. LocalStorage for recent searches

  5. Result categorization UI

  6. Accessibility audit

  7. Mobile responsive styling

5. Implement & Track

As each task completed, updated status and added progress notes with screenshots and implementation details.

Key Outputs

Implementation Plan (linked to design spec) 7 Component Tasks (in Engineering Tasks database) Progress Updates (with code snippets and demo links)

Success Factors

  • Clear component breakdown

  • Separated concerns (logic, UI, accessibility)

  • Each task had acceptance criteria

  • Referenced design spec throughout

  • Included accessibility from start, not afterthought

  • Tracked progress with visual updates

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
OpenAI
Publisher
JetBrains (Official)
Distributed by
JetBrains
Source
JetBrains/skills · notion-spec-to-implementation · commit 3f53782
Licence
MIT License (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by OpenAI or JetBrains.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download notion-spec-to-implementation.zip