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/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026