[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD9V7G4NCQQZDATT0ZM2R5":3,"skill-same:01M6AD9V7G4NCQQZDATT0ZM2R5":71},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6AD9V7G4NCQQZDATT0ZM2R5","breakdown-feature-prd",null,"Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41081,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fbreakdown-feature-prd\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41],"breakdown feature prd","prd","feature","breakdown","documents","product","prompt","requirements","EPIC","Product Requirements","for","features","new","2026-11-10 10:12:30",false,"---\nname: breakdown-feature-prd\ndescription: 'Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.'\n---\n\n# Feature PRD Prompt\n\n## Goal\n\nAct as an expert Product Manager for a large-scale SaaS platform. Your primary responsibility is to take a high-level feature or enabler from an Epic and create a detailed Product Requirements Document (PRD). This PRD will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical specification.\n\nReview the user's request for a new feature and the parent Epic, and generate a thorough PRD. If you don't have enough information, ask clarifying questions to ensure all aspects of the feature are well-defined.\n\n## Output Format\n\nThe output should be a complete PRD in Markdown format, saved to `\u002Fdocs\u002Fways-of-work\u002Fplan\u002F{epic-name}\u002F{feature-name}\u002Fprd.md`.\n\n### PRD Structure\n\n#### 1. Feature Name\n\n- A clear, concise, and descriptive name for the feature.\n\n#### 2. Epic\n\n- Link to the parent Epic PRD and Architecture documents.\n\n#### 3. Goal\n\n- **Problem:** Describe the user problem or business need this feature addresses (3-5 sentences).\n- **Solution:** Explain how this feature solves the problem.\n- **Impact:** What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, etc.)?\n\n#### 4. User Personas\n\n- Describe the target user(s) for this feature.\n\n#### 5. User Stories\n\n- Write user stories in the format: \"As a `\u003Cuser persona>`, I want to `\u003Cperform an action>` so that I can `\u003Cachieve a benefit>`.\"\n- Cover the primary paths and edge cases.\n\n#### 6. Requirements\n\n- **Functional Requirements:** A detailed, bulleted list of what the system must do. Be specific and unambiguous.\n- **Non-Functional Requirements:** A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).\n\n#### 7. Acceptance Criteria\n\n- For each user story or major requirement, provide a set of acceptance criteria.\n- Use a clear format, such as a checklist or Given\u002FWhen\u002FThen. This will be used to validate that the feature is complete and correct.\n\n#### 8. Out of Scope\n\n- Clearly list what is _not_ included in this feature to avoid scope creep.\n\n## Context Template\n\n- **Epic:** [Link to the parent Epic documents]\n- **Feature Idea:** [A high-level description of the feature request from the user]\n- **Target Users:** [Optional: Any initial thoughts on who this is for]\n","# Feature PRD Prompt\n\n## Goal\n\nAct as an expert Product Manager for a large-scale SaaS platform. Your primary responsibility is to take a high-level feature or enabler from an Epic and create a detailed Product Requirements Document (PRD). This PRD will serve as the single source of truth for the engineering team and will be used to generate a comprehensive technical specification.\n\nReview the user's request for a new feature and the parent Epic, and generate a thorough PRD. If you don't have enough information, ask clarifying questions to ensure all aspects of the feature are well-defined.\n\n## Output Format\n\nThe output should be a complete PRD in Markdown format, saved to `\u002Fdocs\u002Fways-of-work\u002Fplan\u002F{epic-name}\u002F{feature-name}\u002Fprd.md`.\n\n### PRD Structure\n\n#### 1. Feature Name\n\n- A clear, concise, and descriptive name for the feature.\n\n#### 2. Epic\n\n- Link to the parent Epic PRD and Architecture documents.\n\n#### 3. Goal\n\n- **Problem:** Describe the user problem or business need this feature addresses (3-5 sentences).\n- **Solution:** Explain how this feature solves the problem.\n- **Impact:** What are the expected outcomes or metrics to be improved (e.g., user engagement, conversion rate, etc.)?\n\n#### 4. User Personas\n\n- Describe the target user(s) for this feature.\n\n#### 5. User Stories\n\n- Write user stories in the format: \"As a `\u003Cuser persona>`, I want to `\u003Cperform an action>` so that I can `\u003Cachieve a benefit>`.\"\n- Cover the primary paths and edge cases.\n\n#### 6. Requirements\n\n- **Functional Requirements:** A detailed, bulleted list of what the system must do. Be specific and unambiguous.\n- **Non-Functional Requirements:** A bulleted list of constraints and quality attributes (e.g., performance, security, accessibility, data privacy).\n\n#### 7. Acceptance Criteria\n\n- For each user story or major requirement, provide a set of acceptance criteria.\n- Use a clear format, such as a checklist or Given\u002FWhen\u002FThen. This will be used to validate that the feature is complete and correct.\n\n#### 8. Out of Scope\n\n- Clearly list what is _not_ included in this feature to avoid scope creep.\n\n## Context Template\n\n- **Epic:** [Link to the parent Epic documents]\n- **Feature Idea:** [A high-level description of the feature request from the user]\n- **Target Users:** [Optional: Any initial thoughts on who this is for]\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fbreakdown-feature-prd",5344,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot","https:\u002F\u002Fawesome-copilot.github.com\u002F","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-13 02:05:36",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add github\u002Fawesome-copilot --skill breakdown-feature-prd",{"tool":63,"command":64},"bunx","bunx skills add github\u002Fawesome-copilot --skill breakdown-feature-prd",{"tool":66,"command":67},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill breakdown-feature-prd","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fbreakdown-feature-prd\u002FSKILL.md",true,[],[72,103,130,158,191,208],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":82,"publishedAt":42},"01M70KXZNX9ES38N2A8M58ZZMZ","supabase-rls-policies","Write, review, and test Supabase Row Level Security (RLS) policies so that one user cannot read or change another user's rows. Use when creating or changing tables, policies, views, or security definer functions in a Supabase project, when reviewing a migration that touches RLS, or when asked to prove user isolation with pgTAP tests that sign in as two users.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase-rls-policies\u002FSKILL.md",[78,81],{"categoryNo":79,"categoryName":80,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":110,"publishedAt":42},"01M70KWA5YWXDV6V8DZ19E3T2Y","skill-distribution-audit","Audit a skill collection before release or investigate installer omissions, archived\u002Ftemplate leakage, duplicate identities, and manifest drift. Reconcile the intended public source set, distribution manifest, and actual discovery output for a specified consumer version. Includes a deterministic set-comparison helper.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fskill-distribution-audit\u002FSKILL.md",[109],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[111,112,113,114,115,116,39,117,118,119,120,121,122,123,124,125,126,127,128,129],"distribution","skill distribution audit","audit","SET","deterministic","installer","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":42},"01M70KCJPFVW7PPQ49CC5R8JGK","logicapps-custom-code-net10-migration","Migrate Azure Logic Apps Standard local-function custom-code projects from .NET 8 to .NET 10. Use for legacy Logic Apps custom-code workspace upgrades, project\u002Fpackage configuration, custom-worker settings, publication, and integrated VS Code debugging. Not for ordinary .NET applications, standalone Azure Functions, Consumption workflows, or cloud deployment.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Flogicapps-custom-code-net10-migration\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[141,142,143,144,145,146,39,87,147,148,149,150,151,152,153,99,154,155,156,157],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":162,"sourceHtmlUrl":163,"categories":164,"keywords":169,"publishedAt":42},"01M6AEBN37RQMXJ3298PEY7PG1","winmd-api-search","Find and explore Windows desktop APIs. Use when building features that need platform capabilities — camera, file access, notifications, UI controls, AI\u002FML, sensors, networking, etc. Discovers the right API for a task and retrieves full type details (methods, properties, events, enumeration values).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fwinmd-api-search\u002FSKILL.md",[165,168],{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":138,"categoryName":139,"taxonomyType":26,"taxonomyTypeDesc":27},[170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,88,40,185,186,187,188,39,189,190],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","full","camera","events","platform","methods","controls",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":195,"licenseFileUrl":196,"sourceHtmlUrl":197,"categories":198,"keywords":204,"publishedAt":42},"01M6AE571R3SC1ZGE202B3NB5S","resemble-detect","Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fresemble-detect\u002FSKILL.md",[199,200,203],{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":201,"categoryName":202,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[205,114,179,206,207],"resemble detect","https","identity",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":195,"licenseFileUrl":212,"sourceHtmlUrl":213,"categories":214,"keywords":219,"publishedAt":42},"01M6AE30BSK2HCY4TQQ22Z8JRD","quality-playbook","Run a complete quality engineering audit on any codebase. Derives behavioral requirements from the code, generates spec-traced functional tests, runs a three-pass code review with regression tests, executes a multi-model spec audit (Council of Three), and produces a consolidated bug report with TDD-verified patches. Finds the 35% of real defects that structural code review alone cannot catch. Works with any language. Trigger on 'quality playbook', 'spec audit', 'Council of Three', 'fitness-to-purpose', or 'coverage theater'.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fquality-playbook\u002FSKILL.md",[215,218],{"categoryNo":216,"categoryName":217,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[220,221,222,223,142,89,9,113,224,225,206,226,227,228,229,230,231,232,233,234,235,236,97,237,238,239,240],"playbook","quality playbook","quality","code review","tdd","run","report","spec","bug report","council","engineering","functional","spec audit","bug","verified","multi-model","three","coverage","model","regression","structural"]