wa-review
Perform a full AWS Well-Architected Framework review evaluating all 57 questions across 6 pillars by analyzing code, IaC, and configurations to produce evidence-backed findings with Eisenhower-prioritized remediation.
Profile →npx skills add aws-samples/sample-well-architected-skills-and-steering --skill wa-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Well-Architected Review ## Step 1: Define the workload scope Ask the user to describe the workload: > What workload would you like me to review? Please share: > - **Workload name** and brief description > - **Code packages/directories** to analyze (IaC, application code, CI/CD configs) > - **Business criticality** (critical, high, standard, low) > - **Current pain points** (optional — anything you already know is problematic) If the user has already provided architecture details or you are in a codebase with IaC, skip the prompt and proceed with discovery. **IMPORTANT**: When no code or IaC is available to analyze (e.g., the user describes their architecture verbally), proceed with the review based on the information provided. Produce the full report using the architecture description as evidence. Mark findings where you cannot verify implementation details as "Based on description — verify in code." Do NOT ask for code if the user has already given you enough context to perform a meaningful review. Determine if a specialized WA Lens applies: - SaaS, Serverless, Data Analytics, Machine Learning, IoT, Containers, Games, Financial Services, Healthcare If a lens is obvious from the
- Step 1: Define the workload scope
- Step 2: Infrastructure Discovery
- Step 3: Application Architecture Discovery
- Step 4: Evaluate EVERY WA Framework question with code evidence
- Review depth
- Coverage strategy — MANIFEST-FIRST, THEN PILLAR FILES
- Mandatory loading pattern for a full review
- Step 4d — MANDATORY coverage audit (do NOT skip)
- When economy matters — quick review mode
- Pillar-scoped review
- When a WA Lens applies
- Step 5: Risk Assessment
- Step 6: Produce the report
- Step 7: Offer follow-up
What does the wa-review skill do?
Perform a full AWS Well-Architected Framework review evaluating all 57 questions across 6 pillars by analyzing code, IaC, and configurations to produce evidence-backed findings with Eisenhower-prioritized remediation.
How do I install it?
Run `npx skills add aws-samples/sample-well-architected-skills-and-steering --skill wa-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aws-samples/sample-well-architected-skills-and-steering, a repository with 233 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.