| name | notion-spec-to-implementation |
| description | Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them. |
| metadata | {"short-description":"Turn Notion specs into implementation plans, tasks, and progress tracking"} |
Spec to Implementation
Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.
Quick start
- Locate the spec with the available Notion search tool, then fetch it with the available Notion page-read tool.
- Parse requirements and ambiguities using
reference/spec-parsing.md.
- Create a plan page with the available Notion page/database create tool (pick a template: quick vs. full).
- Find the task database, confirm schema, then create tasks with the available Notion create tool.
- Link spec ↔ plan ↔ tasks; keep status current with the available Notion update tool.
Workflow
0) If Notion tools are unavailable, pause and ask the user to enable the Notion integration:
- Enable the
notion MCP entry in editors/agents/opencode/opencode.json for this environment or session.
- Complete the Notion auth flow if OpenCode prompts for it.
- Restart OpenCode or the current session if the tools still do not appear.
After the integration is enabled, finish your answer and tell the user to retry so they can continue with Step 1.
1) Locate and read the spec
- Search first using the available Notion search tool; if multiple hits, ask the user which to use.
- Fetch the page using the available Notion page-read tool and scan for requirements, acceptance criteria, constraints, and priorities. See for extraction patterns.