microsoft/amplifier-bundle-skills

second-opinion

Independent review of current work or a past session. USE WHEN a user wants a second opinion. DO NOT USE WHEN ordinary code review is wanted — use code-review.

bug-report

Investigate a defect and write an evidence-backed maintainer report. USE WHEN asked to file a bug, report an issue, investigate and report, or write a defect up for devs. DO NOT USE WHEN only a fix or direct debugging is wanted — use the normal debugging…

create-demo-video

Produce a narrated demo video that shows something the user made or built, cut from recordings they supply or recordings made to their direction. Use when showing a product, feature, tool, or project in action, including explainers built around a live demo.…

adapt-skill

Adapt a skill written for another AI assistant (OpenAI Codex, ChatGPT, Claude Code, Cursor) into a proper Amplifier SKILL.md. Use when the user wants to adapt a skill, port a skill, convert a skill to amplifier, translate a skill, or has a SKILL.md from…

skills-assist

Authoritative consultant for all skills-related questions. Use when creating or modifying skills, understanding the Agent Skills spec, troubleshooting skill loading or invocation issues, leveraging enhanced format features (context fork, model_role,…

councilify

Build a NEW complete "council" for a domain — a panel of orthogonal review lenses that fan out cold, debate to consensus, and return a synthesized verdict with recorded dissent, exactly like /council and /design-council. Identifies the distinct lenses a…

retrospective

Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for code review or transcript replay.

personafy

Build a new opinionated advisor-persona skill — a reviewer "lens" like crusty-old-engineer, modeled on a real person or archetype. Mines the subject's authentic voice, defines its one load-bearing question, drafts it to the family template, and proves it…

skillify

Capture a repeatable process from the current session into a reusable Amplifier SKILL.md skill file. Use when the user wants to create a skill, save a workflow as a skill, turn a process into a reusable skill, or mentions "skillify", "create skill", "make a…

bet-sizer

Delivery-risk reviewer that sizes a plan's investment against the team's real confidence it will land. Voice of a delivery lead who has watched too many "should be straightforward" estimates blow up on the one unknown nobody named. Use at any product…

cranky-old-sam

Simplicity-obsessed reviewer that interrogates complexity and insists on the minimal viable design. Voice of a senior engineer who treats every unnecessary layer as a personal affront. Use at any checkpoint — brainstorm, design, plan, implement, debug, review…

crusty-old-engineer

Curmudgeonly engineering advisor: grounded skepticism and evidence-linked judgment on architecture, legacy refactors, and tooling choices. Voice of a senior systems engineer who has reviewed too many designs to be impressed but still cares about correctness.…

engineering-patterns

Use for tool/service work: CLI packaging, installers, config/state, HTTP, auth/TLS, file IPC, plugins, instance storage, containers, React MFE, Graph, self-update, tool leverage.

intent-keeper

Goal-clarity reviewer that refuses to judge a solution until the intent behind it is pinned. A patient interrogator of "why are we doing this?", hunting goal drift — the deliverable quietly replacing the goal. Use at any checkpoint — brainstorm, design, plan,…

outcome-cartographer

Outcome-validity reviewer that refuses to count shipped work as progress until it maps to a measurable change in behavior. Hunts the gap between "we shipped it" and "we moved the number" — the output mistaken for an outcome. Use at any product checkpoint —…

outcomist

Outcome-clarity reviewer that asks whether you have defined what you're trying to achieve and validated that the problem is real. Catches people BEFORE they build — the moment between "I should build X" and actually building it. Use when a build is starting…

positioning-critic

Competitive-differentiation reviewer that refuses to accept "the user wants this" as sufficient. Demands the plan say why a real customer would choose it over every alternative, including doing nothing — voice of a positioning strategist who has watched…

user-advocate

User-need reviewer that speaks for the person who isn't in the room — the one who will actually live with what gets built. Hunts the gap between "we can build this" and "they actually want this," in the patient, impatient voice of the absent user. Use at any…

council-here

Convene the persona panel on the CURRENT conversation — the plan, design, or decision built in this session. The INLINE counterpart to /council (which forks isolated and cannot see the chat). Use when you want the council to critique what we're working on…

council

Convene the persona panel — six orthogonal review lenses — on a target. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.

image-vision

Analyze images using LLM vision APIs (Anthropic Claude, OpenAI GPT-4, Google Gemini, Azure OpenAI). Use when a task requires understanding image content, describing visual elements, answering questions about images, comparing images, or extracting text from…

monitor

Run a bounded, self-checking polling loop (sleep -> check -> decide, repeat) WITHOUT ENDING THE TURN. The turn ends only when the watched thing is done, has failed, or genuinely needs the user's attention — which is what makes Amplifier's end-of-turn…

product-council-here

Convene the Product Development Council on the CURRENT conversation — the plan, roadmap, or scope decision built in this session. The INLINE counterpart to /product-council (which forks isolated and cannot see the chat). Use when you want the council to…

product-council

Convene the Product Development Council — six orthogonal product-delivery lenses anchored by a mandatory problem-validation gate. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.

restless-old-brian

Momentum-driven engineering reviewer holding one uncompromising gate: is it REAL, proven end-to-end as a user would? Warm, blunt, forward-driving — proof over claims, plumbing before polish, fail-loud over fallbacks, trust in the model over instructions,…

tester-breaker

Adversarial breaker that reviews code by trying to make it fail, not by confirming it works. Hunts the unhappy paths — malformed input, the empty string, the reversed range, the race condition — as a gleeful adversary who assumes everything is broken until a…

verification-discipline

Use when verifying that completed work actually works. Auto-surface during /verify mode, post-implementation review, or before claiming a task is done. Teaches testing outcomes vs implementation, the unit/integration/smoke gradient, and what "done" actually…

mass-change

Research and plan a large-scale change, then execute it in parallel across isolated agents that each open a PR.

session-debug

Diagnose issues in the current Amplifier session — misconfigured tools, failing operations, unexpected behavior. Use when something isn't working right.

amplifier-philosophy

Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles. Use when designing new modules or making architectural decisions.

module-development

Guide for creating new Amplifier modules including protocol implementation, entry points, mount functions, and testing patterns. Use when creating new modules or understanding module architecture.

python-standards

Python coding standards for Amplifier including type hints, async patterns, error handling, and formatting. Use when writing Python code for Amplifier modules.

code-review

Review changed code for reuse, quality, and efficiency, then fix any issues found.