structural-operating

Review releases, rollouts, and runbooks for reversible deployment and safe production operation.

Updated May 27, 2026
One-click install
npx skills add https://github.com/ybaspinar/agent-work-skills --skill structural-operating-ybaspinar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: structural-operating
Source: https://github.com/ybaspinar/agent-work-skills/tree/main/skills/structural-operating
Command: npx skills add https://github.com/ybaspinar/agent-work-skills --skill structural-operating-ybaspinar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping to production often hides irreversible steps, unbounded retries, and unowned alerts until a 2am incident exposes them. This Skill structures release and operations reviews so rollouts are reversible, promotions are evidence-based, and every failure mode has an owner and a runbook. ## Core Features & Use Cases - Rollout Shape Review: Checks flags, canaries, ramps, promotion signals, rollback plans, and approvals for irreversible steps. - Runtime Containment Checks: Verifies degraded tiers, retry caps with backoff and jitter, circuit breakers, load shedding, and graceful shutdown draining. - Ownership & Runbook Audit: Ensures every flag, migration, dashboard, and alert has a named owner, expiry date, and documented failure actions. - Use Case: Before ramping a database migration to full traffic, run this Skill to confirm the backout path works without a new build, the promotion signal is metric-based, and the on-call runbook covers known failure modes. ## Quick Start Ask the AI to review your release plan, rollout configuration, or runbook using the structural-operating checks and flag any red-flag risks.

Frequently Asked Questions about structural-operating

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make a production release reversible?

Ship behind feature flags, canaries, or cohorts so rollback is a config change rather than a new build. Use expand-and-contract for schema changes and require four-eyes approval for irreversible or wide-blast-radius steps.

What should a canary promotion signal be based on?

Promotion should be driven by canary versus control metrics, not calendar time or intuition. Advancing a ramp because "it has been an hour" is a red flag; define measurable success criteria before starting the rollout.

How should retry policies be configured for production services?

Retries need a cap, exponential backoff, jitter, a deadline, and a circuit breaker to avoid amplifying load during an outage. Unbounded retries without these bounds are a common cause of cascading failures.

What does graceful shutdown require for a service?

Stop accepting new work, drain in-flight requests within a deadline, flush buffers, and only acknowledge durably completed work. Shutdowns that wait forever or drop accepted work both violate safe operation.

When is a full canary rollout process not necessary?

Reversible shipping mechanisms like flags and canaries are justified by blast radius; trivial low-risk changes may not need them. The Skill scales its checks to the risk of the release rather than mandating ceremony for every change.