Product skills

Newest skills

85 skills

onnx-opset-bump-checklist

Step-by-step checklist for bumping the pinned ONNX dependency / opset in ONNX Runtime (e.g. ONNX 1.21 / opset 26 → 1.22 / opset 27). Use when integrating a new ONNX release or release-candidate, updating the cmake/deps.txt onnx pin or the cmake/external/onnx submodule, regenerating cmake/patches/onnx/onnx.patch, raising kMaxSupportedOpset, or adding a new opset's CPU kernels. Covers the file taxonomy, archive-hash procedures, patch rebase/mirror rules, the RC→formal strategy, and the optimizer/EP gotchas that the automated audit script misses.

Strategy

0

0

rpi-review

Compare RPI planning and implementation evidence, record review findings, and route follow-up work. Use when an implementation needs acceptance review.

Strategy

0

0

rpi-plan

Create one evidence-based RPI implementation plan from supplied context, research, drafts, and decisions. Use when implementation planning is needed.

Strategy

0

0

rpi-plan-critique

Independently critique an RPI implementation plan once against supplied evidence without editing the plan. Use when planning credibility needs a read-only assessment.

Strategy

0

0

rpi-implement

Execute an approved RPI plan, maintain current planning state, and record implementation evidence. Use when implementation is ready to begin or resume.

Strategy

0

0

requirements-author

Requirements authoring guide for BRD and PRD across Discover, Define, and Govern with canonical templates and handoff contracts

Strategy

0

0

proposal-response

Build traceable internal-review proposal, RFI, RFP, tender, bid, and questionnaire responses from supplied questions and approved sources. Use to analyze questions, contribute business or product evidence, or draft qualified responses.

Strategy

0

0

setting-up-constitution

Creates or updates the project constitution that defines migration principles, constraints, and conventions. Triggers: "set up constitution", "define migration principles", "create project rules", "establish conventions", "establish migration constitution". NOT for: implementation, implementation planning, task generation.

Strategy

0

0

quality-gates

Runs quality gate validation at each workflow stage. Supports 4 gate types: spec-quality, spec-to-plan, plan-to-tasks, completeness. Produces gate pass/fail reports with actionable feedback. Triggers: "run quality gate", "validate spec quality", "spec quality", "plan coverage", "check plan coverage", "validate plan to tasks", "check task traceability", "verify task completeness", "run completeness review", "review implementation", "check plan traceability", "check coverage", "completeness quality gate", "final sign-off", "feature parity sign-off", "completeness gate", "feature parity", "sign-o

Strategy

0

0

project-decomposition

Single-source codebase decomposition: scans a project scope, builds the module dependency graph, counts LOC by language, computes skip patterns (caller-supplied ∪ .gitignore ∪ baseline), and (when grouping is required) produces topology groupings with L3 quality validation. One skill owns ProjectProfile JSON, grouping protocols, and quality gates. Triggers: "before generating a workflow plan", "before topology grouping", "project sizing", "LOC counting", "module grouping", "topology splitting rules", "topology consumer rules", "scale-aware splitting", "large codebase decomposition", "module de

Strategy

0

0

implementing-code

Executes a batch of implementation tasks with TDD workflow, source-anchored rewrite for behavioral fidelity, guideline-based code transformation, and full requirement tracing. Returns a structured batch report. Triggers: "implement tasks", "execute the batch", "write code for these tasks", "implement with source anchoring", "run the implementation". NOT for: task generation (use breaking-down-tasks), implementation planning (use creating-implementation-plan).

Strategy

0

0

creating-implementation-plan

Creates an implementation plan AND task breakdown from a feature spec by consuming design artifacts. Produces plan.md with implementation steps, inline task list with full REQ traceability, and a Requirement Mapping table. This is the single skill for planning + decomposition. Triggers: "create implementation plan", "plan for implementation", "assemble implementation plan", "generate plan from spec", "break down tasks", "generate tasks from plan", "create implementation tasks", "decompose the plan into work items". NOT for: architecture analysis (use analyzing-architecture), implementation (us

Planning

0

0

ghqr-report

Generate an executive assessment report from GitHub Quick Review (ghqr) scan data. Produces an executive summary, a dedicated section per validated subject with all findings, and a prioritized 30/60/90-day remediation plan. Use when the user asks for a report, executive summary, best practices posture overview, or a remediation roadmap from ghqr scan results.

Strategy

0

0

writing-plans

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

Planning

0

0

creating-skills

Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts

Strategy

0

0

schema-discovery

Explore Power BI semantic model schemas using DAX INFO functions. Progressive metadata discovery strategy, scope estimation, and narrowing techniques for tables, columns, measures, and relationships.

Strategy

0

0

work-brief

Build a prioritised morning work brief for Microsoft Scout from Outlook mail, calendar, and Teams chats - what the user owes people, what is blocked on others, what is coming up, and what to do first. Use this skill whenever the user asks for a morning brief, a Monday or weekly brief, a daily digest, a "what is waiting on me" or "what did I miss" summary, a catch-up after time off, a review of unresolved team threads or pending actions, a look at the week ahead, or wants to know who is blocking them - even if they never use the word "brief". Also use it when setting any of this up as a recurri

Strategy

0

0

holiday-recap

Return-from-leave catch-up briefing across Outlook mail, meetings and Teams. Asks which areas to cover and only the scoping questions those areas need, then reports each item once, deep-linked and prioritised. Suggests replies as text; creates drafts, sends, posts and meeting responses only on explicit approval. Use when the user says "prepare my holiday recap", "catch me up after my holiday", "what did I miss while I was away?", "return-from-leave briefing", or "catch me up between <date> and <date>". Do NOT use for a same-day catch-up (use daily-briefing), one meeting summary (use meeting-in

Strategy

0

0

content-quality-auditor

Use this skill when the user asks to assess, audit, score, review, improve, prioritise, or quality-check content, documents, pages, posts, decks, or reusable artefacts.

Strategy

0

0

boards-team-active-work

Get active work items for a team showing dependencies, priorities, and sprint assignments. Displays items that are blocking others, high priority items first, and items due this sprint. Shows parent/child hierarchy with Title, State, Priority, ChangedDate, Iteration Name, and Iteration End Date.

Strategy

0

0

boards-backlog-summary

Get the team's Requirements-level backlog (Product Backlog Items and Bugs) filtered to Active items assigned to the current user. Shows parent/child hierarchy and sorts by priority. Use this skill when the user wants to see their backlog items, sprint assignments, or work they own on a team board.

Strategy

0

0

oss-growth

Activate for OSS adoption work -- README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles -- and any update to the maintained growth strategy at WIP/growth-strategy.md.

Strategy

0

0

apm-strategy

Activate for changes to project positioning, release communication, community-facing artifacts, or breaking-change decisions in microsoft/apm. Triggers on README, MANIFESTO, PRD, CHANGELOG, release workflows, and issue templates.

Strategy

0

0

oss-growth

Activate for OSS adoption work -- README conversion surfaces, quickstart, templates, release announcements, contributor funnel, story angles -- and any update to the maintained growth strategy at WIP/growth-strategy.md.

Strategy

0

0