Skip to content
Back to skills

Architecture Review 4

ASecurity

Review an existing Python RAG codebase against an explicit RAG architecture document and produce a production-readiness backlog with priorities, rationale, and execution guidance.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
ai-agentspythongotestingsecurityperformance

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill architecture-review-4 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Architecture Review 4?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Architecture Review 4
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-architecture-review-4/badge)](https://www.skillsdirectory.com/skills/david-li0406-architecture-review-4)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: architecture-review
description: Review an existing Python RAG codebase against an explicit RAG architecture document and produce a production-readiness backlog with priorities, rationale, and execution guidance.
---

# Architecture Review Skill

## Goal
Produce a **production-grade architecture review document** for a non-trivial Python RAG system.

The output must be a **prioritised, implementation-ready task backlog** that a senior engineering team can directly execute to harden the system for production.

The review must explicitly evaluate:
1. The current implementation
2. The stated architecture document (`RAG_ARCHITECTURE.md`)
3. Known, explicitly deferred architectural areas

---

## When to Use This Skill
Use this skill when the user asks to:
- Review a RAG or LLM system for production readiness
- Audit architecture compliance
- Identify gaps, risks, or missing safeguards
- Produce a structured backlog for engineering execution

---

## Instructions

1. Assume the system is **non-trivial and already deployed** in at least one environment.
2. Assume the audience is **senior engineers**.
3. Evaluate the codebase against:
   - Production engineering standards
   - The architecture document
   - Explicit architectural constraints (including deferred areas)
4. Produce **one table per category**, in the exact order specified below.
5. Each task must be **concrete, opinionated, and actionable**.
6. Do **not** explain code line-by-line.
7. Focus on **what must be done**, not how the system generally works.

---

## Categories
(Create **EXACTLY one table per category**, in this order)

1. Architecture & System Design  
2. RAG Pipeline (Ingestion, Retrieval, Reranking, Generation)  
3. Prompting & Grounding Controls  
4. Code Quality & Python Practices  
5. Observability & Operations  
6. Evaluation & Quality Measurement  
7. Security, Privacy & Data Risks  
8. Performance, Latency & Cost  
9. Testing Strategy  

---

## Table Format (MANDATORY)

Each table must contain **EXACTLY** the following columns, in this order:

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…