[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M69AGE091B91EYCXRHWNNQZF":3,"skill-same:01M69AGE091B91EYCXRHWNNQZF":61},{"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":18,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M69AGE091B91EYCXRHWNNQZF","brainstorming",null,"IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation","microsoft\u002FFluidFramework","microsoft","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6154722?v=4","01M698VYDXZ6JW5WH3CRV650R8","Microsoft","01M69AG0BQKNGBJQ5YNG09HXXW",4948,"MIT","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fbrainstorming\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31],"writing","code","validation","develop","use","implementation","exploration","ideas","structured","plans","socratic","socratic questioning","when","2026-11-10 10:12:30",false,"---\nname: brainstorming\ndescription: IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation\n---\n\n# Brainstorming Ideas Into Designs\n\n## Overview\n\nTransform rough ideas into fully-formed designs through structured questioning and alternative exploration.\n\n**Core principle:** Ask questions to understand, explore alternatives, present design incrementally for validation.\n\n**Announce at start:** \"I'm using the Nori Brainstorming skill to refine your idea into a design.\"\n\n## The Process\n\n### Phase 1: Understanding\n\n- Check current project state in working directory\n- Ask ONE question at a time to refine the idea\n- Prefer multiple choice when possible\n- Gather: Purpose, constraints, success criteria\n\n### Phase 2: Exploration\n\n- Propose 2-3 different approaches\n- For each: Core architecture, trade-offs, complexity assessment\n- Ask your human partner which approach resonates\n\n### Phase 3: Design Presentation\n\n- Present in 200-300 word sections\n- Cover: Architecture, components, data flow, error handling, testing\n- Ask after each section: \"Does this look right so far?\"\n\n### Phase 4: Worktree Setup (for implementation)\n\nWhen design is approved and implementation will follow:\n\n- Announce: \"I'm using the Using Git Worktrees skill to set up an isolated workspace.\"\n- Switch to `.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fusing-git-worktrees`\n- Follow that skill's process for directory selection, safety verification, and setup\n- Return here when worktree ready\n\n### Phase 5: Planning Handoff\n\nAsk: \"Ready to create the implementation plan?\"\n\nWhen your human partner confirms (any affirmative response):\n\n- Announce: \"I'm using the Writing Plans skill to create the implementation plan.\"\n- Switch to the `.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fwriting-plans` skill\n- Create detailed plan in the worktree\n\n## When to Revisit Earlier Phases\n\n**You can and should go backward when:**\n\n- Partner reveals new constraint during Phase 2 or 3 → Return to Phase 1 to understand it\n- Validation shows fundamental gap in requirements → Return to Phase 1\n- Partner questions approach during Phase 3 → Return to Phase 2 to explore alternatives\n- Something doesn't make sense → Go back and clarify\n\n**Don't force forward linearly** when going backward would give better results.\n\n## Remember\n\n- One question per message during Phase 1\n- Apply YAGNI ruthlessly\n- Explore 2-3 alternatives before settling\n- Present incrementally, validate as you go\n- Go backward when needed - flexibility > rigid progression\n- Announce skill usage at start\n","# Brainstorming Ideas Into Designs\n\n## Overview\n\nTransform rough ideas into fully-formed designs through structured questioning and alternative exploration.\n\n**Core principle:** Ask questions to understand, explore alternatives, present design incrementally for validation.\n\n**Announce at start:** \"I'm using the Nori Brainstorming skill to refine your idea into a design.\"\n\n## The Process\n\n### Phase 1: Understanding\n\n- Check current project state in working directory\n- Ask ONE question at a time to refine the idea\n- Prefer multiple choice when possible\n- Gather: Purpose, constraints, success criteria\n\n### Phase 2: Exploration\n\n- Propose 2-3 different approaches\n- For each: Core architecture, trade-offs, complexity assessment\n- Ask your human partner which approach resonates\n\n### Phase 3: Design Presentation\n\n- Present in 200-300 word sections\n- Cover: Architecture, components, data flow, error handling, testing\n- Ask after each section: \"Does this look right so far?\"\n\n### Phase 4: Worktree Setup (for implementation)\n\nWhen design is approved and implementation will follow:\n\n- Announce: \"I'm using the Using Git Worktrees skill to set up an isolated workspace.\"\n- Switch to `.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fusing-git-worktrees`\n- Follow that skill's process for directory selection, safety verification, and setup\n- Return here when worktree ready\n\n### Phase 5: Planning Handoff\n\nAsk: \"Ready to create the implementation plan?\"\n\nWhen your human partner confirms (any affirmative response):\n\n- Announce: \"I'm using the Writing Plans skill to create the implementation plan.\"\n- Switch to the `.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fwriting-plans` skill\n- Create detailed plan in the worktree\n\n## When to Revisit Earlier Phases\n\n**You can and should go backward when:**\n\n- Partner reveals new constraint during Phase 2 or 3 → Return to Phase 1 to understand it\n- Validation shows fundamental gap in requirements → Return to Phase 1\n- Partner questions approach during Phase 3 → Return to Phase 2 to explore alternatives\n- Something doesn't make sense → Go back and clarify\n\n**Don't force forward linearly** when going backward would give better results.\n\n## Remember\n\n- One question per message during Phase 1\n- Apply YAGNI ruthlessly\n- Explore 2-3 alternatives before settling\n- Present incrementally, validate as you go\n- Go backward when needed - flexibility > rigid progression\n- Announce skill usage at start\n",{"name":5,"description":7},"main","8809386f7af487f40be7dcbea5d0e4afc37efd0a",".agency\u002Fplugins\u002Fnori\u002Fskills\u002Fbrainstorming",590,"https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework","https:\u002F\u002Ffluidframework.com","https:\u002F\u002Fgithub.com\u002Fmicrosoft","https:\u002F\u002Fopensource.microsoft.com","Open source projects and samples from Microsoft","2026-11-13 02:46:12",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add microsoft\u002FFluidFramework --skill brainstorming",{"tool":53,"command":54},"bunx","bunx skills add microsoft\u002FFluidFramework --skill brainstorming",{"tool":56,"command":57},"pnpm","pnpm dlx skills add microsoft\u002FFluidFramework --skill brainstorming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.agency\u002Fplugins\u002Fnori\u002Fskills\u002Fbrainstorming\u002FSKILL.md",true,[],[62,83,121,145,163,186],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":32},"01M6PJ5SAHYFZFWDG5Y4RW56EP","trigger-pipelines-for-copilot-pr","Trigger ADO pipelines for a Copilot-created PR by posting \u002Fazp run comments. Use when the user asks to trigger CI pipelines for a specific PR.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftrigger-pipelines-for-copilot-pr\u002FSKILL.md",[],[69,70,71,72,73,74,75,76,77,78,23,79,80,81,82,31],"pr","trigger pipelines for copilot pr","for","trigger","copilot","pipelines","ado","posting","run","ci","number","URL","comments","user",{"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":102,"publishedAt":32},"01M6PJ5M4ZG7E78C4GM4041HEP","review","Review changes relative to a prior state, such as a diff, pull request, branch, commit, or working-tree changes. Use for change-focused code review and regression analysis. Do not use to assess an existing file, API, design, implementation, or other artifact without a comparison; if the request is ambiguous, ask whether the user wants a change review and what prior state to compare against.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freview\u002FSKILL.md",[89,94,97],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":95,"categoryName":96,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[85,103,104,105,106,107,108,20,109,110,111,112,113,114,115,116,117,118,71,119,120],"branch","regression","code review","design","ask","analysis","commit","api","change","artifact","request","pull","tree","as","do","diff","assess","ambiguous",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":130,"publishedAt":32},"01M6PJ5E3PCBDS319FFMHPFACN","review-pr-local","The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored review prose the human did not ask for, invoke this skill instead.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Freview-pr-local\u002FSKILL.md",[127],{"categoryNo":128,"categoryName":129,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发",[131,85,69,132,133,134,103,135,136,137,138,139,140,141,80,142,107,110,143,144],"local","review pr local","review pr","back","posts","only","MCP","authority","auto","invoke","azure devops","you","cli","worktree",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":32},"01M6PJ5AVZAS0AEBPCYJZ9ZMMD","policy-check","This skill should be used when the user asks to \"run policy check\", \"check policy\", \"policy-check\", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpolicy-check\u002FSKILL.md",[],[152,153,154,155,156,71,77,157,158,159,160,82,161,31,162],"policy check","policy","check","packages","compliance","repository","guidance","validate","package","running","entire",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":172,"publishedAt":32},"01M6PJ54H068MZF2WD2JDKCVDC","pipeline-test-triage","Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build\u002Fpipeline URL or build ID and wants failures analyzed, when they ask \"why did this pipeline fail\", \"summarize the test failures\", \"is this test flaky or a real bug\", \"compare these runs\", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fpipeline-test-triage\u002FSKILL.md",[169],{"categoryNo":170,"categoryName":171,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000008","测试与质量",[173,174,175,176,177,178,179,180,141,80,107,77,181,182,183,184,75,116,185,71,31],"pipeline","test triage","pipeline test triage","pipeline test","test","triage","end","test pipeline","why","bug","but","framework","bugs",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":192,"publishedAt":32},"01M6PJ4ZJASDV2CGQTG1JWKBFE","fluid-release","Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on \"release\", \"do the release\", \"release status\", version bump, release notes, changelog, release branch, or release engineering.","https:\u002F\u002Fgithub.com\u002Fmicrosoft\u002FFluidFramework\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffluid-release\u002FSKILL.md",[],[193,194,195,134,103,196,197,198,199,200,139,201,202,203,204,205,206,207,208,209],"release","fluid release","fluid","bump","mode","autonomous","release notes","release status","updates","patch","notes","changelog","release prep","releases","status","issue","branching"]