templates/skills/planning/rollout-strategy/SKILL.md
--- name: planning-rollout-strategy description: Rollout strategy: stages, audiences, enablement mechanics, stop points --- <purpose> <item>Reduce rollout degradation risk and keep enablement controllable</item> </purpose> <inputs> <required>Change description + risks/criticality</required> <optional>Available mechanisms (feature flags, canary, blue-green)</optional> <optional>Release/window constraints</optional> </inputs> <method> <step>Select a rollout mechanism (flag/canary/blue
npx skillsauth add ozerohax/assistagents templates/skills/planning/rollout-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
<output_format>
<section>Rollout mechanism</section> <section>Stages</section> <section>Gates / stop points</section> <section>Actions on degradation</section> </output_format><quality_rules> <rule importance="critical">Stages and gates are specific (percent/time/conditions)</rule> <rule importance="high">There are explicit actions on degradation, not "we will see"</rule> </quality_rules>
testing
Visual regression (baseline diffs, UI stabilization)
testing
Design detailed reproducible test cases (Given/When/Then, one check per case); not smoke/regression checklists
development
Mobile testing (native/hybrid/web, gestures, offline, interruptions)
testing
Load testing (k6/JMeter scenarios, benchmarks)