Releasing and operating products
Codex plugin for governing large software projects from discovery through release and operations.
npx -y skills add VKK-00/agentic-project-lifecycle --skill releasing-and-operating-productsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when preparing alpha, beta, release candidate, general availability, production rollout, feature flags, migrations, rollback, SLOs, alerts, runbooks, customer support, incident response, or post-release learning.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, as published. Nobody here has run it
Releasing and Operating Products
A release is a controlled exposure with a product hypothesis, operational ownership, and a reversible path—not merely a deployment.
Define and expose safely
- RULE-OPS-01: Specify audience, hypothesis, included and excluded scope, entry criteria, exit criteria, metrics, known limitations, owner, and support channel for every staged release.
- RULE-OPS-02: Define SLOs or explicit reliability targets, telemetry, dashboards, actionable alerts, runbooks, escalation, and support ownership before exposing users.
- RULE-OPS-03: Use the smallest safe exposure mechanism—internal cohort, allowlist, feature flag, canary, or percentage rollout—with explicit pause and rollback thresholds.
- RULE-OPS-04: Rehearse migrations, backup restore, rollback, and operator recovery on production-shaped conditions. A backup without a successful restore test is not recovery evidence.
Operate and learn
- RULE-OPS-05: Record incident impact, timeline, detection, causes, contributing factors, corrective actions, owners, and deadlines without blame. Feed evidence back into specifications and roadmap.
- RULE-OPS-06: Do not declare a release complete without fresh command results, manual critical-path checks, known limitations, approval status, and observed post-release metrics.
Read release stages, reliability and recovery, and incidents and learning.