Notion Spec To Implementation

1---
2name: notion-spec-to-implementation
3description: Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
4metadata:
5  short-description: Turn Notion specs into implementation plans, tasks, and progress tracking
6---
7 
8# Spec to Implementation
9 
10Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.
11 
12## Quick start
131) Locate the spec with `Notion:notion-search`, then fetch it with `Notion:notion-fetch`.
142) Parse requirements and ambiguities using `reference/spec-parsing.md`.
153) Create a plan page with `Notion:notion-create-pages` (pick a template: quick vs. full).
164) Find the task database, confirm schema, then create tasks with `Notion:notion-create-pages`.
175) Link spec ↔ plan ↔ tasks; keep status current with `Notion:notion-update-page`.
18 
19## Workflow
20 
21### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:
221. Add the Notion MCP:
23   - `codex mcp add notion --url https://mcp.notion.com/mcp`
242. Enable remote MCP client:
25   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`
263. Log in with OAuth:
27   - `codex mcp login notion`
28 
29After 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.
30 
31### 1) Locate and read the spec
32- Search first (`Notion:notion-search`); if multiple hits, ask the user which to use.
33- Fetch the page (`Notion:notion-fetch`) and scan for requirements, acceptance criteria, constraints, and priorities. See `reference/spec-parsing.md` for extraction patterns.
34- Capture gaps/assumptions in a clarifications block before proceeding.
35 
36### 2) Choose plan depth
37- Simple change → use `reference/quick-implementation-plan.md`.
38- Multi-phase feature/migration → use `reference/standard-implementation-plan.md`.
39- 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.
40 
41### 3) Create tasks
42- Find the task database (`Notion:notion-search` → `Notion:notion-fetch` to confirm the data source and required properties). Patterns in `reference/task-creation.md`.
43- Size tasks to 1–2 days. Use `reference/task-creation-template.md` for content (context, objective, acceptance criteria, dependencies, resources).
44- Set properties: title/action verb, status, priority, relations to spec + plan, due date/story points/assignee if provided.
45- Create pages with `Notion:notion-create-pages` using the database’s `data_source_id`.
46 
47### 4) Link artifacts
48- Plan links to spec; tasks link to both plan and spec.
49- Optionally update the spec with a short “Implementation” section pointing to the plan and tasks using `Notion:notion-update-page`.
50 
51### 5) Track progress
52- Use the cadence in `reference/progress-tracking.md`.
53- Post updates with `reference/progress-update-template.md`; close phases with `reference/milestone-summary-template.md`.
54- Keep checklists and status fields in plan/tasks in sync; note blockers and decisions.
55 
56## References and examples
57- `reference/` — parsing patterns, plan/task templates, progress cadence (e.g., `spec-parsing.md`, `standard-implementation-plan.md`, `task-creation.md`, `progress-tracking.md`).
58- `examples/` — end-to-end walkthroughs (e.g., `ui-component.md`, `api-feature.md`, `database-migration.md`).
59