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

Notion Spec To Implementation

OpenAIOfficialCreated by Notion Labs, IncDistributed by OpenAI

  • 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 Notion Labs, Inc

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 specifications and technical execution. It guides the agent through locating and parsing Notion documents, creating structured implementation plans, generating granular tasks within existing databases, and maintaining ongoing progress tracking. By following defined templates and linking artifacts, it ensures that project requirements remain synchronized with development activities.

What it does

  • Searches and retrieves product specifications from Notion workspaces.
  • Parses requirements, constraints, and acceptance criteria from raw spec documents.
  • Generates structured implementation plans using predefined templates.
  • Creates linked tasks in Notion databases with appropriate metadata and sizing.
  • Updates specifications to include links to implementation plans and tasks.
  • Facilitates ongoing progress tracking and milestone reporting.

When to use it

  • When you need to translate a new PRD or feature spec into a concrete development plan.
  • When you need to break down complex features into manageable, sized tasks.
  • When you want to ensure traceability between product requirements and task execution.
  • When you need to maintain consistent progress updates for a project in Notion.

Advantages

  • Reduces manual overhead in project planning and task creation.
  • Ensures consistent documentation standards across implementation artifacts.
  • Maintains clear traceability between high-level specs and granular tasks.
  • Provides a repeatable process for different types of technical projects.

Usage examples

“Find the 'User Authentication' spec in Notion and create an implementation plan for it.”
The agent searches for the spec, parses the requirements, creates a new implementation plan page in Notion, and links it back to the original spec.
“Break down the 'API Rate Limiting' spec into tasks in our engineering database.”
The agent identifies the task database, creates sized tasks with acceptance criteria, and links them to the spec and the implementation plan.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/openai/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 Notion Labs, Inc

Spec to Implementation

Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.

Quick start

  1. Locate the spec with Notion:search, then fetch it with 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.

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; use Notion:search and Notion:fetch where sufficient.

  • Use one literal search query per Notion:search call and include filters: {} when no narrower filter is needed. Run separate searches for alternate phrasings instead of putting or in 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 parent and pages fields. For task databases, fetch first and use the returned collection://... data source ID.

  • To append an implementation section to a spec, fetch the current section text first, then use Notion:notion-update-page with command: "update_content", properties: {}, and exact old_str / new_str content. For property-only edits, use command: "update_properties" with content_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:

  1. Enable the bundled Notion app for this plugin or session.

  2. Complete the Notion auth flow if prompted.

  3. 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. 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:search → 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

reference/task-creation.md

Task Creation from Specs

Finding the Task Database

Before creating tasks, locate the task database:

1. Search for task database:
   Notion:search
   query: "[Project] Tasks"
   query_type: "internal"
   filters: {}

   If needed, run separate searches for:
   - "Tasks"
   - "Task Management"

2. Fetch database schema:
   Notion:fetch
   id: "database-id-from-search"

3. Identify data source:
   - Look for <data-source url="collection://..."> tags
   - Extract collection ID for parent parameter

4. Note schema:
   - Required properties
   - Property types and options
   - Relation properties for linking

Example:
Notion:search
query: "Engineering Tasks"
query_type: "internal"
filters: {}

Notion:fetch
id: "tasks-database-id"

Result: collection://abc-123-def for use as parent

Task Breakdown Strategy

Size Guidelines

Good task size:

  • Completable in 1-2 days

  • Single clear deliverable

  • Independently testable

  • Minimal dependencies

Too large:

  • Takes > 3 days

  • Multiple deliverables

  • Many dependencies

  • Break down further

Too small:

  • Takes < 2 hours

  • Too granular

  • Group with related work

Granularity by Phase

Early phases: Larger tasks acceptable

  • "Design database schema"

  • "Set up API structure"

Middle phases: Medium-sized tasks

  • "Implement user authentication"

  • "Build dashboard UI"

Late phases: Smaller, precise tasks

  • "Fix validation bug in form"

  • "Add loading state to button"

Task Creation Pattern

For each requirement or work item:

1. Identify the work
2. Determine task size
3. Create task in database
4. Set properties
5. Write task description
6. Link to spec/plan
Creating Task
Notion:notion-create-pages
parent: {
  type: "data_source_id",
  data_source_id: "collection://tasks-db-uuid"
}
pages: [{
  properties: {
    "[Title Property]": "Task: [Clear task name]",
    "Status": "To Do",
    "Priority": "[High/Medium/Low]",
    "[Project/Related]": ["spec-page-id", "plan-page-id"],
    "Assignee": "[Person]",
    "date:Due Date:start": "[Date]",
    "date:Due Date:is_datetime": 0
  },
  content: "[Task description using template]"
}]

Task Description Template

# [Task Name]

## Context
Implementation task for <mention-page url="...">Feature Spec</mention-page>

Part of <mention-page url="...">Implementation Plan</mention-page> - Phase [N]

## Objective
[What this task accomplishes]

## Requirements
Based on spec requirements:
- [Relevant requirement 1]
- [Relevant requirement 2]

## Acceptance Criteria
- [ ] [Specific, testable criterion]
- [ ] [Specific, testable criterion]
- [ ] [Specific, testable criterion]

## Technical Approach
[Suggested implementation approach]

### Components Affected
- [Component 1]
- [Component 2]

### Key Decisions
- [Decision point 1]
- [Decision point 2]

## Dependencies

### Blocked By
- <mention-page url="...">Prerequisite Task</mention-page> or None

### Blocks
- <mention-page url="...">Dependent Task</mention-page> or None

## Resources
- [Link to design mockup]
- [Link to API spec]
- [Link to relevant code]

## Estimated Effort
[Time estimate]

## Progress
[To be updated during implementation]

Task Types

Infrastructure/Setup Tasks
Title: "Setup: [What's being set up]"
Examples:
- "Setup: Configure database connection pool"
- "Setup: Initialize authentication middleware"
- "Setup: Create CI/CD pipeline"

Focus: Getting environment/tooling ready
Feature Implementation Tasks
Title: "Implement: [Feature name]"
Examples:
- "Implement: User login flow"
- "Implement: File upload functionality"
- "Implement: Dashboard widget"

Focus: Building specific functionality
Integration Tasks
Title: "Integrate: [What's being integrated]"
Examples:
- "Integrate: Connect frontend to API"
- "Integrate: Add payment provider"
- "Integrate: Link user profile to dashboard"

Focus: Connecting components
Testing Tasks
Title: "Test: [What's being tested]"
Examples:
- "Test: Write unit tests for auth service"
- "Test: E2E testing for checkout flow"
- "Test: Performance testing for API"

Focus: Validation and quality assurance
Documentation Tasks
Title: "Document: [What's being documented]"
Examples:
- "Document: API endpoints"
- "Document: Setup instructions"
- "Document: Architecture decisions"

Focus: Creating documentation
Bug Fix Tasks
Title: "Fix: [Bug description]"
Examples:
- "Fix: Login error on Safari"
- "Fix: Memory leak in image processing"
- "Fix: Race condition in payment flow"

Focus: Resolving issues
Refactoring Tasks
Title: "Refactor: [What's being refactored]"
Examples:
- "Refactor: Extract auth logic to service"
- "Refactor: Optimize database queries"
- "Refactor: Simplify component hierarchy"

Focus: Code quality improvement

Sequencing Tasks

Critical Path

Identify must-happen-first tasks:

1. Database schema
2. API foundation
3. Core business logic
4. Frontend integration
5. Testing
6. Deployment
Parallel Tracks

Tasks that can happen simultaneously:

Track A: Backend development
- API endpoints
- Business logic
- Database operations

Track B: Frontend development
- UI components
- State management
- Routing

Track C: Infrastructure
- CI/CD setup
- Monitoring
- Documentation
Phase-Based Sequencing

Group by implementation phase:

Phase 1 (Foundation):
- Setup tasks
- Infrastructure tasks

Phase 2 (Core):
- Feature implementation tasks
- Integration tasks

Phase 3 (Polish):
- Testing tasks
- Documentation tasks
- Optimization tasks

Priority Assignment

P0/Critical

  • Blocks everything else

  • Core functionality

  • Security requirements

  • Data integrity

P1/High

  • Important features

  • User-facing functionality

  • Performance requirements

P2/Medium

  • Nice-to-have features

  • Optimizations

  • Minor improvements

P3/Low

  • Future enhancements

  • Edge case handling

  • Cosmetic improvements

Estimation

Story Points

If using story points:

  • 1 point: Few hours

  • 2 points: Half day

  • 3 points: Full day

  • 5 points: 2 days

  • 8 points: 3-4 days (consider breaking down)

Time Estimates

Direct time estimates:

  • 2-4 hours: Small task

  • 1 day: Medium task

  • 2 days: Large task

  • 3+ days: Break down further

Estimation Factors

Consider:

  • Complexity

  • Unknowns

  • Dependencies

  • Testing requirements

  • Documentation needs

Task Relationships

Parent Task Pattern

For large features:

Parent: "Feature: User Authentication"
Children:
- "Setup: Configure auth library"
- "Implement: Login flow"
- "Implement: Password reset"
- "Test: Auth functionality"
Dependency Chain Pattern

For sequential work:

Task A: "Design database schema"
↓ (blocks)
Task B: "Implement data models"
↓ (blocks)
Task C: "Create API endpoints"
↓ (blocks)
Task D: "Integrate with frontend"
Related Tasks Pattern

For parallel work:

Central: "Feature: Dashboard"
Related:
- "Backend API for dashboard data"
- "Frontend dashboard component"
- "Dashboard data caching"

Bulk Task Creation

When creating many tasks:

For each work item in breakdown:
  1. Determine task properties
  2. Create task page
  3. Link to spec/plan
  4. Set relationships

Then:
  1. Update plan with task links
  2. Review sequencing
  3. Assign tasks (if known)

Task Naming Conventions

Be specific: ✓ "Implement user login with email/password" ✗ "Add login"

Include context: ✓ "Dashboard: Add revenue chart widget" ✗ "Add chart"

Use action verbs:

  • Implement, Build, Create

  • Integrate, Connect, Link

  • Fix, Resolve, Debug

  • Test, Validate, Verify

  • Document, Write, Update

  • Refactor, Optimize, Improve

Validation Checklist

Before finalizing tasks:

☐ Each task has clear objective ☐ Acceptance criteria are testable ☐ Dependencies identified ☐ Appropriate size (1-2 days) ☐ Priority assigned ☐ Linked to spec/plan ☐ Proper sequencing ☐ Resources noted

Requirements and compatibility

Written for: OpenAI Codex

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
Notion Labs, Inc
Publisher
OpenAI (Official)
Distributed by
OpenAI
Source
openai/plugins · plugins/notion/skills/notion-spec-to-implementation · commit d420d13
Licence
MIT License (redistribution allowed)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Notion Labs, Inc or OpenAI.

Download ZIP

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