Using Amazon Skills

Using Amazon Skills

Overview

This is the meta-skill: it describes how to navigate, select, and combine the other skills in this library. Use this when you're unsure which skill applies, when you need to understand how skills interact, or when you want to establish core operating behaviors that underpin all other skills. Think of this as the operating system on which individual skills run.

When to Use

• Starting a new project and wondering "what's the Amazon way?"
• Unsure which skill applies to your current situation
• Onboarding new team members to this way of working
• Wanting to establish core behaviors before diving into specific practices
• Assessing whether your team is following the overall system, not just individual parts

Amazon Context

Amazon doesn't have a single monolithic process—it has a collection of mechanisms, principles, and practices that compose together. The power comes from the composition: progressive deployment is effective because pipelines enforce safety gates, which work because alarms are set up correctly, which matter because the team operates the service they build. Remove one piece and the others weaken. This meta-skill helps you see the whole system.

Skill Routing Flow Chart

"I'm starting a new project"

Start → Working Backwards (define what customer needs)
      → Dependency Management (if external/system dependencies exist)
      → Feature Flag Lifecycle (if controlled exposure or kill switch is needed)
      → Operational Excellence (operational signals and runbooks)
      → Design Document (technical approach)
      → API Contract First (define interfaces)
      → Infrastructure as Code (define resources)
      → Operational Excellence (set up monitoring)
      → Progressive Deployment (ship safely)

"I'm writing/reviewing code"

Code change → Code Review Bar Raising (quality)
            → Test-Driven Development (coverage)
            → Pipeline Safety (automated gates)
            → Progressive Deployment (ship it)