gap-analysis
Use to find what's missing — spec → implementation gaps, target → actual gaps, intended-vs-built. Produces a gap inventory with severity and effort estimates.
What this skill does
# gap-analysis
What was promised vs what was built. What was intended vs what exists. Surface gaps with severity + effort.
## Method
1. **Establish target.** What's the reference? Possible inputs:
- Spec doc
- Acceptance criteria checklist
- Architecture doc / diagram
- Test plan
- Prior implementation in another repo (for migration)
2. **Establish actual.** What exists?
- Code present
- Tests present
- Docs present
- Operational / monitored
3. **Match item-by-item.**
- **Present** ✅
- **Partial** ⚠️ (exists but incomplete or buggy)
- **Missing** ❌
4. **Severity per gap:**
- **Blocker** — capability unavailable
- **High** — capability degraded
- **Medium** — secondary functionality
- **Low** — nice-to-have
5. **Effort estimate** per gap (hours or days).
## Output shape
```
Target: <spec/doc/checklist source>
Actual: <repo / branch / deploy>
Coverage: ✅ N ⚠️ M ❌ K (out of N+M+K total items)
Gaps:
❌ [BLOCKER] <item>
Target says: <quote>
Actual: <evidence of absence>
Effort: <hrs/days>
⚠ [HIGH] <item>
Target says: <quote>
Actual: <partial impl at file:line>
Effort: <hrs/days>
⚠ [MEDIUM] <item>
...
Total effort to close gaps: <hrs/days>
```
## Rules
- **Cite both sides.** Target quote + actual evidence (or "not found in <searched paths>").
- **Don't conflate "not yet built" with "not designed".** Flag the latter as a target ambiguity.
- **Severity by capability impact, not effort.** Easy fix can still be a blocker.
- **Search broadly before declaring missing.** Capability may be implemented under a different name.
## Anti-patterns
- Counting tests as items (separate analysis)
- Marking partial as missing (or vice versa) without evidence
- Effort estimates without scope (always say what's in the estimate)
- Ignoring "extra" — items in actual that aren't in target (might be rot or prudent additions)
## When NOT to use
- No clear target reference — gap-analysis needs both sides
- Pre-spec stage — `/improve-spec` first
- Ongoing development — wait for a milestone
## Subagent dispatch
- `Explore` to map actual
- `general-purpose` for the matching pass
- Memory MCP for what was decided in prior sessions
## Value over native CC
CC will compare two things if asked. CC won't naturally produce structured target ↔ actual matrix with severity + effort columns. The structure IS the value — feeds into prioritisation.
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.