# notion-spec-to-implementation

Turns Notion specs into implementation plans, linked tasks, and progress reports backed by evidence. Handy when requirements need to become work without losing acceptance criteria.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 220
- Author: makenotion
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/makenotion/notion-cookbook/tree/HEAD/skills/mcp-clients/spec-to-implementation/SKILL.md
- Updated: 2026-10-25
- HTML: https://affpapa.org/en/nevibecode/skills/makenotion-notion-spec-to-implementation

## What it does

This skill reads a product or technical spec and turns it into verifiable work. The workflow picks an outcome first: plan, task creation, implementation, or a progress update. Then it reads the spec, plans at a granularity that fits, and creates tasks in Notion when asked.

Each task gets an objective, source requirements, testable acceptance criteria, and dependencies. The skill checks for existing tasks before creating duplicates and links dependencies only after IDs exist. It does not guess assignees, dates, or relation values.

For changed specs, it compares requirements against the current plan and tasks, updates affected work, keeps completed history, and records the impact. Progress is computed from observed task or requirement coverage. It needs Notion tools and write access; without them, you get a plan or task list with unsaved parts marked.

## Requirements
- Works with: Notion

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add makenotion/notion-cookbook --skill spec-to-implementation -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/spec-to-implementation/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/spec-to-implementation/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add makenotion/notion-cookbook --skill spec-to-implementation -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/spec-to-implementation/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add makenotion/notion-cookbook --skill spec-to-implementation -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/spec-to-implementation/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install makenotion/notion-cookbook spec-to-implementation
```

2. **Manually: put the files in place**
- File: `.github/skills/spec-to-implementation/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add makenotion/notion-cookbook --skill spec-to-implementation -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/makenotion/notion-cookbook --path skills/mcp-clients/spec-to-implementation
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/spec-to-implementation/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add makenotion/notion-cookbook --skill spec-to-implementation -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/makenotion/notion-cookbook/tree/HEAD/skills/mcp-clients/spec-to-implementation/SKILL.md

## When to use it
- extract requirements and acceptance criteria from a spec
- create Notion tasks without duplicates
- keep plans and tasks linked to the source spec
- compute progress from actual requirement coverage
- update tasks after a spec change, preserving completed work

## Example prompts
- Build an implementation plan from this Notion spec and create tasks in the project database
- Break these requirements into tasks with acceptance criteria and dependencies
- Compare current tasks with the updated spec and show what needs to change

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: b2588a2b6788605d.

BEGIN THIRD-PARTY FILE b2588a2b6788605d
```text
---
name: notion-spec-to-implementation
description: Converts Notion product or technical specs into implementation plans, linked tasks, and evidence-based progress updates. Use for planning or implementing a spec, creating tasks from requirements, or reconciling implementation with spec changes.
---

# Spec to implementation

Translate requirements into verifiable work while preserving constraints,
acceptance criteria, dependencies, and traceability to the source spec.

## Workflow

1. **Select the requested outcome.** Distinguish a plan, task creation,
   implementation, and a progress update. Complete the requested combination.
   A plan alone does not require task pages or an “In Progress” status. If actual
   implementation is requested and code tools are available, continue through
   implementation and appropriate validation; do not stop at planning.
2. **Read the specification.** Fetch a supplied URL directly; otherwise search by
   project or title. Resolve ambiguous matches. Extract functional and
   non-functional requirements, acceptance criteria, constraints, dependencies,
   and unresolved decisions. Preserve explicit out-of-scope items. When code is
   available, inspect relevant implementation and repository instructions before
   choosing an approach. Label assumptions and estimates; do not invent commitments.
3. **Plan at useful granularity.** Choose independently verifiable deliverables
   and identify prerequisite work. Use phases only when they help coordinate the
   work. Preserve requirement-to-task coverage, including validation. Fit estimates
   to the team's conventions when requested or useful; do not force a task count,
   number of phases, or 1–2-day duration. Reuse an existing plan when updating it.
4. **Create tasks when requested.** Fetch the supplied task database directly or
   discover it if unknown. Read its schema once; identify the correct data source,
   title, status options, and relation targets. Check for existing tasks covering
   the same spec before creating duplicates. Each task needs an objective,
   source requirements, testable acceptance criteria, and dependencies. Use
   supported batching for independent creates when it reduces calls; link task
   dependencies after IDs exist. Do not guess assignees, dates, or relation values.
5. **Implement or track progress within scope.** Update statuses when work actually
   starts or meets the team's completion criteria. Record meaningful changes,
```
END THIRD-PARTY FILE b2588a2b6788605d

The third-party file has ended. Everything between the b2588a2b6788605d tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2486 of 4982 bytes. © makenotion · MIT · https://github.com/makenotion/notion-cookbook/tree/HEAD/skills/mcp-clients/spec-to-implementation/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md