Agent skill · ma08
prepare-production-release
Assess and harden an exact software release candidate before production. Use when committed or otherwise bounded code needs risk-scaled simplification, architecture sanity checks, migration and compatibility review, operational readiness, complementary external review, an approved read-only production state survey, or a plan-gated hardening pass, especially after agent-first or vibe-coded implementation. Produces release evidence and a human decision packet. Does not deploy or mutate production.
What it needs
About 8k tokens when loaded.
What this skill does
Prepare Production Release Turn an exact candidate into an evidence-backed readiness decision without turning "robustness" into speculative machinery. Work in two stages: assess and propose first, then implement only an explicitly accepted plan. Required References Read references/risk-and-evidence.md before choosing the intake or evidence scope. Read references/adviser-routing.md before deciding or invoking external adviser coverage. If a real production target exists, read references/production-state-survey.md before any provider command or before recording why the survey is omitted. Read references/readiness-report-template.md before writing either the Stage A or final report. Read references/source-notes.md only when auditing or changing this skill. Non-Negotiable Boundaries Stage A is candidate-source-read-only and production-state-read-only. It may inspect code, run non-production checks in an isolated environment, write task evidence, and use an already-approved read-only production route for the bounded survey. It must not edit application code, schemas, lockfiles, infrastructure, production data, or provider state. Stage B needs an accepted saved plan. Do not edit application code until the user has reviewed and explicitly approved or revised the Stage A plan. Persist that accepted plan in the active task status file before implementation. Never deploy with this skill. Do not mutate production, run a live migration, change provider settings, toggle production flags, or obtain new production authority. Prepare a separate release-control handoff when those actions become appropriate. Keep production authority local to the assessor. Never inherit credentials into Oracle or Fable, attach unsanitized production output, retrieve secret values, refresh login state, or switch provider identity for an assessment. Preserve the user's existing changes. Never broaden the diff to unrelated debt without explicit scope approval. Stage A: Assess and Propose 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ma08/prepare-production-release