mikeparcewski/rollout
skills/delivery/rollout/SKILL.md
Plan and coordinate progressive feature rollouts. Risk assessment, canary deployments, feature flag management, rollback procedures. Discovers deployment tools via capabilities. Use when: "roll out feature", "progressive rollout", "canary deployment", "feature flag", "rollback plan", "launch feature", "deploy gradually"
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden rolloutInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 6:25 AM146.8s4 files scanned
SKILL.md
- name:
- rollout
- description:
- |
- Use when:
- roll out feature", "progressive rollout", "canary deployment",
- phase_relevance:
- ["build", "review", "operate"]
- archetype_relevance:
- ["*"]
Rollout Skill
Plan and execute safe, progressive feature rollouts.
Quick Start
# Plan rollout for feature
/wicked-garden:delivery:rollout feature-new-dashboard
# Plan with specific strategy
/wicked-garden:delivery:rollout feature-checkout --strategy canary
# Discover deployment tools
/wicked-garden:delivery:rollout --discover
What This Skill Does
- Assesses rollout risk
- Selects appropriate rollout strategy
- Defines progressive stages
- Establishes success and rollback criteria
- Creates monitoring and communication plan
Risk Assessment
Risk Factors
User impact: <1% (LOW) | 1-25% (MEDIUM) | >25% (HIGH) Revenue impact: Non-revenue (LOW) | Funnel (MEDIUM) | Direct payment (HIGH) System criticality: Nice-to-have (LOW) | Important (MEDIUM) | Mission-critical (HIGH) Reversibility: Flag toggle (HIGH) | Schema change (MEDIUM) | Data migration (LOW)
Overall Risk
Risk = MAX(user, revenue, criticality) + reversibility_penalty
Rollout Strategies
| Risk | Strategy | Timeline | Stages | |------|----------|----------|--------| | LOW | Big Bang | Immediate | 0% → 100% | | MEDIUM | Progressive | 1-2 weeks | 0% → 10% → 25% → 50% → 100% | | HIGH | Canary | 4-6 weeks | 0% → 1% → 5% → 10% → 25% → 50% → 100% |
See strategies-core.md and strategies-operations.md for detailed guidance.
Stage Definition
For each stage:
- Traffic percentage: 1%, 10%, 25%, 50%, 100%
- Duration: 24h to 1 week
- Success criteria: Error rate, conversion, performance
- Rollback criteria: Automatic and manual triggers
Success & Rollback Criteria
Success (all must pass):
- Primary metric stable or improved
- Error rate within bounds
- Performance acceptable
- No critical bugs
Automatic rollback:
- Error rate >2x baseline
- Performance >2x latency
- Availability <99.5%
Manual rollback:
- Revenue impact detected
- Security vulnerability
- Regulatory issue
Monitoring Plan
Business: Primary metric, revenue, retention Technical: Error rate, latency (p50/p95/p99), throughput User: Support tickets, feedback, crashes
Alerts:
- WARNING: 1.5x baseline
- CRITICAL: 2x baseline or 5% error rate
Communication Plan
Stakeholders: Engineering (technical), Product (timeline), Support (FAQs), Leadership (risk)
Timeline:
- T-2 days: Pre-rollout notification
- T-0: Rollout begins
- T+checkpoints: Progress updates
- T+complete: Completion summary
Output Format
The skill emits a markdown rollout plan with sections: Risk Assessment, Strategy, Rollout Stages (table), Monitoring, Rollback Plan, Communication, Stage Gate Checklist, Next Steps.
Full template with substitutable placeholders: refs/output-template.md.
Capability Discovery
Discovers deployment tools automatically via capability detection:
Capabilities needed:
feature-flags: Feature toggle and flag managementdeployment: Progressive rollout and canary deployment toolsmonitoring: Metrics, dashboards, and alerting
Discovery methods:
- CLI tools (container orchestration, feature flag CLIs, IaC tools)
- Configuration files (deployment manifests, infrastructure configs)
- Environment variables (API keys, endpoints)
- SDK detection (package dependencies)
Asks "Do I have deployment capability?" not "Do I have Kubernetes?" Gracefully degrades to manual procedures when capabilities unavailable.
Integration
With native tasks: Tracks rollout progress per stage via TaskCreate/TaskUpdate with metadata.event_type="task"
With qe: Uses test scenarios for validation
With wicked-brain:memory: Recalls past rollout learnings
With wicked-garden:delivery:experiment: Uses experiment results for confidence
See Also
- strategies-core.md and strategies-operations.md - Detailed rollout strategies
/wicked-garden:delivery:experiment- Design and analyze experiments before rollout
Related Skills
mikeparcewski/skills/engineering/large-scale-migration
development
VerifiedTrustedCommunity
--- name: large-scale-migration description: How to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/fra
8SKILL.mdUpdated Jun 3, 2026
mikeparcewski/wicked-garden:classify
testing
VerifiedTrustedCommunity
v11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a `<wg classify-due />` directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.
8SKILL.mdUpdated May 26, 2026
mikeparcewski/wicked-garden:archetype
tools
VerifiedTrustedCommunity
v11 work-shape archetype runner. When a prompt has been routed to one of the 9 archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or when one of the per-archetype slash commands resolves to this skill.
8SKILL.mdUpdated May 8, 2026
mikeparcewski/intent
development
VerifiedTrustedCommunity
Show or set the session intent variable. Intent gates how loud the framework is — simple-edit (silent), feature/research (synthesis directive), rigor (full crew context). Auto-detected on turn 1; this skill overrides explicitly. Sticky for the session. Use when: "set intent", "intent override", "/wicked-garden:intent", "make the framework quiet", "force rigor", "what's my intent".
8SKILL.mdUpdated May 6, 2026