Shipping And Launch

Shipping and Launch

Purpose

Stage: Ship — the release workhorse. Runs after the human merges; release-level, so one pass may cover a single merged change or batch several.

Ship with confidence. The goal is not just to deploy — it's to deploy safely, with monitoring in place, a rollback plan ready, and a clear understanding of what success looks like. Every launch should be reversible, observable, and incremental.

Written after the merge, executed at the deploy. Two different moments, and confusing them breaks the stage. A release runbook is not an input to a pull request: one slice's draft PR is not a release, so pull-request neither reads this runbook nor waits for one to exist. This skill starts once the change is on the base branch. The runbook's own steps — deploy, enable the flag, advance the canary, roll back — happen later still, run by the human off the written plan.

A merged change is therefore the entry condition, and that is what puts this skill outside the autonomous run. Nothing in this suite is merged by the agent: a run ends at an open draft PR and the human merges whenever they get to it. Whoever invokes this skill afterwards — the human, or an agent the human starts — is working on the far side of that merge.

v1 autonomy fence. This skill AUTHORS the release runbook; it does not execute deploy, rollout, or rollback commands, and it sits outside the autonomous span. The agent's run ends at the open draft PR (pull-request workhorse); this skill picks up on the far side of the human's merge — every DEPLOY / ENABLE / canary-advance / ROLL BACK step below is a runbook the human runs, never an action the agent fires unattended. Auto-deploy and auto-merge are out of v1 (safety rail 1, references/safety-rails.md: a human merges). Whoever invokes it, human or agent, its output is a written plan in release.md, not a side effect.

When to use / when to skip

• Preparing a feature's first production deploy
• Releasing a significant change to users
• Migrating data or infrastructure
• Opening a beta or early access program
• Any deployment that carries risk (all of them)
• Skip for a docs-only / config-only change with no user-visible runtime effect — there is no rollout to stage and nothing to roll back.

Inputs

Consumes (refuse to run if absent):

• The change being released, with its gates green — the slice (or the set of slices batched into one release) whose qa.md ## Verdict reads pass and whose Review fan-out is clear, plus the diff that was merged. Green gates are what makes a change launch-ready. A change nobody has verified or reviewed has nothing to write a runbook about.
• environment.md (typed-kind manifest; read-only, value-blind) — names the production + staging targets and the feature-flag / monitoring services as typed rows. It carries NO values and NO commands; read it for what exists, never for secrets or shell strings.
• prd.md + referenced ADRs — the success definition the rollout decision thresholds bind to (which business metrics matter, what "Good" means for this feature).

Refuse-to-run if: the change has not cleared Verify and Review (qa.md ## Verdict is not pass, or a Critical/Required review finding is still open) — route it back, there is nothing launch-ready to prepare; environment.md is missing or its rows are unprovisioned (run preflight-readiness first); or no rollback path is identifiable for the change.

Do gate on the merge. There is no release to plan until the change is on the base branch, and the agent never performs that merge — so this skill starts when the human hands it merged work, never mid-run. A slice still sitting at an open draft PR belongs to pull-request; route it back there.

The Pre-Launch Checklist

Code Quality

• All tests pass (unit, integration, e2e)
• Build succeeds with no warnings
• Lint and type checking pass
• Code reviewed and approved
• No TODO comments that should be resolved before launch
• No console.log debugging statements in production code
• Error handling covers expected failure modes

Security

• No secrets in code or version control
• npm audit shows no critical or high vulnerabilities
• Input validation on all user-facing endpoints
• Authentication and authorization checks in place
• Security headers configured (CSP, HSTS, etc.)
• Rate limiting on authentication endpoints
• CORS configured to specific origins (not wildcard)

Performance

• Core Web Vitals within "Good" thresholds
• No N+1 queries in critical paths
• Images optimized (compression, responsive sizes, lazy loading)
• Bundle size within budget
• Database queries have appropriate indexes
• Caching configured for static assets and repeated queries

Accessibility

• Keyboard navigation works for all interactive elements
• Screen reader can convey page content and structure
• Color contrast meets WCAG 2.1 AA (4.5:1 for text)
• Focus management correct for modals and dynamic content
• Error messages are descriptive and associated with form fields
• No accessibility warnings in axe-core or Lighthouse

Infrastructure

• Environment variables set in production
• Database migrations applied (or ready to apply)
• DNS and SSL configured
• CDN configured for static assets
• Logging and error reporting configured
• Health check endpoint exists and responds

Documentation

• README updated with any new setup requirements
• API documentation current
• ADRs written for any architectural decisions
• Changelog updated
• User-facing documentation updated (if applicable)

Feature Flag Strategy

Ship behind feature flags to decouple deployment from release:

// Feature flag check
const flags = await getFeatureFlags(userId);

if (flags.taskSharing) {
  // New feature: task sharing
  return <TaskSharingPanel task={task} />;
}

// Default: existing behavior
return null;

Feature flag lifecycle:

1. DEPLOY with flag OFF     → Code is in production but inactive
2. ENABLE for team/beta     → Internal testing in production environment
3. GRADUAL ROLLOUT          → 5% → 25% → 50% → 100% of users
4. MONITOR at each stage    → Watch error rates, performance, user feedback
5. CLEAN UP                 → Remove flag and dead code path after full rollout

Rules:

• Every feature flag has an owner and an expiration date
• Clean up flags within 2 weeks of full rollout
• Don't nest feature flags (creates exponential combinations)
• Test both flag states (on and off) in CI

Staged Rollout

The Rollout Sequence

1. DEPLOY to staging
   └── Full test suite in staging environment
   └── Manual smoke test of critical flows

2. DEPLOY to production (feature flag OFF)
   └── Verify deployment succeeded (health check)
   └── Check error monitoring (no new errors)

3. ENABLE for team (flag ON for internal users)
   └── Team uses the feature in production
   └── 24-hour monitoring window

4. CANARY rollout (flag ON for 5% of users)
   └── Monitor error rates, latency, user behavior
   └── Compare metrics: canary vs. baseline
   └── 24-48 hour monitoring window
   └── Advance only if all thresholds pass (see table below)

5. GRADUAL increase (25% -> 50% -> 100%)
   └── Same monitoring at each step
   └── Ability to roll back to previous percentage at any point

6. FULL rollout (flag ON for all users)
   └── Monitor for 1 week
   └── Clean up feature flag

Rollout Decision Thresholds

Use these thresholds to decide whether to advance, hold, or roll back at each stage:

When to Roll Back

Roll back immediately if:

• Error rate increases by more than 2x baseline
• P95 latency increases by more than 50%
• User-reported issues spike
• Data integrity issues detected
• Security vulnerability discovered

Monitoring and Observability

What to Monitor

Application metrics:
├── Error rate (total and by endpoint)
├── Response time (p50, p95, p99)
├── Request volume
├── Active users
└── Key business metrics (conversion, engagement)

Infrastructure metrics:
├── CPU and memory utilization
├── Database connection pool usage
├── Disk space
├── Network latency
└── Queue depth (if applicable)

Client metrics:
├── Core Web Vitals (LCP, INP, CLS)
├── JavaScript errors
├── API error rates from client perspective
└── Page load time

Error Reporting

// Set up error boundary with reporting
class ErrorBoundary extends React.Component {
  componentDidCatch(error: Error, info: React.ErrorInfo) {
    // Report to error tracking service
    reportError(error, {
      componentStack: info.componentStack,
      userId: getCurrentUser()?.id,
      page: window.location.pathname,
    });
  }

  render() {
    if (this.state.hasError) {
      return <ErrorFallback => this.setState({ hasError: false })} />;
    }
    return this.props.children;
  }
}

// Server-side error reporting
app.use((err: Error, req: Request, res: Response, next: NextFunction) => {
  reportError(err, {
    method: req.method,
    url: req.url,
    userId: req.user?.id,
  });

  // Don't expose internals to users
  res.status(500).json({
    error: { code: 'INTERNAL_ERROR', message: 'Something went wrong' },
  });
});

Post-Launch Verification

In the first hour after launch:

1. Check health endpoint returns 200
2. Check error monitoring dashboard (no new error types)
3. Check latency dashboard (no regression)
4. Test the critical user flow manually
5. Verify logs are flowing and readable
6. Confirm rollback mechanism works (dry run if possible)

Rollback Strategy

Every deployment needs a rollback plan before it happens:

## Rollback Plan for [Feature/Release]

### Trigger Conditions
- Error rate > 2x baseline
- P95 latency > [X]ms
- User reports of [specific issue]

### Rollback Steps
1. Disable feature flag (if applicable)
   OR
1. Deploy previous version: `git revert <commit> && git push`
2. Verify rollback: health check, error monitoring
3. Communicate: notify team of rollback

### Database Considerations
- Migration [X] has a rollback: `npx prisma migrate rollback`
- Data inserted by new feature: [preserved / cleaned up]

### Time to Rollback
- Feature flag: < 1 minute
- Redeploy previous version: < 5 minutes
- Database rollback: < 15 minutes

See Also

• For the project-wide Definition of Done that every change must clear before this checklist, see references/definition-of-done.md
• For security pre-launch checks, see references/security-checklist.md
• For performance pre-launch checklist, see references/performance-checklist.md
• For accessibility verification before launch, see references/accessibility-checklist.md

Rationalizations

Red flags

• Deploying without a rollback plan
• No monitoring or error reporting in production
• Big-bang releases (everything at once, no staging)
• Feature flags with no expiration or owner
• No one monitoring the deploy for the first hour
• Production environment configuration done by memory, not code
• "It's Friday afternoon, let's ship it"
• Agent (not the human) executing a DEPLOY / canary-advance / ROLL BACK command unattended — the v1 fence makes deploy a human-post-merge action.

Verification (ending criteria)

This skill is done when the runbook is written, not when the deploy happens. The two lists sit on opposite sides of the deploy.

Before deploying — whoever authors the release finishes these, and finishing them is what ends the skill:

• Pre-launch checklist completed (all sections green)
• Feature flag configured (if applicable)
• Rollback plan documented
• Monitoring dashboards set up
• Team notified of deployment

After deploying — the runbook hands these to the human, who works them once the deploy is out; the agent never checks them off itself:

• Health check returns 200
• Error rate is normal
• Latency is normal
• Critical user flow works
• Logs are flowing
• Rollback tested or verified ready

Outputs & handoff contract

Emits the release artifact → release.md under docs/features/<slug>/ (or docs/releases/<date>-<slug>.md for a batched multi-feature release). Stable sections a consumer depends on — change the shape, update the consumer in the same commit:

• Pre-launch checklist — every section green (Code Quality · Security · Performance · Accessibility · Infrastructure · Documentation) with the gating items checked.
• Feature-flag plan — flag name, owner, expiration date, and the OFF → team → canary → 100% lifecycle.
• Staged-rollout plan — the rollout sequence plus the decision-threshold table (advance / hold / roll-back per metric).
• Rollback plan — trigger conditions, steps, DB considerations, and the time-to-rollback budget (the ## Rollback Plan for [Feature] template, filled).
• Monitoring setup — the dashboards/alerts to watch + the first-hour post-launch verification list.
• Deploy fence — an explicit Executed by: human, post-merge banner. In v1 the agent authors this runbook but executes no deploy/rollout/rollback command; every action is fenced behind the human's async merge (auto-deploy out of v1).

Consumer: the human running the deploy. No skill reads release.md — pull-request in particular does not, because a slice's draft PR opens well before any release exists and never waits on one.

STATE.md: shipping-and-launch is release-level and post-merge — it does NOT own a slice row and never flips a slice gate to agent for a deploy action (pull-request owns the slice row). Once the feature's slices read done and their PRs are merged, record release.md under that feature's Artifacts cell. If a CRITICAL/HIGH security finding or a secret surfaces while preparing the release → hard STOP, fire PushNotification, open no release (safety rails 2 and 3).