# spec-to-implementation

Turns a Notion spec page into an implementation plan with phases, tasks and acceptance criteria, then keeps statuses current as work moves.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 38
- Author: makenotion
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/makenotion/cursor-notion-plugin/tree/HEAD/skills/spec-to-implementation/SKILL.md
- Updated: 2026-02-07
- HTML: https://affpapa.org/en/nevibecode/skills/spec-to-implementation

## What it does

Point the skill at a specification and it does the breakdown. It searches Notion by title or topic, reads the page in full, then pulls out functional and non-functional requirements, acceptance criteria, dependencies and blockers. Ambiguous or empty search results send it back to you for a URL or page ID.

What comes out is an implementation plan page titled “Implementation Plan: [Feature Name]”: overview, a link to the source spec, technical approach, phases, effort estimates, risks and success criteria. The skill also locates your task database, reads its schema, and files each task there with Status set to To Do, a priority and related-task links; the detail lives in the task body. It suggests splitting work by component, by vertical slice, or by P0–P2 priority, and keeping each task to a day or two of work.

None of this runs without live Notion access, since both finding the spec and writing tasks depend on it. Progress updates come from what you tell it — status changes, notes on current focus, blockers, links to PRs and designs. A contradictory spec won't stop the breakdown either: conflicts land in the plan as separate items, with a decision task proposed for each.

## Requirements
- Works with: Notion

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add makenotion/cursor-notion-plugin --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/cursor-notion-plugin --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/cursor-notion-plugin --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/cursor-notion-plugin 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/cursor-notion-plugin --skill spec-to-implementation -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/makenotion/cursor-notion-plugin --path skills/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/cursor-notion-plugin --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/cursor-notion-plugin/tree/HEAD/skills/spec-to-implementation/SKILL.md

## When to use it
- break a spec page into phases and concrete tasks
- file tasks into a Notion database with statuses and priorities
- pull acceptance criteria out of a feature description
- flag dependencies and blockers before work starts
- keep progress and PR links updated during implementation

## Example prompts
- Find the “User Authentication” spec in Notion and build an implementation plan with tasks
- Break the payments spec into tasks in the Tasks database and set priorities
- Update task statuses from the plan and mark what's done

## Similar
- [notion-spec-to-implementation](https://affpapa.org/en/nevibecode/skills/notion-spec-to-implementation-2.md) — skill · 358 installs
- [spec](https://affpapa.org/en/nevibecode/skills/spec.md) — skill · 4100 installs
- [4-spec](https://affpapa.org/en/nevibecode/skills/4-spec.md) — skill · 1800 installs
- [notion](https://affpapa.org/en/nevibecode/plugins/notion-notion.md) — plugin · ★ 7604
- [notion-meeting-intelligence](https://affpapa.org/en/nevibecode/skills/openai-notion-meeting-intelligence.md) — skill · 3100 installs
- [notion-mcp](https://affpapa.org/en/nevibecode/skills/notion-mcp.md) — skill · 735 installs

From the same set: [makenotion/cursor-notion-plugin](https://affpapa.org/en/nevibecode/by/makenotion/cursor-notion-plugin.md) — 4 cards

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