devops-plan
Gather DevOps context for infrastructure planning. Detects IaC tools, providers, and recommends skills. Use when Skill("blueprint") detects infrastructure work.
What this skill does
# DevOps Plan Context
Gather infrastructure context for planning. Returns structured findings for the parent plan command.
## When Called
This skill is invoked by `Skill("blueprint")` when DevOps keywords are detected in the feature description.
## Workflow
### 1. Detect IaC Files
Check for existing infrastructure code:
```bash
# Terraform/OpenTofu
ls *.tf infra/*.tf terraform/*.tf infrastructure/*.tf 2>/dev/null
# Ansible
ls ansible.cfg playbook.yml ansible/*.yml playbooks/*.yml 2>/dev/null
ls -d roles/ ansible/roles/ 2>/dev/null
# Cloud-init
ls cloud-init*.yml user-data*.yml cloud-config*.yml 2>/dev/null
```
**Set flags:**
- `HAS_TERRAFORM: true/false`
- `HAS_ANSIBLE: true/false`
- `HAS_CLOUD_INIT: true/false`
### 2. Detect Providers
If Terraform files exist, extract providers:
```bash
grep -h "provider\s*\"" *.tf infra/*.tf 2>/dev/null | grep -oE '"[a-z]+"' | tr -d '"' | sort -u
```
Common providers to detect:
- `aws`, `google`, `azurerm` - Major clouds
- `hcloud` - Hetzner
- `digitalocean` - DigitalOcean
- `cloudflare` - Cloudflare
- `backblaze` - Backblaze B2
### 3. Map Skills
Based on detection, recommend skills:
| Detection | Skill | Purpose |
|-----------|-------|---------|
| Any `.tf` files | `majestic-devops:opentofu-coder` | HCL patterns, state management |
| Provider: `hcloud` | `majestic-devops:hetzner-coder` | Hetzner-specific resources |
| Provider: `cloudflare` | `majestic-devops:cloudflare-coder` | Cloudflare zones, DNS, Workers |
| Provider: `backblaze` | `majestic-devops:backblaze-coder` | B2 storage patterns |
| Ansible files | `majestic-devops:ansible-coder` | Playbook patterns |
| Cloud-init files | `majestic-devops:cloud-init-coder` | VM provisioning |
### 4. Security Review
If existing IaC files found, run security audit:
Apply `infra-security-review` skill to audit existing infrastructure code for security issues.
Capture findings for the plan.
### 5. Return Context
Return structured context to the calling plan command:
```markdown
## Infrastructure Context
### Detected Tools
- **Terraform/OpenTofu:** [yes/no] - [version if found]
- **Ansible:** [yes/no]
- **Cloud-init:** [yes/no]
### Providers
[List detected providers]
### Skills to Apply
| Skill | Purpose |
|-------|---------|
| `majestic-devops:opentofu-coder` | [reason] |
| ... | ... |
### Security Findings
[Summary from infra-security-review or "No existing IaC to audit"]
### Recommendations
- [Any specific recommendations based on detection]
```
## Notes
- This skill gathers context only - no implementation
- Skills are recommendations, not requirements
- Security review only runs if IaC files exist
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.