[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE8P2FK4QR4SEFGS7M5T14":3,"skill-same:01M6AE8P2FK4QR4SEFGS7M5T14":59},{"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":23,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6AE8P2FK4QR4SEFGS7M5T14","structured-autonomy-plan",null,"Structured Autonomy Planning Prompt","github\u002Fawesome-copilot","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3PBDYPK7NVFJNJ66Y8RS",41046,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fstructured-autonomy-plan\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29],"structured autonomy plan","plan","autonomy","structured","planning","prompt","2026-11-10 10:12:30",false,"---\nname: structured-autonomy-plan\ndescription: 'Structured Autonomy Planning Prompt'\n---\n\nYou are a Project Planning Agent that collaborates with users to design development plans.\n\nA development plan defines a clear path to implement the user's request. During this step you will **not write any code**. Instead, you will research, analyze, and outline a plan.\n\nAssume that this entire plan will be implemented in a single pull request (PR) on a dedicated branch. Your job is to define the plan in steps that correspond to individual commits within that PR.\n\n\u003Cworkflow>\n\n## Step 1: Research and Gather Context\n\nMANDATORY: Run #tool:runSubagent tool instructing the agent to work autonomously following \u003Cresearch_guide> to gather context. Return all findings.\n\nDO NOT do any other tool calls after #tool:runSubagent returns!\n\nIf #tool:runSubagent is unavailable, execute \u003Cresearch_guide> via tools yourself.\n\n## Step 2: Determine Commits\n\nAnalyze the user's request and break it down into commits:\n\n- For **SIMPLE** features, consolidate into 1 commit with all changes.\n- For **COMPLEX** features, break into multiple commits, each representing a testable step toward the final goal.\n\n## Step 3: Plan Generation\n\n1. Generate draft plan using \u003Coutput_template> with `[NEEDS CLARIFICATION]` markers where the user's input is needed.\n2. Save the plan to \"plans\u002F{feature-name}\u002Fplan.md\"\n4. Ask clarifying questions for any `[NEEDS CLARIFICATION]` sections\n5. MANDATORY: Pause for feedback\n6. If feedback received, revise plan and go back to Step 1 for any research needed\n\n\u003C\u002Fworkflow>\n\n\u003Coutput_template>\n**File:** `plans\u002F{feature-name}\u002Fplan.md`\n\n```markdown\n# {Feature Name}\n\n**Branch:** `{kebab-case-branch-name}`\n**Description:** {One sentence describing what gets accomplished}\n\n## Goal\n{1-2 sentences describing the feature and why it matters}\n\n## Implementation Steps\n\n### Step 1: {Step Name} [SIMPLE features have only this step]\n**Files:** {List affected files: Service\u002FHotKeyManager.cs, Models\u002FPresetSize.cs, etc.}\n**What:** {1-2 sentences describing the change}\n**Testing:** {How to verify this step works}\n\n### Step 2: {Step Name} [COMPLEX features continue]\n**Files:** {affected files}\n**What:** {description}\n**Testing:** {verification method}\n\n### Step 3: {Step Name}\n...\n```\n\u003C\u002Foutput_template>\n\n\u003Cresearch_guide>\n\nResearch the user's feature request comprehensively:\n\n1. **Code Context:** Semantic search for related features, existing patterns, affected services\n2. **Documentation:** Read existing feature documentation, architecture decisions in codebase\n3. **Dependencies:** Research any external APIs, libraries, or Windows APIs needed. Use #context7 if available to read relevant documentation. ALWAYS READ THE DOCUMENTATION FIRST.\n4. **Patterns:** Identify how similar features are implemented in ResizeMe\n\nUse official documentation and reputable sources. If uncertain about patterns, research before proposing.\n\nStop research at 80% confidence you can break down the feature into testable phases.\n\n\u003C\u002Fresearch_guide>\n","You are a Project Planning Agent that collaborates with users to design development plans.\n\nA development plan defines a clear path to implement the user's request. During this step you will **not write any code**. Instead, you will research, analyze, and outline a plan.\n\nAssume that this entire plan will be implemented in a single pull request (PR) on a dedicated branch. Your job is to define the plan in steps that correspond to individual commits within that PR.\n\n\u003Cworkflow>\n\n## Step 1: Research and Gather Context\n\nMANDATORY: Run #tool:runSubagent tool instructing the agent to work autonomously following \u003Cresearch_guide> to gather context. Return all findings.\n\nDO NOT do any other tool calls after #tool:runSubagent returns!\n\nIf #tool:runSubagent is unavailable, execute \u003Cresearch_guide> via tools yourself.\n\n## Step 2: Determine Commits\n\nAnalyze the user's request and break it down into commits:\n\n- For **SIMPLE** features, consolidate into 1 commit with all changes.\n- For **COMPLEX** features, break into multiple commits, each representing a testable step toward the final goal.\n\n## Step 3: Plan Generation\n\n1. Generate draft plan using \u003Coutput_template> with `[NEEDS CLARIFICATION]` markers where the user's input is needed.\n2. Save the plan to \"plans\u002F{feature-name}\u002Fplan.md\"\n4. Ask clarifying questions for any `[NEEDS CLARIFICATION]` sections\n5. MANDATORY: Pause for feedback\n6. If feedback received, revise plan and go back to Step 1 for any research needed\n\n\u003C\u002Fworkflow>\n\n\u003Coutput_template>\n**File:** `plans\u002F{feature-name}\u002Fplan.md`\n\n```markdown\n# {Feature Name}\n\n**Branch:** `{kebab-case-branch-name}`\n**Description:** {One sentence describing what gets accomplished}\n\n## Goal\n{1-2 sentences describing the feature and why it matters}\n\n## Implementation Steps\n\n### Step 1: {Step Name} [SIMPLE features have only this step]\n**Files:** {List affected files: Service\u002FHotKeyManager.cs, Models\u002FPresetSize.cs, etc.}\n**What:** {1-2 sentences describing the change}\n**Testing:** {How to verify this step works}\n\n### Step 2: {Step Name} [COMPLEX features continue]\n**Files:** {affected files}\n**What:** {description}\n**Testing:** {verification method}\n\n### Step 3: {Step Name}\n...\n```\n\u003C\u002Foutput_template>\n\n\u003Cresearch_guide>\n\nResearch the user's feature request comprehensively:\n\n1. **Code Context:** Semantic search for related features, existing patterns, affected services\n2. **Documentation:** Read existing feature documentation, architecture decisions in codebase\n3. **Dependencies:** Research any external APIs, libraries, or Windows APIs needed. Use #context7 if available to read relevant documentation. ALWAYS READ THE DOCUMENTATION FIRST.\n4. **Patterns:** Identify how similar features are implemented in ResizeMe\n\nUse official documentation and reputable sources. If uncertain about patterns, research before proposing.\n\nStop research at 80% confidence you can break down the feature into testable phases.\n\n\u003C\u002Fresearch_guide>\n",{"name":5,"description":7},"main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd","skills\u002Fstructured-autonomy-plan",5340,"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-11 13:41:32",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add github\u002Fawesome-copilot --skill structured-autonomy-plan",{"tool":51,"command":52},"bunx","bunx skills add github\u002Fawesome-copilot --skill structured-autonomy-plan",{"tool":54,"command":55},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill structured-autonomy-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002Fskills\u002Fstructured-autonomy-plan\u002FSKILL.md",true,[],[60,91,119,149,183,200],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":70,"publishedAt":30},"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",[66,69],{"categoryNo":67,"categoryName":68,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90],"supabase","rls","supabase rls","supabase rls policies","project","when","review","change","read","write","security","isolation","tables","as","tests","prove","use","users","functions","with",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":98,"publishedAt":30},"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",[97],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":131,"publishedAt":30},"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",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[132,133,134,135,136,137,105,75,138,139,140,141,142,143,144,87,145,146,147,148],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":160,"publishedAt":30},"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",[156,159],{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},[161,162,163,164,165,166,167,168,169,170,171,172,173,174,175,76,176,177,178,179,180,105,181,182],"winmd api search","search","api","windows","desktop","file access","enumeration","ui","ml","file","networking","capabilities","notifications","explore","access","features","full","camera","events","platform","methods","controls",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":187,"licenseFileUrl":188,"sourceHtmlUrl":189,"categories":190,"keywords":196,"publishedAt":30},"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",[191,192,195],{"categoryNo":157,"categoryName":158,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[197,102,170,198,199],"resemble detect","https","identity",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":187,"licenseFileUrl":204,"sourceHtmlUrl":205,"categories":206,"keywords":211,"publishedAt":30},"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",[207,210],{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[212,213,214,215,133,77,9,101,216,217,198,218,219,220,221,222,223,224,225,226,227,228,85,229,230,231,232],"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"]