architectureUse when asked for high-level architecture documentation or a big-picture review: interfaces, data flows, contracts, failure modes, and accessible Mermaid diagrams. Writes documentation only; never changes code or tests. upstream: https://github.com/github/awesome-copilot/blob/main/agents/hlbpa.agen
researchUse when asked to validate a technical spike document through exhaustive, recursive research; it mines documentation, analyzes code patterns, runs experiments with permission, and continuously updates the spike with structured findings.
sequenceSequence a multi-file change: map every affected file, trace dependencies, and emit an ordered edit plan before any code is touched. File-level ordering, not strategy — use planning:strategy to choose what to build. upstream: https://github.com/github/awesome-copilot/blob/main/agents/context-archite
strategyStrategic pre-code planning for a single feature or goal: explore the codebase, weigh approaches with trade-offs, and recommend an implementation strategy with risks and open questions. Reason, not sequence — use planning:sequence for a file-by-file edit order. upstream: https://github.com/github/aw