opensite-ai/opensite-skills / aws-well-architected-review
aws-well-architected-review
VerifiedPerforms a full AWS Well-Architected Framework review evaluating every framework question across all pillars discovered from the live AWS documentation by analyzing code, IaC, and configurations to produce evidence-backed findings with Eisenhower-prioritized remediation. Supports full reviews (every framework best practice with BP ID citations), quick reviews (question-level), pillar-scoped reviews, and lens-specific reviews using lenses discovered from the live AWS documentation. Triggers on mentions of Well-Architected review, WA review, WAR, WAFR, pillar assessment, architecture review, workload assessment, or cloud readiness evaluation. Does not apply to learning WA concepts without assessing a workload, ADRs, or migration readiness assessments.
| File | Kind | Size |
|---|---|---|
| .aws-skill-metadata | other | 18 B |
| SKILL.md | skill md | 12.5 KB |
| assets/report-template.md | markdown | 6.6 KB |
| references/discovery-procedure.md | markdown | 3.5 KB |
| references/evaluation-procedure.md | markdown | 11.8 KB |
| references/lens-guidance.md | markdown | 2.1 KB |
| references/phase-live-inventory.md | markdown | 11.3 KB |
| references/review-modes.md | markdown | 3.1 KB |
| references/risk-assessment.md | markdown | 1.6 KB |
| references/security-considerations.md | markdown | 5.4 KB |
assets/report-template.md
View on GitHub# Report Template — Full Well-Architected Review
Produce the final report with this exact structure. Do not drop sections. The Coverage audit (defined in the evaluation procedure reference) goes immediately before the Executive Summary.
```markdown
# Well-Architected Review: {Workload Name}
> **Classification: CONFIDENTIAL** — This report contains sensitive infrastructure details and unremediated security findings. Restrict distribution to authorized personnel. Do not post to broadly visible channels or ticketing systems without explicit approval.
## Coverage Audit
{Coverage audit output from Step 5d — see the evaluation procedure reference}
## Executive Summary
- **Date**: {date}
- **Workload**: {name}
- **Business Criticality**: {level}
- **Lens Applied**: {lens or "General"}
- **Packages Analyzed**: {list}
- **Questions Assessed**: {n}/{n per live documentation}
- **Findings**: {X} Critical, {Y} High, {Z} Medium, {W} Low
- **Overall Maturity**: {1-5} — {one-line justification}
## Architecture Overview
{PlantUML diagram}
{Brief description of architecture, key services, data flows}
## Pillar Scorecard
| Pillar | Score (1-5) | Questions Assessed | Key Strength | Key Gap |
|--------|-------------|-------------------|--------------|---------|
| {pillar from live inventory} | {score} | {n}/{n} | {strength} | {gap} |
| ...one row per discovered pillar... | ... | ... | ... | ... |
{Denominators come from the Step 5a question inventory — use the live counts recorded in corpus/manifest.json}
## Per-Question Assessment
| ID | Question | Status | Risk Level | Key Evidence |
|----|----------|--------|------------|--------------|
| {question ID from live inventory} | {question} | {status} | {risk or Not Applicable} | {evidence} |
| ...one row per discovered question... | ... | ... | ... | ... |
{Complete this table for every question in the Step 5a inventory — use the live count recorded in corpus/manifest.json; do not truncate}
## Full BP Ledger (MANDATORY)
**This section MUST list every BP citation produced by every pillar pass.** Concatenate every pillar table here, sorted by pillar then BP ID. Do NOT filter, cluster, or paraphrase. Every row surfaced by each pass must appear in the ledger. Target row count: one row per BP evaluated across all pillars — matching the summed per-pillar documentation counts from Step 5b.
This section is where recall reaches the user: skipping or truncating it collapses a full-inventory review down to whatever the assembler compresses to. **Do not skip this section.**
| BP ID | Pillar | Status | Risk Level | Evidence | Recommendation |
|-------|--------|--------|----------|----------|-----------------|
| {BP ID from live inventory} | {pillar} | {status} | {risk level or blank} | {evidence} | {recommendation} |
| ...one row per discovered BP... | ... | ... | ... | ... | ... |
{After writing this table, count the rows and confirm the count matches the sum of the pillar-pass rows. If not, you dropped citations — go back and add them.}
## Lens Findings (only if a lens was applied)
{Lens-specific best-practice evaluation, separate from the core findings above. Omit this section entirely for a General review.}
## Critical and High Risk Findings
{For each: ID, pillar, title, description, evidence (file:line), impact assessment, recommendation, effort, AWS services. This section EXPANDS on rows in the Full BP Ledger — it does NOT replace them.}
## Medium Risk Findings
{Same format, condensed. Also references ledger rows.}
## Low Risk Findings
{Summary table: ID | Pillar | Title | Recommendation. Also references ledger rows.}
## Cross-Pillar Trade-offs
{Conflicts between pillars and recommended resolution}
## Prioritize Improvements — Eisenhower Matrix
Not all findings should be addressed at once. Focus on a selected number of issues that make the most business impact and are easiest to implement. Then iterate.
Classify each finding by **importance** (business value) and **effort** (time, complexity, headcount):
HIGH IMPORTANCE
│
┌─────────┼─────────┐
│ DO │ PLAN │
│ FIRST │ │
│ │ │
───┼─────────┼─────────┼───
│ │ │
│DELEGATE │ DEFER │
│ │ │
└─────────┼─────────┘
│
LOW IMPORTANCE
LOW EFFORT HIGH EFFORT
| Quadrant | Action | Findings |
|----------|--------|----------|
| **Do First** (High Importance, Low Effort) | Implement immediately | {finding IDs} |
| **Plan** (High Importance, High Effort) | Schedule in roadmap, break into phases | {finding IDs} |
| **Delegate** (Low Importance, Low Effort) | Batch together, assign to available team member | {finding IDs} |
| **Defer** (Low Importance, High Effort) | Revisit in next iteration | {finding IDs} |
### Solution Characteristics
For each solution in "Do First" and "Plan":
- **SMART goal**: Specific, Measurable, Achievable, Relevant, Time-bound
- **Owner**: Identify who is responsible
- **Simple over complex**: Choose the simplest solution unless complexity is a non-negotiable requirement
- **Two-way door decisions**: Solutions should be extensible and evolve over time — avoid static solutions that cannot adapt
- **Pattern-based**: Target solutions that can be codified, reused, and re-shared (reference AWS Architecture Center)
## Prioritized Remediation Plan
### Quick Wins (< 1 week) — "Do First" quadrant
| Finding | Action | SMART Goal | Owner Suggestion | Effort |
|---------|--------|-----------|-----------------|--------|
{Config changes, enabling features, adding tags/alarms — simple, high-impact}
### Foundation (1-4 weeks) — "Plan" quadrant
| Finding | Action | Phases | Effort | Dependencies |
|---------|--------|--------|--------|--------------|
{Multi-AZ, CI/CD improvements, monitoring, caching — phased approach}
### Strategic (1-3 months) — "Plan" quadrant (complex)
| Finding | Action | Phases | Effort | Dependencies |
|---------|--------|--------|--------|--------------|
{DR, re-architecture, compliance programs — two-way door design}
### Delegate (batch & assign) — "Delegate" quadrant
| Finding | Action | Owner Suggestion | Effort |
|---------|--------|-----------------|--------|
{Low-importance, low-effort fixes — batch together and assign to an available team member}
### Deferred — Revisit Next Iteration
{Findings in the "Defer" quadrant with brief justification for deferral}
## Next Steps
{Top 5 concrete actions from the "Do First" quadrant — the team should start this week}
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |