What kind of spec does it work with?

It works with PRDs and feature specs in Notion.

Does it create tasks in Notion?

Yes, it creates Notion plans and tasks from the spec.

Can it track progress?

Yes, it tracks progress against the implementation plan.

Do I need a Notion workspace?

Yes, the spec and the plan live in Notion.

What if my spec is not in Notion?

The skill is for Notion specs, so it expects the spec to be in Notion.

Spec to Implementation

SkillDocs & knowledge

This is a skill that turns a Notion product spec into an implementation plan. It reads a PRD or feature spec and produces a plan with tasks and progress tracking. Use it when you are moving from a written spec to actual work. The notion claude skill keeps the plan and the spec connected.

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.

Have a Notion workspace with the PRD or feature spec you want to implement.

Then ask your AI: use the Spec to Implementation skill

What your AI can do with it

Read a Notion PRD or feature spec
Create an implementation plan from the spec
Break the plan into tasks
Track progress against the plan

Getting started

Have a Notion workspace with the PRD or feature spec you want to implement.
Add the skill to your agent.
Point the agent at the Notion spec.
Ask the agent to create an implementation plan and tasks.
Use the plan to track progress as you work.

What this skill tells your AI

The instructions your AI receives, as published by davila7/claude-code-templates in cli-tool/components/skills/productivity/notion-spec-to-implementation/SKILL.md and read by ahel’s review.

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

Quick start

Locate the spec with Notion:notion-search, then fetch it with Notion:notion-fetch.
Parse requirements and ambiguities using reference/spec-parsing.md.
Create a plan page with Notion:notion-create-pages (pick a template: quick vs. full).
Find the task database, confirm schema, then create tasks with Notion:notion-create-pages.
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:

Add the Notion MCP:
- codex mcp add notion --url https://mcp.notion.com/mcp
Enable remote MCP client:
- Set [features].rmcp_client = true in config.toml or run codex --enable rmcp_client
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).

Signals

GitHub stars: 32k
Forks: 4k
Last commit: Oct 2026

ahel review

S4info
community integration, published by davila7, not notion

Automated review, not a security audit. Ruleset v1+k2.

Questions

What kind of spec does it work with?: It works with PRDs and feature specs in Notion.
Does it create tasks in Notion?: Yes, it creates Notion plans and tasks from the spec.
Can it track progress?: Yes, it tracks progress against the implementation plan.
Do I need a Notion workspace?: Yes, the spec and the plan live in Notion.
What if my spec is not in Notion?: The skill is for Notion specs, so it expects the spec to be in Notion.

Advanced

Item type: skill
Key: notion-spec-to-implementation-davila7
Source: github.com/davila7/claude-code-templates

github.com/davila7/claude-code-templates