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.
Best use case
notion-spec-to-implementation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
Teams using notion-spec-to-implementation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/notion-spec-to-implementation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How notion-spec-to-implementation Compares
| Feature / Agent | notion-spec-to-implementation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this 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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 → 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`).
Related Skills
vertex-engine-inspector
Inspect and validate Vertex AI Agent Engine deployments including Code Execution Sandbox, Memory Bank, A2A protocol compliance, and security posture. Generates production readiness scores. Use when asked to inspect, validate, or audit an Agent Engine deployment. Trigger with "inspect agent engine", "validate agent engine deployment", "check agent engine config", "audit agent engine security", "agent engine readiness check", "vertex engine health", or "reasoning engine status".
spec-writing
Execute this skill should be used when the user asks about "writing specs", "specs.md format", "how to write specifications", "sprint requirements", "testing configuration", "scope definition", or needs guidance on creating effective sprint specifications for agentic development. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
openapi-spec-generator
Openapi Spec Generator - Auto-activating skill for API Development. Triggers on: openapi spec generator, openapi spec generator Part of the API Development skill category.
validating-authentication-implementations
This skill enables Claude to validate authentication implementations against security best practices and industry standards. It analyzes various authentication methods, including JWT, OAuth, session-based authentication, and API keys. Use this skill when you need to perform an authentication security check, assess password policies, evaluate MFA implementation, or analyze session security. Trigger this skill with phrases like "validate authentication," "authentication check," or "authcheck."
adk-deployment-specialist
Deploy and orchestrate Vertex AI ADK agents using A2A protocol. Manages AgentCard discovery, task submission, Code Execution Sandbox, and Memory Bank. Use when asked to "deploy ADK agent" or "orchestrate agents". Trigger with phrases like 'deploy', 'infrastructure', or 'CI/CD'.
update-specification
Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.
update-implementation-plan
Update an existing implementation plan file with new or update requirements to provide new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.
typespec-create-api-plugin
Generate a TypeSpec API plugin with REST operations, authentication, and Adaptive Cards for Microsoft 365 Copilot
typespec-create-agent
Generate a complete TypeSpec declarative agent with instructions, capabilities, and conversation starters for Microsoft 365 Copilot
typespec-api-operations
Add GET, POST, PATCH, and DELETE operations to a TypeSpec API plugin with proper routing, parameters, and adaptive cards
gen-specs-as-issues
This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.
create-specification
Create a new specification file for the solution, optimized for Generative AI consumption.