Notion spec to implementation skill
Turn Notion specs into implementation plans, tasks, and progress tracking.
by davila7·MIT license·★ 32,299 Stars on the repo·GitHub ↗
Use now
npx degit davila7/claude-code-templates/cli-tool/components/skills/productivity/notion-spec-to-implementation#main ~/.claude/skills/notion-spec-to-implementationChecked ·commit main
Files of Notion spec to implementation
SKILL.md
Show the full text59 lines
Spec to Implementation
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 withNotion: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 = trueinconfig.tomlor runcodex --enable rmcp_client
- Set
- 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. Seereference/spec-parsing.mdfor 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-fetchto confirm the data source and required properties). Patterns inreference/task-creation.md. - Size tasks to 1–2 days. Use
reference/task-creation-template.mdfor 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-pagesusing the database'sdata_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 withreference/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).
| 1 | |
| 2 | name notion-spec-to-implementation |
| 3 | description Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them. |
| 4 | metadata |
| 5 | short-description Turn Notion specs into implementation plans, tasks, and progress tracking |
| 6 | |
| 7 | |
| 8 | # Spec to Implementation |
| 9 | |
| 10 | Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates. |
| 11 | |
| 12 | ## Quick start |
| 13 | 1) Locate the spec with `Notion:notion-search`, then fetch it with `Notion:notion-fetch`. |
| 14 | 2) Parse requirements and ambiguities using `reference/spec-parsing.md`. |
| 15 | 3) Create a plan page with `Notion:notion-create-pages` (pick a template: quick vs. full). |
| 16 | 4) Find the task database, confirm schema, then create tasks with `Notion:notion-create-pages`. |
| 17 | 5) 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: |
| 22 | Add the Notion MCP: |
| 23 | `codex mcp add notion --url https://mcp.notion.com/mcp` |
| 24 | Enable remote MCP client: |
| 25 | Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client` |
| 26 | Log in with OAuth: |
| 27 | `codex mcp login notion` |
| 28 | |
| 29 | 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. |
| 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 |
Discussion
Alternatives
Academy guideStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
Analyze feature requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Advocacy program designerUse when the user asks to "design an employee advocacy program", "set up founder-led sharing", or "build a share kit for the team"; produces an advocacy program blueprint in two modes — participation-driven opt-in (default) or top-down assigned with its coercion and authenticity risks flagged — with a voluntary opt-in roster spec submitted as channel-registry proposal events, share kits with mandatory per-person variation, staggered human posting windows plus anti-pod guardrails (no coordinated identical reshares, no engagement rings), per-person material-connection disclosure lines per FTC and 《互联网广告管理办法》, and a Slack/Teams distribution spec. Not for paid creator campaigns — use campaign-planner. 员工倡导/创始人IP分享/内部分享计划/披露合规Act as a product managerGuides the AI to act as a product manager, assisting in writing product requirement documents and addressing product-related queries.Browse more free Claude skills or everything in Product.