[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77SCFFB4N0HDPRM52CB4XH7":3,"skill-same:01M77SCFFB4N0HDPRM52CB4XH7":130},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77SCFFB4N0HDPRM52CB4XH7","notion-spec-to-implementation",null,"Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs\u002Ffeature specs and creating Notion plans + tasks from them.","vdcworkshop\u002FSkills-Catalog","vdcworkshop","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F275270998?v=4","01M77R8FXSKYTB2X9SSVJN7ZRZ","αtef βouafif","01M77R8FYGECN2YWM6WVBVPMGS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: notion-spec-to-implementation\ndescription: Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs\u002Ffeature 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:notion-search`, then fetch it with `Notion:notion-fetch`.\n2) Parse requirements and ambiguities using `reference\u002Fspec-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## Workflow\n\n### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:\n1. Add the Notion MCP:\n   - `codex mcp add notion --url https:\u002F\u002Fmcp.notion.com\u002Fmcp`\n2. Enable remote MCP client:\n   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`\n3. Log in with OAuth:\n   - `codex mcp login notion`\n\nAfter 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.\n\n### 1) Locate and read the spec\n- Search first (`Notion:notion-search`); if multiple hits, ask the user which to use.\n- Fetch the page (`Notion:notion-fetch`) and scan for requirements, acceptance criteria, constraints, and priorities. See `reference\u002Fspec-parsing.md` for extraction patterns.\n- Capture gaps\u002Fassumptions in a clarifications block before proceeding.\n\n### 2) Choose plan depth\n- Simple change → use `reference\u002Fquick-implementation-plan.md`.\n- Multi-phase feature\u002Fmigration → use `reference\u002Fstandard-implementation-plan.md`.\n- Create the plan via `Notion:notion-create-pages`, include: overview, linked spec, requirements summary, phases, dependencies\u002Frisks, and success criteria. Link back to the spec.\n\n### 3) Create tasks\n- Find the task database (`Notion:notion-search` → `Notion:notion-fetch` to confirm the data source and required properties). Patterns in `reference\u002Ftask-creation.md`.\n- Size tasks to 1–2 days. Use `reference\u002Ftask-creation-template.md` for content (context, objective, acceptance criteria, dependencies, resources).\n- Set properties: title\u002Faction verb, status, priority, relations to spec + plan, due date\u002Fstory points\u002Fassignee 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\u002Fprogress-tracking.md`.\n- Post updates with `reference\u002Fprogress-update-template.md`; close phases with `reference\u002Fmilestone-summary-template.md`.\n- Keep checklists and status fields in plan\u002Ftasks in sync; note blockers and decisions.\n\n## References and examples\n- `reference\u002F` — parsing patterns, plan\u002Ftask templates, progress cadence (e.g., `spec-parsing.md`, `standard-implementation-plan.md`, `task-creation.md`, `progress-tracking.md`).\n- `examples\u002F` — end-to-end walkthroughs (e.g., `ui-component.md`, `api-feature.md`, `database-migration.md`).\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:notion-search`, then fetch it with `Notion:notion-fetch`.\n2) Parse requirements and ambiguities using `reference\u002Fspec-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## Workflow\n\n### 0) If any MCP call fails because Notion MCP is not connected, pause and set it up:\n1. Add the Notion MCP:\n   - `codex mcp add notion --url https:\u002F\u002Fmcp.notion.com\u002Fmcp`\n2. Enable remote MCP client:\n   - Set `[features].rmcp_client = true` in `config.toml` **or** run `codex --enable rmcp_client`\n3. Log in with OAuth:\n   - `codex mcp login notion`\n\nAfter 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.\n\n### 1) Locate and read the spec\n- Search first (`Notion:notion-search`); if multiple hits, ask the user which to use.\n- Fetch the page (`Notion:notion-fetch`) and scan for requirements, acceptance criteria, constraints, and priorities. See `reference\u002Fspec-parsing.md` for extraction patterns.\n- Capture gaps\u002Fassumptions in a clarifications block before proceeding.\n\n### 2) Choose plan depth\n- Simple change → use `reference\u002Fquick-implementation-plan.md`.\n- Multi-phase feature\u002Fmigration → use `reference\u002Fstandard-implementation-plan.md`.\n- Create the plan via `Notion:notion-create-pages`, include: overview, linked spec, requirements summary, phases, dependencies\u002Frisks, and success criteria. Link back to the spec.\n\n### 3) Create tasks\n- Find the task database (`Notion:notion-search` → `Notion:notion-fetch` to confirm the data source and required properties). Patterns in `reference\u002Ftask-creation.md`.\n- Size tasks to 1–2 days. Use `reference\u002Ftask-creation-template.md` for content (context, objective, acceptance criteria, dependencies, resources).\n- Set properties: title\u002Faction verb, status, priority, relations to spec + plan, due date\u002Fstory points\u002Fassignee 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\u002Fprogress-tracking.md`.\n- Post updates with `reference\u002Fprogress-update-template.md`; close phases with `reference\u002Fmilestone-summary-template.md`.\n- Keep checklists and status fields in plan\u002Ftasks in sync; note blockers and decisions.\n\n## References and examples\n- `reference\u002F` — parsing patterns, plan\u002Ftask templates, progress cadence (e.g., `spec-parsing.md`, `standard-implementation-plan.md`, `task-creation.md`, `progress-tracking.md`).\n- `examples\u002F` — end-to-end walkthroughs (e.g., `ui-component.md`, `api-feature.md`, `database-migration.md`).\n",{"name":5,"metadata":25,"description":7},{"short-description":26},"Turn Notion specs into implementation plans, tasks, and progress tracking","main","cd5116e81009ad620d09c7bc8664ce8c37f88a99","02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation",0,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog","https:\u002F\u002Fgithub.com\u002Fvdcworkshop","https:\u002F\u002Fvdcworkshop.com","2026-06-28 03:22:57",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add vdcworkshop\u002FSkills-Catalog --skill notion-spec-to-implementation",{"tool":41,"command":42},"bunx","bunx skills add vdcworkshop\u002FSkills-Catalog --skill notion-spec-to-implementation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add vdcworkshop\u002FSkills-Catalog --skill notion-spec-to-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002FSKILL.md",true,[49,55,61,65,69,73,77,81,85,89,94,98,102,106,110,114,118,122,126],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",524,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Fnotion-small.svg","ASSET","资产文件",15777,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Fassets\u002Fnotion-small.svg",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"assets\u002Fnotion.png",8526,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Fassets\u002Fnotion.png",{"path":66,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":67,"sourceHtmlUrl":68},"evaluations\u002Fbasic-spec-implementation.json",2401,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Fevaluations\u002Fbasic-spec-implementation.json",{"path":70,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":71,"sourceHtmlUrl":72},"evaluations\u002FREADME.md",4427,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Fevaluations\u002FREADME.md",{"path":74,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":75,"sourceHtmlUrl":76},"evaluations\u002Fspec-to-tasks.json",2561,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Fevaluations\u002Fspec-to-tasks.json",{"path":78,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":79,"sourceHtmlUrl":80},"examples\u002Fapi-feature.md",13579,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Fexamples\u002Fapi-feature.md",{"path":82,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":83,"sourceHtmlUrl":84},"examples\u002Fdatabase-migration.md",2443,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Fexamples\u002Fdatabase-migration.md",{"path":86,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":87,"sourceHtmlUrl":88},"examples\u002Fui-component.md",1662,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Fexamples\u002Fui-component.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",1057,{"path":95,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":96,"sourceHtmlUrl":97},"README.md",833,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002FREADME.md",{"path":99,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":100,"sourceHtmlUrl":101},"reference\u002Fmilestone-summary-template.md",456,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Freference\u002Fmilestone-summary-template.md",{"path":103,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":104,"sourceHtmlUrl":105},"reference\u002Fprogress-tracking.md",9020,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Freference\u002Fprogress-tracking.md",{"path":107,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":108,"sourceHtmlUrl":109},"reference\u002Fprogress-update-template.md",420,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Freference\u002Fprogress-update-template.md",{"path":111,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":112,"sourceHtmlUrl":113},"reference\u002Fquick-implementation-plan.md",480,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Freference\u002Fquick-implementation-plan.md",{"path":115,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":116,"sourceHtmlUrl":117},"reference\u002Fspec-parsing.md",6942,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Freference\u002Fspec-parsing.md",{"path":119,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":120,"sourceHtmlUrl":121},"reference\u002Fstandard-implementation-plan.md",3286,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Freference\u002Fstandard-implementation-plan.md",{"path":123,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":124,"sourceHtmlUrl":125},"reference\u002Ftask-creation-template.md",597,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Freference\u002Ftask-creation-template.md",{"path":127,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":128,"sourceHtmlUrl":129},"reference\u002Ftask-creation.md",7965,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F08 Business Apps\u002Fnotion-spec-to-implementation\u002Freference\u002Ftask-creation.md",[131,138,145,153,160,167],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M77XBV88FMNX83MKDZMXKQZ2","rhaios-staging","Interact with the Rhaios staging REST API for yield operations. Discover -> prepare -> setup-if-needed -> sign -> execute flow with pluggable signer backend. Triggers on requests involving DeFi yield, vault deposits, redeems, rebalancing, or Rhaios API.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F12 Blockchain\u002F03 DeFi\u002Frhaios-staging\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":20},"01M77X7AFQGDCFHC25GQ7V92GZ","git-commit-push","Commit and push repository changes safely. Use when user asks to commit, push, or verify and push current changes.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F12 Blockchain\u002F01 Smart Contracts\u002Fgit-commit-push\u002FSKILL.md",[],[],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":149,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":20},"01M77X71FJ1KR7PTBPRC7S2241","exec-slurm-compile","Compile TensorRT-LLM on a SLURM cluster. Covers submitting a batch job with a container image, monitoring the job, and verifying the build. Use when the user wants to compile TRT-LLM remotely via SLURM rather than on a local compute node.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F12 Blockchain\u002F01 Smart Contracts\u002Fexec-slurm-compile\u002FSKILL.md",[],[],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":20},"01M77X4BQJ025SPPGRQ96X72QV","databases","Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F11 Databases\u002F03 NoSQL Databases\u002Fdatabases\u002FSKILL.md",[],[],{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":20},"01M77WZYZGCV9DK5HA0XCWSK97","toast","Toast — restaurant POS, orders, menus, employees, revenue centers, and reporting.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F10 Lifestyle\u002F06 Culinary Arts\u002Ftoast\u002FSKILL.md",[],[],{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":20},"01M77WYYESVCXT81ERPHM77SA9","k-schoollunch-menu","Use when the user asks for Korean school meal menus (급식 식단) by natural-language education office and school name, via k-skill-proxy NEIS school-search and school-meal routes.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F10 Lifestyle\u002F06 Culinary Arts\u002Fk-schoollunch-menu\u002FSKILL.md",[],[]]