microsoft/amplifier-bundle-skills.

adapt-skill

>-

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.

bet-sizer

>-

bug-report

>-

council

>-

council-here

>-

councilify

>-

cranky-old-sam

>-

create-demo-video

>-

crusty-old-engineer

>-

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.

image-vision

>-

intent-keeper

>-

mass-change

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

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.

monitor

>-

outcome-cartographer

>-

outcomist

>-

personafy

>-

positioning-critic

>-

product-council

>-

product-council-here

>-

python-standards

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

restless-old-brian

>-

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.

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.

session-debug

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

skillify

>-

skills-assist

>-

tester-breaker

>-

user-advocate

>-

verification-discipline

>-