Change → safer release

Make go/no-go a reviewable decision.

Review what changed, assess risk, allocate test depth, prepare rollout and rollback, and write release notes from verified facts.

Single-user license · 7-day refund window · 12 months of maintenance updates

ReleaseReady OS cover

01 / Outcome

A reviewable artifact, not a confident paragraph.

A release packet tied to a precise artifact, explicit evidence owners, staged rollout controls, stop conditions, and an executable recovery path.

When the evidence is incomplete, the workflow narrows the conclusion, marks the gap, and returns the next verification instead of inventing project facts.

02 / Workflow

7 focused skills, each with one job.

  1. 01

    Review the change

    Intent, diff, and missing evidence made explicit

  2. 02

    Assess risk

    An explained risk level and required controls

  3. 03

    Build the test matrix

    Test depth allocated to likely and harmful failures

  4. 04

    Prepare release

    A go/no-go packet tied to an exact artifact

  5. 05

    Plan rollout

    Observable and reversible release stages

  6. 06

    Prepare rollback

    Owned recovery with irreversible limits exposed

  7. 07

    Write notes

    Useful communication grounded in verified facts

03 / Fictional demonstration

Worked example: zero-downtime migration

A fictional required-column change becomes an expand/backfill/contract release. The workflow holds the constraint until old writers are gone and mismatch evidence is archived.

This excerpt is a fictional demonstration. It is not a customer result, production test, approval, or performance claim.

Release sequence

Expand, dual write, backfill, read switch, enforce, contract

Stop conditions

Replication lag, mismatch rate, and error-rate thresholds

Decision

Conditional plan until engine, size, lock window, and rehearsal are known

04 / Included

Everything needed to install, adapt, and inspect the workflow.

  • 7 native SKILL.md workflows
  • 7 portable prompts
  • 7 reusable Markdown templates
  • 3 realistic worked examples
  • Quick-start PDF, compatibility guide, license, and 12 months of maintenance updates

For

Use it when the work needs a boundary.

Developers, tech leads, and solo maintainers who need a repeatable release decision and recovery plan.

Not for

Keep the limits visible.

Buyers looking for a certification, compliance approval, production access, or a guarantee that a release cannot fail.

05 / Questions

Compatibility, evidence, and execution.

Is this a generic prompt collection?

No. Each workflow has a narrow trigger, required inputs, a procedure, an output contract, and rules for handling missing evidence.

Which assistants are supported?

The native filesystem skills are designed for Codex and Claude custom Agent Skills. Portable copy-and-paste prompts are included for other assistants. Availability depends on the model, plan, tools, and permissions you use.

Does the pack run code or change systems automatically?

No bundled workflow contains scripts or hidden network calls. A workflow may guide an assistant that already has tools, but consequential actions still require the user's authorization.

Are outcomes guaranteed?

No. Results depend on the context supplied, available evidence, model capability, tool access, and human review.

Replace improvised prompting with a reviewable workflow.

Native skills, portable prompts, templates, worked examples, and a practical quick start.

Get ReleaseReady OS — $29