Agent skill · Documentation

notion-spec-to-implementation

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

composio-communitygithub.com/composio-communityGitHub ↗
codex
Install
npx skills add composio-community/awesome-codex-skills --skill notion-spec-to-implementation --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 16
SKILL.md size: 3 KB
Bundled scripts: none
Path: notion-spec-to-implementation/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 15,591
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Spec to Implementation Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates. ## Quick start 1) Locate the spec with `Notion:notion-search`, then fetch it with `Notion:notion-fetch`. 2) Parse requirements and ambiguities using `reference/spec-parsing.md`. 3) Create a plan page with `Notion:notion-create-pages` (pick a template: quick vs. full). 4) Find the task database, confirm schema, then create tasks with `Notion:notion-create-pages`. 5) 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: 1. Add the Notion MCP: - `codex mcp add notion --url https://mcp.notion.com/mcp` 2. Enable remote MCP client: - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client` 3. 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. - Fetc

What's inside
Steps it walks through
  1. Quick start
  2. Workflow
  3. 1) Locate and read the spec
  4. 2) Choose plan depth
  5. 3) Create tasks
  6. 4) Link artifacts
  7. 5) Track progress
  8. References and examples
Ships with 15 files
  • LICENSE.txt
  • evaluations/README.md
  • evaluations/basic-spec-implementation.json
  • evaluations/spec-to-tasks.json
  • examples/api-feature.md
  • examples/database-migration.md
  • examples/ui-component.md
  • reference/milestone-summary-template.md
  • reference/progress-tracking.md
  • reference/progress-update-template.md
  • reference/quick-implementation-plan.md
  • reference/spec-parsing.md
  • reference/standard-implementation-plan.md
  • reference/task-creation-template.md
  • reference/task-creation.md
More from awesome-codex-skills
All skills →
About this skill
What does the notion-spec-to-implementation skill do?

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.

How do I install it?

Run `npx skills add composio-community/awesome-codex-skills --skill notion-spec-to-implementation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From composio-community/awesome-codex-skills, a repository with 15,591 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going