skills/notion-spec-to-implementation/SKILL.md
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
npx skillsauth add chatandbuild/chatchat-skills notion-spec-to-implementationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Convert a Notion spec into linked implementation plans, tasks, and ongoing status updates.
Notion:notion-search, then fetch it with Notion:notion-fetch.reference/spec-parsing.md.Notion:notion-create-pages (pick a template: quick vs. full).Notion:notion-create-pages.Notion:notion-update-page.codex mcp add notion --url https://mcp.notion.com/mcp[features].rmcp_client = true in config.toml or run codex --enable rmcp_clientcodex mcp login notionAfter 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.
Notion:notion-search); if multiple hits, ask the user which to use.Notion:notion-fetch) and scan for requirements, acceptance criteria, constraints, and priorities. See reference/spec-parsing.md for extraction patterns.reference/quick-implementation-plan.md.reference/standard-implementation-plan.md.Notion:notion-create-pages, include: overview, linked spec, requirements summary, phases, dependencies/risks, and success criteria. Link back to the spec.Notion:notion-search → Notion:notion-fetch to confirm the data source and required properties). Patterns in reference/task-creation.md.reference/task-creation-template.md for content (context, objective, acceptance criteria, dependencies, resources).Notion:notion-create-pages using the database’s data_source_id.Notion:notion-update-page.reference/progress-tracking.md.reference/progress-update-template.md; close phases with reference/milestone-summary-template.md.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).tools
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
development
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
development
Use this skill when turning messy workout information into clear logs, comparing user-provided sessions, surfacing trends or likely PRs, and suggesting realistic next-session steps.
tools
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.