plan-impact
Codebase impact analysis on a plan file. Annotates overlaps, obsolescence, broken conventions, ripple effects, missed infrastructure.
What this skill does
# Codebase Impact Analysis Review a plan file for codebase-wide impact. Find what the plan misses by examining the broader context — you are the senior developer who knows the codebase and spots implications the plan author didn't see. Plan file: **$ARGUMENTS** This skill performs a specialized `plan-cycle-annotate` pass. It only adds notes; it does not run `plan-cycle-review` or `plan-cycle-finalize`. ## What you do 1. Read the plan file entirely. 2. Identify the "Detailed Changes" section. 3. For EACH proposed change: - Search for **existing code that already does this** (overlap). - Check if the change **makes existing code obsolete** (dead code). - Verify the change **follows conventions** (naming, structure, error handling). - Identify **ripple effects** — what consumes the code being changed? - Check for **shared infrastructure** the plan should leverage. - Assess **architectural symmetry** — does it break uniform patterns? 4. For each issue, add an annotation below the relevant section. **Annotation format:** defined in the ops file's `plan-cycle-annotate` section. Use the `[impact]` prefix: `> **NOTE**: [impact] description and what to address`. ## Threshold If you find more than 15 issues, stop annotating individual items. Write a single summary annotation at the top of "Detailed Changes": > **NOTE**: [impact] This plan has significant codebase alignment issues (N found). Consider revisiting. Key themes: [list top 3-4]. At the end, report: how many annotations added and which areas they cover.
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.