aiwg-sync
Ensure the session's AIWG installation is current and correctly deployed to the active provider
What this skill does
# AIWG Sync You ensure the current session's AIWG installation is up-to-date and correctly deployed to the active provider. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "is the framework current" → sync dry-run check - "re-deploy" → force redeploy to active provider - "aiwg drift" → deploy drift detected, sync needed ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Sync request | "make sure AIWG is current" | Run `aiwg sync` | | Version check | "is AIWG up to date?" | Run `aiwg sync --dry-run` | | Update request | "update AIWG" | Run `aiwg sync` | | Refresh request | "refresh the framework" | Run `aiwg sync` | | Provider deploy | "deploy latest to copilot" | Run `aiwg sync --provider copilot` | | Dry run | "check if AIWG needs updating" | Run `aiwg sync --dry-run` | ## Behavior When triggered: 1. **Extract intent**: - Is this a check only (dry-run) or should changes be applied? - Is a specific provider mentioned? - Are specific frameworks mentioned? 2. **Run the appropriate command**: ```bash # Default: full sync aiwg sync # Check only (no changes) aiwg sync --dry-run # Provider-specific aiwg sync --provider copilot # Specific frameworks only aiwg sync --frameworks sdlc,rlm # Machine-readable (for orchestration) aiwg sync --quiet ``` 3. **Report the result** inline — summarize what changed or what would change. ## Examples ### Example 1: Simple check **User**: "Is AIWG up to date?" **Extraction**: Check-only request, no provider specified **Action**: ```bash aiwg sync --dry-run ``` **Response**: "AIWG is current (v2026.3.15). All 2 frameworks are deployed to claude-code. No changes needed." ### Example 2: Full sync **User**: "Make sure we're running the latest AIWG" **Extraction**: Full sync requested **Action**: ```bash aiwg sync ``` **Response**: "Updated AIWG 2026.3.12 -> 2026.3.15 and re-deployed sdlc-complete to claude-code. Health check passed." ### Example 3: Provider-specific **User**: "Deploy the latest AIWG to GitHub Copilot" **Extraction**: Sync to copilot provider **Action**: ```bash aiwg sync --provider copilot ``` **Response**: "Synced AIWG to copilot. SDLC framework deployed to .github/agents/ and .github/copilot-instructions.md." ## Clarification Prompts If the user's intent is ambiguous: - "Would you like me to check what needs updating (dry run), or go ahead and sync?" - "Which provider should I sync to? (detected: claude-code)" ## References - @$AIWG_ROOT/src/cli/handlers/sync.ts — Sync command handler - @$AIWG_ROOT/docs/cli-reference.md — CLI reference - @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/rules/self-maintenance.md — Self-maintenance rule
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.