Create microsoft research plan

Skill PlagueHO/plagueho.copilot/skills/create-microsoft-research-plan

**WORKFLOW SKILL** — Generate a structured research plan for a Microsoft technology topic, defining scope, research areas, search terms, and output section mapping based on purpose (guide/presentation/lab/demo). WHEN: "create research plan", "plan Microsoft research", "research plan for", "plan technical research", "scope research topic", "define research areas". INVOKES: editFiles. FOR SINGLE OPERATIONS: Create plan.md manually.From its SKILL.md

Install

npx -y skills add PlagueHO/plagueho.copilot --skill create-microsoft-research-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.7 KB, as published. Nobody here has run it

Create Microsoft Research Plan

Generate a structured research plan for deep technical research on a Microsoft technology feature, architecture, or solution. The plan defines scope, research areas to investigate, search terms per area, and maps output sections based on the research purpose.

Prerequisites

A clear technology topic (e.g., "Azure Container Apps dynamic sessions")
A defined purpose: deep-guide, presentation, lab, or demo

Process

Step 1 — Confirm Topic and Purpose

If the user has not specified both a topic and purpose, ask:

Topic: Which Microsoft technology, feature, architecture, or solution?
Purpose: What is the research for?
- deep-guide — comprehensive technical reference
- presentation — tech talk or demo deck
- lab — hands-on workshop exercises
- demo — sample solution or proof-of-concept

Derive a kebab-case topic slug for the folder name (e.g., azure-container-apps-dynamic-sessions).

Step 2 — Load Taxonomy and Purpose Mapping

Read taxonomy.md to understand all available research dimensions.

Read purpose-mapping.yaml to determine which dimensions and output sections apply for the chosen purpose.

Step 3 — Generate Search Terms

For each research area enabled by the purpose mapping, generate specific search terms based on the topic:

Area	Search Term Pattern
`docs`	`"<topic> overview"`, `"<topic> documentation"`, `"<topic> concepts"`
`tech`	`"<topic> SDK"`, `"<topic> API reference"`, `"<topic> configuration"`
`blogs`	`"<topic> announcement"`, `"<topic> what's new"`, `"<topic> preview"`
`arch`	`"<topic> architecture"`, `"<topic> best practices"`, `"<topic> patterns"`
`samples`	`"<topic> sample"`, `"<topic> quickstart"`, `"<topic> tutorial"`
`solutions`	`"<topic> solution accelerator"`, `"<topic> reference implementation"`
`other`	`"<topic> community"`, `"<topic> comparison"`, `"<topic> real-world"`

Use service-specific terminology.

Step 4 — Write plan.md

Write the plan to .research/<topic-slug>/plan.md using the template at plan-template.md.

Fill in all sections:

Topic and boundaries
Purpose and target audience
Research areas enabled (with search terms per area)
Expected output sections (from purpose mapping)
Estimated source count targets per area

Step 5 — Present Plan for Confirmation

Show the user:

Topic slug and folder path
Purpose and enabled dimensions
Research areas with search terms
Expected output sections

Ask: "Does this plan look correct? Adjust scope, research areas, or search terms if needed."

Output

The plan at .research/<topic-slug>/plan.md is the contract for the orchestrator and all subagents.