Skip to content
Back to skills

Production Readiness Lord

BSecurity

Lord skill for evidence-based production-readiness audits — full-spectrum project review (architecture, security, data, testing, performance, observability, config, deployment, supply chain, docs, UX/a11y, legal), severity-ranked findings, mid-session decision escalation, and a human-only launch checklist.

  • 6 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added November 13, 2026
ai-agentsgotestingapidatabasefrontenddevopsci/cdsecurityperformancedocumentation

Works with

  • api

Security analysis

B85/100
  • highPerforms destructive filesystem operations

Pro shows the line behind each finding and how to fix it

Scanned November 13, 2026

npx -y skills add m3taz-ahmed/aizee --skill production-readiness-lord --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Production Readiness Lord?

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

Security grade badge for Production Readiness Lord
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/m3taz-ahmed-production-readiness-lord/badge)](https://www.skillsdirectory.com/skills/m3taz-ahmed-production-readiness-lord)

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: production-readiness-lord
description: Lord skill for evidence-based production-readiness audits — full-spectrum project review (architecture, security, data, testing, performance, observability, config, deployment, supply chain, docs, UX/a11y, legal), severity-ranked findings, mid-session decision escalation, and a human-only launch checklist.
triggers:
  - production readiness lord
  - production readiness
  - production audit
  - pre-launch review
  - pre-launch audit
  - go-live
  - go live checklist
  - launch readiness
  - readiness review
  - ready for production
  - ship it review
  - audit project
  - full project review
  - production checklist
  - before launch
  - before deploy
  - launch checklist
  - release readiness
  - مراجعة قبل الإطلاق
  - جاهزية الإنتاج
  - راجع المشروع
  - مراجعة المشروع
  - مراجعة شاملة
  - جاهز للانتاج
  - قبل النشر
personas:
  - ARCH
  - DEV
  - QA
  - SRE
  - DEVOPS
  - SEC
tech_stack:
  - api-design-standards
  - design-foundations
  - appsec-hardening
lord: true

---

# Production Readiness Lord

[SKILL] production-readiness-lord
[OBJ] Audit any project end-to-end for production readiness — evidence-based findings, mid-session decision escalation, severity-ranked gaps, and a human-only launch checklist. This is an AUDIT, never a refactor.

[RULES]
1. [REQ] Phase 0 — ask FIRST, before auditing: (a) what does the project do + for whom, (b) target environment (cloud/VPS/shared/store/on-prem), (c) expected scale (users, req/day, data size), (d) compliance obligations (GDPR/PCI/HIPAA/none/unsure), (e) deadline or hard constraints, (f) what was already reviewed (don't re-flag accepted risk). If the repo answers any of these (README/docs/config), state the answer instead of asking.
2. [REQ] READ-ONLY: never refactor, fix, commit, or delete. Never run destructive commands (drop tables, rm -rf, force-push, production mutations). If verification could mutate anything — ask first.
3. [REQ] Evidence on every finding: file:line, command output, or config excerpt. "Looks fine" is not a finding; "no rate limit on /api/login (server/routes/auth.ts:31)" is.
4. [REQ] Label every observation: FACT (verified in code) / ASSUMPTION (inferred — needs confirmation) / UNVERIFIABLE (needs access — log it, never guess it as "fine").
5. [REQ] Mid-session escalation: when a decision only the owner can make appears — trade-off, business policy, missing context, a fix that changes behavior — STOP and ask immediately. Never batch questions to the end; an audit built on wrong assumptions is worthless.
6. [REQ] Run the project's own gates: if tests/lint/typecheck/build are configured, run them and report real output. If they can't run, say exactly why.
7. [REQ] Severity discipline: 🔴 BLOCKER (data loss, breach, legal, unrecoverable), 🟠 HIGH (real user impact, security weakness — fix at/before launch), 🟡 MEDIUM (debt that will bite), 🔵 LOW (polish). Every finding gets one — no unranked lists.
8. [REQ] No checklist padding: report only what was actually verified. An axis that can't be audited (no infra access) is marked UNVERIFIABLE — never "assumed fine".
9. [REQ] Audit ALL 13 axes — none skipped silently:
   1. **Architecture & design** — layering, dependency direction, coupling, god-objects, dead code, single points of failure, baked-in scale assumptions.
   2. **Code quality** — swallowed errors/empty catches, typing discipline, duplication, TODO/FIXME, debug leftovers (console.log, commented blocks, hardcoded test data), magic values.
   3. **Security** — OWASP Top 10: injection, object-level authz (BOLA — check per-resource, not just login), secrets in code/history/logs, unsafe deserialization, CORS, security headers, upload validation, SSRF, session/JWT handling, crypto choices, rate limiting on auth + expensive routes.
   4. **Data & database** — constraints at DB level, reversible tested migrations, indexes on hot queries, N+1, PII retention, backup + TESTED restore (untested backup = finding), seed/fixture leakage into prod.
   5. **Testing** — run the suite; real results vs coverage claims; critical untested paths (auth, payments, mutations); flakes; missing regression tests.
   6. **Performance** — unbounded queries, sync loops over remote calls, missing pagination, payload sizes, bundle/artifact size, cold start, cache strategy + invalidation, leaks (listeners, unbounded caches).
   7. **Observability & ops** — structured logs, error tracking, /healthz + /readyz, alerting, metrics, correlation IDs; "what would a 3AM incident look like with current visibility" is the bar.
   8. **Config & environments** — env vars documented + validated at boot, secrets via manager, dev/staging/prod separation, sane defaults, committed .env (🔴), per-env CORS/hosts.
   9. **Deployment & CI/CD** — reproducible build, lockfile committed, tested rollback path, migration deploy order, zero-downtime story, CI gates merges, artifacts scanned/signed.
   10. **Dependencies & supply chain** — audit tooling run (npm audit/pip-audit/composer audit), outdated/abandoned deps, license conflicts for commercial use, pinning.
   11. **Documentation** — README gets a stranger running in minutes, env documented, runbooks, architecture notes MATCH reality (verify claims against code — stale docs are findings).
   12. **UX & accessibility (if UI exists)** — keyboard nav, contrast, focus states, loading/empty/error states everywhere, responsive, form errors, RTL/i18n where claimed.
   13. **Legal & business** — license compliance, privacy/terms where required, consent/cookies, payment edge cases (refunds, failed charges, trial expiry), data-processing terms.
10. [REQ] Execution order: Phase 0 questions → recon (map structure/stack/entry points; one-paragraph summary to the user before deep-diving) → axis-by-axis audit with one-line progress per axis → escalate decisions the moment they appear → final report.
11. [REQ] Final report format — exact structure:
    `# Production Readiness Report — <project>` → **Verdict** ([READY / READY WITH CONDITIONS / NOT READY] + 2-3 sentences) → **Scorecard** (13-axis table, /10 + blocking issues) → **🔴 Blockers** table (# / Finding / Evidence / Fix / Effort) → **🟠/🟡/🔵** same table per tier → **⚠️ DECISIONS NEEDED FROM ME** (pending questions + UNVERIFIABLE items needing granted access) → **👤 HUMAN-ONLY ACTIONS** (accounts, secrets to provision, DNS, legal sign-off, billing limits, on-call ownership, restore drill, dashboards) → **Recommended launch sequence** (blockers → high → human-only → final verification pass).
12. [PROHIBIT] Marking anything "done" without verification; generic best-practice dumps unverified against THIS codebase; fixing without asking; burying a blocker inside a Medium list; or presenting assumptions as findings.
13. [CMD] Delegate deep domain verification to the domain lords: security deep-dive → `security-auditor`/`security-lord`, DB internals → `database-lord`, infra/hosts → `server-ops-lord`, pipeline → `devops-engineer`/`devops-lord`, UI quality → `frontend-ui-expert` + `accessibility-auditor`, reasoning under ambiguity → `problem-solving-lord`. The auditor aggregates; specialists verify.

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.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.