agentleFS
dvy1987dvy1987/agent-loom/.agents/skills/shipping-and-launch/SKILL.md

shipping-and-launch

Skill4 starsChanged 3 months agoMITView on GitHub

Prepare safe production launches — pre-launch checklist, monitoring, staged rollout, and rollback. Load when deploying to production, releasing a major change, opening beta access, or the user asks for a launch checklist, go-live plan, rollout strategy, or rollback plan. Not for local-only prototypes. Pairs with ci-cd-and-automation and app-security-hardening.

67 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use observability-and-instrumentation, constraint-driven-development and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HK-hubSkill

    observability-and-instrumentation

    Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

    Also in 40 projects that use this

  • MrCipherSmithSkill

    constraint-driven-development

    Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.

    Also in 16 projects that use this

  • HK-hubSkill

    deprecation-and-migration

    Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

    Also in 41 projects that use this

  • seikaikyoSkill

    doubt-driven-development

    對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。

    Also in 46 projects that use this

  • skytiger6724Skill

    brainstorm-experiments-existing

    Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

    Also in 4 projects that use this

  • skytiger6724Skill

    prioritize-assumptions

    Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.

    Also in 4 projects that use this

  • +2 more from skytiger6724

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 60 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Document: what ships, who is affected, success metrics, rollback triggers (error rate, latency, support tickets).

    line 38
  2. Distinctive:

    No secrets in repo; dependencies audited for critical CVEs

    line 45
  3. Distinctive:

    If triggers hit → rollback first, postmortem second.

    line 63
  4. Distinctive:

    No changes — citation audit passed.

    line 138

“Common” is measured: kept by at least 6 in 10 of the 60 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Shipping and Launch

Ship with confidence: reversible, observable, incremental. Every launch has a rollback path and success metrics defined before traffic moves.

Hard Rules

  • No launch without rollback — feature flag, previous artifact, or DB migration down path.
  • Monitoring before traffic — alerts on errors, latency, and business KPIs.
  • Staged rollout — internal → beta → % canary → full unless risk is trivial.
  • Checklist is blocking — unchecked security/perf/a11y items are explicit deferrals with owner.
  • Communicate — stakeholders know window, owner, and rollback trigger.

Workflow

Step 1 — Define success and risk

Document: what ships, who is affected, success metrics, rollback triggers (error rate, latency, support tickets).

Step 2 — Pre-launch checklist

Minimum gates:

  • Tests green (unit, integration, e2e on critical paths)
  • No secrets in repo; dependencies audited for critical CVEs
  • Performance budgets met on changed surfaces
  • Accessibility spot-check on changed UI
  • Runbook: deploy steps, owner, comms channel

Step 3 — Staged rollout

  1. Deploy to staging with prod-like data volume if possible
  2. Internal dogfood or feature flag to staff
  3. Canary (% traffic or invite-only beta)
  4. Full rollout with monitoring watch window

Step 4 — Monitor and decide

Watch 24–72h (risk-dependent): error rate, p95 latency, Core Web Vitals, conversion/support signals.

Step 5 — Rollback or complete

If triggers hit → rollback first, postmortem second. If stable → remove flags, archive runbook learnings.


When NOT to use

  • Pure local dev with no users
  • Changes already live behind a flag with an existing runbook (update runbook only)

Gotchas

  • "Green staging" with 10x less data than prod hides query issues.
  • Launch without feature flags forces redeploy to rollback.
  • Announcing before monitoring is wired means flying blind.
  • Skipping comms strands on-call.

Common Rationalizations

ExcuseReality
"It's a small change"Small deploys still need rollback and error visibility.
"We'll add alerts after launch"You discover outages from users instead of dashboards.
"Full send is faster"One incident costs more than a canary day.
"Rollback is unlikely"Plan for it anyway — Hyrum's Law applies in prod.
"Checklist is bureaucracy"It's how you remember security and a11y under time pressure.

Output Format

## Launch plan — [feature]

Risk: [low/med/high] | Rollback: [how]
Stages: [list] | Metrics: [list]
Checklist: [pass/deferred items]
Owner / window: [who / when]

Examples

<examples> <example> <input>"Ship new billing flow Friday."</input> <output>Feature flag at 5% → 25% → 100%; dashboards on payment errors; rollback = disable flag; checklist signed.</output> </example> </examples>

Verification

  • Rollback path documented and tested (or dry-run)
  • Monitoring/alerts live before user traffic
  • Staged rollout plan matches risk level
  • Pre-launch checklist complete or deferrals explicit
  • Success metrics and rollback triggers defined

Red Flags

  • Launch without rollback path or previous artifact
  • Traffic shifted before error and KPI monitors exist
  • Full rollout for non-trivial change without canary
  • Staging-only validation at fraction of prod data volume

Prune Log

Last pruned: 2026-07-04

  • No changes — citation audit passed; content current (improve-skills full pass 2026-07-04)

Impact Report

Feature: [name] | Risk: [level]
Stages: N | Rollback: [ready/deferred]
Checklist: [N pass / M deferred]

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.