[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD3X0RQ80BSQSP8CBWPE60":3,"skill-same:01M6AD3X0RQ80BSQSP8CBWPE60":82},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6AD3X0RQ80BSQSP8CBWPE60","create-canvas-extension",null,"Create or register a canvas extension in the awesome-copilot repository. Use when asked to scaffold a new canvas extension, create its plugin.json, add a reusable extension to one or more plugins, or migrate extension metadata. Extensions are reusable source under extensions\u002F; shippable plugin manifests belong under plugins\u002F.","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\u002F.github\u002Fskills\u002Fcreate-canvas-extension\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"create canvas","canvas","create","create canvas extension","extension","new","when","manifests","extensions","more","register","name","reusable","use","json","migrate","repository","plugins","metadata","plugin","copilot","scaffold","2026-11-10 10:12:30",false,"---\nname: create-canvas-extension\ndescription: 'Create or register a canvas extension in the awesome-copilot repository. Use when asked to scaffold a new canvas extension, create its plugin.json, add a reusable extension to one or more plugins, or migrate extension metadata. Extensions are reusable source under extensions\u002F; shippable plugin manifests belong under plugins\u002F.'\nargument-hint: '[optional extension name or description]'\n---\n\n# Create a canvas extension\n\nUse this skill only for the `github\u002Fawesome-copilot` repository. Canvas extensions are reusable source components. They do not have a `plugin.json` under `extensions\u002F`.\n\n## Required decisions\n\nBefore creating files, ask for each missing value:\n\n1. **Extension ID**: lowercase kebab-case, matching the source folder and plugin name.\n2. **Display metadata**:\n   - description\n   - version (default `1.0.0`)\n   - author name and optional URL\n   - keywords (lowercase, hyphenated, maximum 10)\n   - repository and license (default to the repository URL and `MIT` when appropriate)\n3. **Canvas entrypoint**: confirm whether the extension already has `extension.mjs`. If not, create a minimal entrypoint only when the user provides enough implementation details; otherwise create the directory and leave an explicit TODO.\n4. **Preview image**: obtain an existing `assets\u002Fpreview.png` path or ask the user to add it. Do not invent a binary image or silently use a misleading placeholder.\n5. **Plugin registration**:\n   - For a standalone installable canvas plugin, create `plugins\u002F\u003Cextension-id>`.\n   - For an extension that belongs to an existing plugin, ask for the parent plugin ID and add `.\u002Fextensions\u002F\u003Cextension-id>` to that plugin's `extensions.com.github.awesome-copilot.extensions`.\n   - If the extension should be shipped by multiple plugins, collect all plugin IDs and add the same extension ID to each mapping file.\n\n## Files to create\n\nFor a new extension plugin, create this structure:\n\n```text\nextensions\u002F\u003Cextension-id>\u002F\n├── extension.mjs\n└── assets\u002F\n    └── preview.png\n\nplugins\u002F\u003Cextension-id>\u002F\n├── plugin.json\n└── README.md\n```\n\nThe extension source may contain additional files such as `package.json`, canvas assets, or supporting modules. Keep all reusable implementation files under `extensions\u002F\u003Cextension-id>\u002F`.\n\nCreate `plugins\u002F\u003Cextension-id>\u002Fplugin.json` with this shape:\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Fagent-plugins.org\u002Fschemas\u002F1.0.0\u002Fplugin.schema.json\",\n  \"name\": \"\u003Cextension-id>\",\n  \"description\": \"\u003Cdescription>\",\n  \"version\": \"1.0.0\",\n  \"author\": {\n    \"name\": \"\u003Cauthor>\"\n  },\n  \"repository\": \"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\",\n  \"license\": \"MIT\",\n  \"keywords\": [\n    \"\u003Ckeyword>\"\n  ],\n  \"extensions\": {\n    \"com.github.copilot\": {\n      \"logo\": \"assets\u002Fpreview.png\"\n    },\n    \"com.github.awesome-copilot\": {\n      \"extensions\": [\n        \".\u002Fextensions\u002F\u003Cextension-id>\"\n      ]\n    }\n  }\n}\n```\n\nKeep Agent Plugins fields at the manifest top level. Repository composition belongs only under `extensions.com.github.awesome-copilot`; do not put `agents`, `commands`, `hooks`, or `skills` at the top level or directly under `extensions`. MCP servers are declared in `mcp.json` at the plugin root, never in `plugin.json`. Do not add `x-awesome-copilot`, `standalone`, or other repository-specific top-level fields.\n\nFor an existing parent plugin, create or update:\n\n```text\nplugins\u002F\u003Cparent-plugin>\u002Fplugin.json (`extensions.com.github.awesome-copilot.extensions`)\n```\n\nIts `extensions` property must contain sorted repository-relative paths:\n\n```json\n{\n  \"extensions\": [\n    \".\u002Fextensions\u002F\u003Cextension-id>\"\n  ]\n}\n```\n\nDo not copy the extension source into the parent plugin. Materialization resolves the IDs from the root `extensions\u002F` directory, so the same source can be bundled by multiple plugins.\n\n## Workflow\n\n1. Inspect the repository before editing:\n   - confirm `extensions\u002F\u003Cextension-id>` and `plugins\u002F\u003Cextension-id>` do not already conflict\n   - inspect the target parent plugin, if any\n   - check whether a preview image and entrypoint already exist\n2. Ask only the missing required questions from the decisions above.\n3. Create the source and plugin directories with the required files.\n4. If creating a new entrypoint, keep it minimal and clearly mark implementation TODOs rather than fabricating behavior.\n5. Add or update `extensions.com.github.awesome-copilot.extensions` for every parent plugin that should ship the extension. Keep paths alphabetically sorted and unique.\n6. Ensure there is no `extensions\u002F\u003Cextension-id>\u002F.github\u002Fplugin\u002Fplugin.json`.\n7. Run:\n\n   ```bash\n   npm run plugin:validate\n   npm run build\n   npm run website:data\n   ```\n\n8. Report the created paths, the plugins that ship the extension, and any missing user-provided assets or TODOs.\n\n## Existing extension migration\n\nWhen migrating an existing extension:\n\n1. Move its existing manifest to `plugins\u002F\u003Cextension-id>\u002Fplugin.json`.\n2. Update the manifest to the namespace-based `extensions.com.github.copilot.logo` shape.\n3. Remove the old manifest from `extensions\u002F\u003Cextension-id>`.\n4. Register the extension in any parent plugin's `extensions.com.github.awesome-copilot.extensions`.\n5. Run the validation and build commands above.\n","# Create a canvas extension\n\nUse this skill only for the `github\u002Fawesome-copilot` repository. Canvas extensions are reusable source components. They do not have a `plugin.json` under `extensions\u002F`.\n\n## Required decisions\n\nBefore creating files, ask for each missing value:\n\n1. **Extension ID**: lowercase kebab-case, matching the source folder and plugin name.\n2. **Display metadata**:\n   - description\n   - version (default `1.0.0`)\n   - author name and optional URL\n   - keywords (lowercase, hyphenated, maximum 10)\n   - repository and license (default to the repository URL and `MIT` when appropriate)\n3. **Canvas entrypoint**: confirm whether the extension already has `extension.mjs`. If not, create a minimal entrypoint only when the user provides enough implementation details; otherwise create the directory and leave an explicit TODO.\n4. **Preview image**: obtain an existing `assets\u002Fpreview.png` path or ask the user to add it. Do not invent a binary image or silently use a misleading placeholder.\n5. **Plugin registration**:\n   - For a standalone installable canvas plugin, create `plugins\u002F\u003Cextension-id>`.\n   - For an extension that belongs to an existing plugin, ask for the parent plugin ID and add `.\u002Fextensions\u002F\u003Cextension-id>` to that plugin's `extensions.com.github.awesome-copilot.extensions`.\n   - If the extension should be shipped by multiple plugins, collect all plugin IDs and add the same extension ID to each mapping file.\n\n## Files to create\n\nFor a new extension plugin, create this structure:\n\n```text\nextensions\u002F\u003Cextension-id>\u002F\n├── extension.mjs\n└── assets\u002F\n    └── preview.png\n\nplugins\u002F\u003Cextension-id>\u002F\n├── plugin.json\n└── README.md\n```\n\nThe extension source may contain additional files such as `package.json`, canvas assets, or supporting modules. Keep all reusable implementation files under `extensions\u002F\u003Cextension-id>\u002F`.\n\nCreate `plugins\u002F\u003Cextension-id>\u002Fplugin.json` with this shape:\n\n```json\n{\n  \"$schema\": \"https:\u002F\u002Fagent-plugins.org\u002Fschemas\u002F1.0.0\u002Fplugin.schema.json\",\n  \"name\": \"\u003Cextension-id>\",\n  \"description\": \"\u003Cdescription>\",\n  \"version\": \"1.0.0\",\n  \"author\": {\n    \"name\": \"\u003Cauthor>\"\n  },\n  \"repository\": \"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\",\n  \"license\": \"MIT\",\n  \"keywords\": [\n    \"\u003Ckeyword>\"\n  ],\n  \"extensions\": {\n    \"com.github.copilot\": {\n      \"logo\": \"assets\u002Fpreview.png\"\n    },\n    \"com.github.awesome-copilot\": {\n      \"extensions\": [\n        \".\u002Fextensions\u002F\u003Cextension-id>\"\n      ]\n    }\n  }\n}\n```\n\nKeep Agent Plugins fields at the manifest top level. Repository composition belongs only under `extensions.com.github.awesome-copilot`; do not put `agents`, `commands`, `hooks`, or `skills` at the top level or directly under `extensions`. MCP servers are declared in `mcp.json` at the plugin root, never in `plugin.json`. Do not add `x-awesome-copilot`, `standalone`, or other repository-specific top-level fields.\n\nFor an existing parent plugin, create or update:\n\n```text\nplugins\u002F\u003Cparent-plugin>\u002Fplugin.json (`extensions.com.github.awesome-copilot.extensions`)\n```\n\nIts `extensions` property must contain sorted repository-relative paths:\n\n```json\n{\n  \"extensions\": [\n    \".\u002Fextensions\u002F\u003Cextension-id>\"\n  ]\n}\n```\n\nDo not copy the extension source into the parent plugin. Materialization resolves the IDs from the root `extensions\u002F` directory, so the same source can be bundled by multiple plugins.\n\n## Workflow\n\n1. Inspect the repository before editing:\n   - confirm `extensions\u002F\u003Cextension-id>` and `plugins\u002F\u003Cextension-id>` do not already conflict\n   - inspect the target parent plugin, if any\n   - check whether a preview image and entrypoint already exist\n2. Ask only the missing required questions from the decisions above.\n3. Create the source and plugin directories with the required files.\n4. If creating a new entrypoint, keep it minimal and clearly mark implementation TODOs rather than fabricating behavior.\n5. Add or update `extensions.com.github.awesome-copilot.extensions` for every parent plugin that should ship the extension. Keep paths alphabetically sorted and unique.\n6. Ensure there is no `extensions\u002F\u003Cextension-id>\u002F.github\u002Fplugin\u002Fplugin.json`.\n7. Run:\n\n   ```bash\n   npm run plugin:validate\n   npm run build\n   npm run website:data\n   ```\n\n8. Report the created paths, the plugins that ship the extension, and any missing user-provided assets or TODOs.\n\n## Existing extension migration\n\nWhen migrating an existing extension:\n\n1. Move its existing manifest to `plugins\u002F\u003Cextension-id>\u002Fplugin.json`.\n2. Update the manifest to the namespace-based `extensions.com.github.copilot.logo` shape.\n3. Remove the old manifest from `extensions\u002F\u003Cextension-id>`.\n4. Register the extension in any parent plugin's `extensions.com.github.awesome-copilot.extensions`.\n5. Run the validation and build commands above.\n",{"name":5,"description":7,"argument-hint":51},"[optional extension name or description]","main","5269f7ea2d6c3a9bfda5ed878b6726cf509121fd",".github\u002Fskills\u002Fcreate-canvas-extension",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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add github\u002Fawesome-copilot --skill create-canvas-extension",{"tool":68,"command":69},"bunx","bunx skills add github\u002Fawesome-copilot --skill create-canvas-extension",{"tool":71,"command":72},"pnpm","pnpm dlx skills add github\u002Fawesome-copilot --skill create-canvas-extension","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fawesome-copilot\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcreate-canvas-extension\u002FSKILL.md",true,[76],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"core-bare-fix.md","REFERENCE","参考文档",778,"https:\u002F\u002Fgithub.com\u002Fviktomas\u002Fdotfiles\u002Fblob\u002Fmaster\u002Fpi\u002F.pi\u002Fagent\u002Fpurge\u002Fskills\u002Fgit-worktree\u002Fcore-bare-fix.md",[83,114,142,172,206,223],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":95,"publishedAt":46},"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",[89,92],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[96,97,98,99,100,30,101,102,103,104,105,106,107,108,109,110,37,111,112,113],"supabase","rls","supabase rls","supabase rls policies","project","review","change","read","write","security","isolation","tables","as","tests","prove","users","functions","with",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":46},"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",[120],{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},[122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141],"distribution","skill distribution audit","audit","SET","deterministic","installer","for","discovery","comparison","helper","manifest","version","collection","drift","output","investigate","duplicate","template","release","reconcile",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":146,"sourceHtmlUrl":147,"categories":148,"keywords":154,"publishedAt":46},"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",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[155,156,157,158,159,160,128,100,161,162,163,164,165,166,167,37,168,169,170,171],"custom","code","logicapps custom code net10 migration","migration","projects","standalone","deployment","applications","local","azure","worker","upgrades","package","apps","Legacy","debugging","workflows",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":176,"sourceHtmlUrl":177,"categories":178,"keywords":183,"publishedAt":46},"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",[179,182],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},[184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,30,199,200,201,202,203,128,204,205],"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":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":210,"licenseFileUrl":211,"sourceHtmlUrl":212,"categories":213,"keywords":219,"publishedAt":46},"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",[214,215,218],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":216,"categoryName":217,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},[220,125,193,221,222],"resemble detect","https","identity",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":210,"licenseFileUrl":227,"sourceHtmlUrl":228,"categories":229,"keywords":234,"publishedAt":46},"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",[230,233],{"categoryNo":231,"categoryName":232,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":93,"categoryName":94,"taxonomyType":21,"taxonomyTypeDesc":22},[235,236,237,238,156,101,9,124,239,240,221,241,242,243,244,245,246,247,248,249,250,251,109,252,253,254,255],"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"]