Update to Notion

{
  "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.",
  "included_files": [
    {
      "relative_path": "LICENSE.txt",
      "size_in_bytes": 1057
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 339
    },
    {
      "relative_path": "assets/notion-small.svg",
      "size_in_bytes": 1561
    },
    {
      "relative_path": "assets/notion.png",
      "size_in_bytes": 8526
    },
    {
      "relative_path": "evaluations/README.md",
      "size_in_bytes": 4441
    },
    {
      "relative_path": "evaluations/basic-spec-implementation.json",
      "size_in_bytes": 2358
    },
    {
      "relative_path": "evaluations/spec-to-tasks.json",
      "size_in_bytes": 2504
    },
    {
      "relative_path": "examples/api-feature.md",
      "size_in_bytes": 14073
    },
    {
      "relative_path": "examples/database-migration.md",
      "size_in_bytes": 2639
    },
    {
      "relative_path": "examples/ui-component.md",
      "size_in_bytes": 2150
    },
    {
      "relative_path": "reference/milestone-summary-template.md",
      "size_in_bytes": 455
    },
    {
      "relative_path": "reference/progress-tracking.md",
      "size_in_bytes": 9018
    },
    {
      "relative_path": "reference/progress-update-template.md",
      "size_in_bytes": 419
    },
    {
      "relative_path": "reference/quick-implementation-plan.md",
      "size_in_bytes": 479
    },
    {
      "relative_path": "reference/spec-parsing.md",
      "size_in_bytes": 7057
    },
    {
      "relative_path": "reference/standard-implementation-plan.md",
      "size_in_bytes": 3285
    },
    {
      "relative_path": "reference/task-creation-template.md",
      "size_in_bytes": 596
    },
    {
      "relative_path": "reference/task-creation.md",
      "size_in_bytes": 8025
    }
  ],
  "skill_md_contents": "---\nname: notion-spec-to-implementation\ndescription: Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.\nmetadata:\n  short-description: Turn Notion specs into implementation plans, tasks, and progress tracking\n---\n\n# Spec to Implementation\n\nConvert a Notion spec into linked implementation plans, tasks, and ongoing status updates.\n\n## Quick start\n1) Locate the spec with `Notion:search`, then fetch it with `Notion:fetch`.\n2) Parse requirements and ambiguities using `reference/spec-parsing.md`.\n3) Create a plan page with `Notion:notion-create-pages` (pick a template: quick vs. full).\n4) Find the task database, confirm schema, then create tasks with `Notion:notion-create-pages`.\n5) Link spec ↔ plan ↔ tasks; keep status current with `Notion:notion-update-page`.\n\n## Tool-call guardrails\n- Notion tool availability can vary by workspace. If a Notion MCP call returns `Tool <name> not found`, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use `Notion:search` and `Notion:fetch` where sufficient.\n- Use one literal search query per `Notion:search` call and include `filters: {}` when no narrower filter is needed. Run separate searches for alternate phrasings instead of putting `or` in a single query string.\n- Only send Notion page, database, or data-source URLs/IDs to `Notion:fetch`; external connected-source search results are not fetch targets.\n- Create plans and task pages with explicit `parent` and `pages` fields. For task databases, fetch first and use the returned `collection://...` data source ID.\n- To append an implementation section to a spec, fetch the current section text first, then use `Notion:notion-update-page` with `command: \"update_content\"`, `properties: {}`, and exact `old_str` / `new_str` content. For property-only edits, use `command: \"update_properties\"` with `content_updates: []`; the current deployed schema expects both top-level fields even when one is unused.\n\n## Workflow\n\n### 0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:\n1. Enable the bundled Notion app for this plugin or session.\n2. Complete the Notion auth flow if prompted.\n3. Start a new session if the tools still do not appear.\n\nAfter the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.\n\n### 1) Locate and read the spec\n- Search first (`Notion:search`); if multiple hits, ask the user which to use.\n- Fetch the page (`Notion:fetch`) and scan for requirements, acceptance criteria, constraints, and priorities. See `reference/spec-parsing.md` for extraction patterns.\n- Capture gaps/assumptions in a clarifications block before proceeding.\n\n### 2) Choose plan depth\n- Simple change → use `reference/quick-implementation-plan.md`.\n- Multi-phase feature/migration → use `reference/standard-implementation-plan.md`.\n- 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.\n\n### 3) Create tasks\n- Find the task database (`Notion:search` → `Notion:fetch` to confirm the data source and required properties). Patterns in `reference/task-creation.md`.\n- Size tasks to 1–2 days. Use `reference/task-creation-template.md` for content (context, objective, acceptance criteria, dependencies, resources).\n- Set properties: title/action verb, status, priority, relations to spec + plan, due date/story points/assignee if provided.\n- Create pages with `Notion:notion-create-pages` using the database’s `data_source_id`.\n\n### 4) Link artifacts\n- Plan links to spec; tasks link to both plan and spec.\n- Optionally update the spec with a short “Implementation” section pointing to the plan and tasks using `Notion:notion-update-page`.\n\n### 5) Track progress\n- Use the cadence in `reference/progress-tracking.md`.\n- Post updates with `reference/progress-update-template.md`; close phases with `reference/milestone-summary-template.md`.\n- Keep checklists and status fields in plan/tasks in sync; note blockers and decisions.\n\n## References and examples\n- `reference/` — parsing patterns, plan/task templates, progress cadence (e.g., `spec-parsing.md`, `standard-implementation-plan.md`, `task-creation.md`, `progress-tracking.md`).\n- `examples/` — end-to-end walkthroughs (e.g., `ui-component.md`, `api-feature.md`, `database-migration.md`).\n"
}