[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AJB0FVBPCKJM80R9XPCQQ":3,"skill-same:01M71AJB0FVBPCKJM80R9XPCQQ":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M71AJB0FVBPCKJM80R9XPCQQ","prd-to-plan",null,"Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in .\u002Fplans\u002F. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions \"tracer bullets\".","eiei114\u002Fclaude-code-template","eiei114","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60887155?v=4","01M71AG644Y7ZYKMN5WQQY0NGA","01M71AG64WKT3DJGHWWJJH84HQ",0,"MIT","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fprd-to-plan\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"to plan","prd to plan","prd","plan","implementation","break","markdown","create","multi","saved","phase","file","break down","when","use","plans","implementation plan","local","down","as","2026-11-10 10:12:30",false,"---\nname: prd-to-plan\ndescription: Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in .\u002Fplans\u002F. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions \"tracer bullets\".\n---\n\n# PRD to Plan\n\nBreak a PRD into a phased implementation plan using vertical slices (tracer bullets). Output is a Markdown file in `.\u002Fplans\u002F`.\n\n## Process\n\n### 1. Confirm the PRD is in context\n\nThe PRD should already be in the conversation. If it isn't, ask the user to paste it or point you to the file.\n\n### 2. Explore the codebase\n\nIf you have not already explored the codebase, do so to understand the current architecture, existing patterns, and integration layers.\n\n### 3. Identify durable architectural decisions\n\nBefore slicing, identify high-level decisions that are unlikely to change throughout implementation:\n\n- Route structures \u002F URL patterns\n- Database schema shape\n- Key data models\n- Authentication \u002F authorization approach\n- Third-party service boundaries\n\nThese go in the plan header so every phase can reference them.\n\n### 4. Draft vertical slices\n\nBreak the PRD into **tracer bullet** phases. Each phase is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.\n\n\u003Cvertical-slice-rules>\n- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)\n- A completed slice is demoable or verifiable on its own\n- Prefer many thin slices over few thick ones\n- Do NOT include specific file names, function names, or implementation details that are likely to change as later phases are built\n- DO include durable decisions: route paths, schema shapes, data model names\n\u003C\u002Fvertical-slice-rules>\n\n### 5. Quiz the user\n\nPresent the proposed breakdown as a numbered list. For each phase show:\n\n- **Title**: short descriptive name\n- **User stories covered**: which user stories from the PRD this addresses\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Should any phases be merged or split further?\n\nIterate until the user approves the breakdown.\n\n### 6. Write the plan file\n\nCreate `.\u002Fplans\u002F` if it doesn't exist. Write the plan as a Markdown file named after the feature (e.g. `.\u002Fplans\u002Fuser-onboarding.md`). Use the template below.\n\n\u003Cplan-template>\n# Plan: \u003CFeature Name>\n\n> Source PRD: \u003Cbrief identifier or link>\n\n## Architectural decisions\n\nDurable decisions that apply across all phases:\n\n- **Routes**: ...\n- **Schema**: ...\n- **Key models**: ...\n- (add\u002Fremove sections as appropriate)\n\n---\n\n## Phase 1: \u003CTitle>\n\n**User stories**: \u003Clist from PRD>\n\n### What to build\n\nA concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.\n\n### Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n- [ ] Criterion 3\n\n---\n\n## Phase 2: \u003CTitle>\n\n**User stories**: \u003Clist from PRD>\n\n### What to build\n\n...\n\n### Acceptance criteria\n\n- [ ] ...\n\n\u003C!-- Repeat for each phase -->\n\u003C\u002Fplan-template>\n","# PRD to Plan\n\nBreak a PRD into a phased implementation plan using vertical slices (tracer bullets). Output is a Markdown file in `.\u002Fplans\u002F`.\n\n## Process\n\n### 1. Confirm the PRD is in context\n\nThe PRD should already be in the conversation. If it isn't, ask the user to paste it or point you to the file.\n\n### 2. Explore the codebase\n\nIf you have not already explored the codebase, do so to understand the current architecture, existing patterns, and integration layers.\n\n### 3. Identify durable architectural decisions\n\nBefore slicing, identify high-level decisions that are unlikely to change throughout implementation:\n\n- Route structures \u002F URL patterns\n- Database schema shape\n- Key data models\n- Authentication \u002F authorization approach\n- Third-party service boundaries\n\nThese go in the plan header so every phase can reference them.\n\n### 4. Draft vertical slices\n\nBreak the PRD into **tracer bullet** phases. Each phase is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.\n\n\u003Cvertical-slice-rules>\n- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)\n- A completed slice is demoable or verifiable on its own\n- Prefer many thin slices over few thick ones\n- Do NOT include specific file names, function names, or implementation details that are likely to change as later phases are built\n- DO include durable decisions: route paths, schema shapes, data model names\n\u003C\u002Fvertical-slice-rules>\n\n### 5. Quiz the user\n\nPresent the proposed breakdown as a numbered list. For each phase show:\n\n- **Title**: short descriptive name\n- **User stories covered**: which user stories from the PRD this addresses\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Should any phases be merged or split further?\n\nIterate until the user approves the breakdown.\n\n### 6. Write the plan file\n\nCreate `.\u002Fplans\u002F` if it doesn't exist. Write the plan as a Markdown file named after the feature (e.g. `.\u002Fplans\u002Fuser-onboarding.md`). Use the template below.\n\n\u003Cplan-template>\n# Plan: \u003CFeature Name>\n\n> Source PRD: \u003Cbrief identifier or link>\n\n## Architectural decisions\n\nDurable decisions that apply across all phases:\n\n- **Routes**: ...\n- **Schema**: ...\n- **Key models**: ...\n- (add\u002Fremove sections as appropriate)\n\n---\n\n## Phase 1: \u003CTitle>\n\n**User stories**: \u003Clist from PRD>\n\n### What to build\n\nA concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.\n\n### Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n- [ ] Criterion 3\n\n---\n\n## Phase 2: \u003CTitle>\n\n**User stories**: \u003Clist from PRD>\n\n### What to build\n\n...\n\n### Acceptance criteria\n\n- [ ] ...\n\n\u003C!-- Repeat for each phase -->\n\u003C\u002Fplan-template>\n",{"name":5,"description":7},"main","7959c7e2d5ebcd9c684c4372eaa278dac53a1805","skills\u002Fprd-to-plan","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template","https:\u002F\u002Fgithub.com\u002Feiei114","https:\u002F\u002Fspot-camelotia-ca8.notion.site\u002FPortfolio-66f9a6d667d84785afe1cecfea0fd2ab","Roblox & UEFN Engineer","2026-04-19 15:32:22",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add eiei114\u002Fclaude-code-template --skill prd-to-plan",{"tool":62,"command":63},"bunx","bunx skills add eiei114\u002Fclaude-code-template --skill prd-to-plan",{"tool":65,"command":66},"pnpm","pnpm dlx skills add eiei114\u002Fclaude-code-template --skill prd-to-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fprd-to-plan\u002FSKILL.md",true,[],[71,96,113,133,161,184],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":88,"publishedAt":43},"01M71AKWNFHFZ3R213KZZ02NV3","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[77,82,85],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",[89,90,91,92,93,37,94,95,36],"writing","writing skills","work","editing","deployment","Existing","new",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":104,"publishedAt":43},"01M71AKV2MQCJ0MYHT0JQ3N7T8","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[102,103],{"categoryNo":83,"categoryName":84,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":86,"categoryName":87,"taxonomyType":20,"taxonomyTypeDesc":21},[105,38,89,106,31,107,108,109,110,111,36,37,112],"writing plans","for","spec","multi-step task","code","requirements","you","task",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":43},"01M71AKSFECF023Y09S63M71MW","write-a-prd","Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwrite-a-prd\u002FSKILL.md",[119],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[121,122,25,123,36,124,37,95,125,126,127,128,129,42,130,131,26,132,30,110],"write","write a prd","codebase exploration","document","module","design","submit","feature","exploration","interview","user interview","new feature",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":137,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":145,"publishedAt":43},"01M71AKQNV0SWR65KYTXV5PNTZ","webapp-testing","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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[141,142],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},{"categoryNo":143,"categoryName":144,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000009","前端开发",[146,147,148,40,149,150,151,152,153,154,155,156,157,158,159,160,106],"webapp testing","testing","webapp","ui","behavior","web","playwright","with","browser","logs","toolkit","debugging","frontend","screenshots","applications",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":137,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":169,"publishedAt":43},"01M71AKMVPPNG5S07QXZACP049","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[168],{"categoryNo":143,"categoryName":144,"taxonomyType":80,"taxonomyTypeDesc":81},[170,151,171,172,173,174,158,175,176,106,177,178,37,179,180,181,31,182,183,34],"web artifacts builder","artifacts","artifacts builder","builder","single","ui components","Tailwind","css","single-file","state management","routing","state","react","components",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":43},"01M71AKHAW8VXPPM2PM22H2P4Q","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Feiei114\u002Fclaude-code-template\u002Fblob\u002Fmain\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[191,192,193,194,195,91,196,36,197,37,198,199,200,201,202],"verification before completion","verification","claims","commands","about","output","assertions","claim","prs","complete","evidence","running"]