← ClaudeAtlas

notion-spec-to-implementationlisted

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
aiskillstore/marketplace · ★ 334 · Testing & QA · score 83
Install: claude install-skill aiskillstore/marketplace
# 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. - 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 →