5d-gap-analysis

Included with Lifetime

$97 forever

Analyze the gap between current state and specification to identify all required changes. Use when: (1) After SPEC phase in 5D-SDD workflow, (2) Spec exists and implementation is about to begin, (3) User asks 'what needs to change' or 'what's the delta,' (4) Assessing scope of work. This phase prevents surprise discoveries during implementation.

General

What this skill does


# GAP ANALYSIS Phase

Identify everything that must change to implement the spec.

## Multi-Quadrant Gap Analysis

### 1. Code Gaps (Individual Outer)

Compare spec to current implementation:
- New components needed
- Existing components requiring modification
- Components to deprecate/remove
- New dependencies to add

Output: List of concrete code changes.

### 2. Knowledge Gaps (Individual Inner)

Identify what must be learned:
- Unfamiliar technologies in spec
- Domain knowledge needed
- Patterns/approaches to research

Output: Learning tasks before or during implementation.

### 3. System Gaps (Collective Outer)

Identify infrastructure/tooling needs:
- New services or environments
- CI/CD changes
- Monitoring/observability additions
- Database migrations

Output: Infrastructure tasks.

### 4. Alignment Gaps (Collective Inner)

Identify communication needs:
- Stakeholders who need to review spec
- Teams affected by changes
- Documentation updates needed
- Training or handoff required

Output: Alignment tasks.

## Gap Assessment Process

1. **Read the spec thoroughly**
2. **Examine current codebase** (if exists)
3. **For each spec item:** Does current state satisfy it? If no, document the gap.
4. **Categorize gaps** by quadrant
5. **Estimate complexity** for each gap: trivial / moderate / complex / unknown

## Additional 5D Checks

### Thinking Level Gaps (Depth)

- Are any gaps caused by Level 2 (dogmatic) thinking in the spec?
- Do gaps require Level 3+ thinking to resolve (holding contradictions)?
- Where might we be defending assumptions rather than solving problems?

### Skill Dependency Gaps (Height)

- What capabilities are missing that block multiple gaps?
- Which gap, if resolved, would unlock others?
- What learning is prerequisite to implementation?

### Time Pattern Gaps

- What historical patterns predict where gaps will appear?
- Are we repeating mistakes from past projects?
- What must we "transcend and include" from current approaches?

### Identity Trap Gaps

- Are any gaps being minimized because they threaten core assumptions?
- What gaps are we avoiding looking at closely?

## Output Format

```
## Gap Analysis

### Code Gaps
| Gap | Spec Item | Complexity | Notes |
|-----|-----------|------------|-------|
| [gap] | [ref] | [level] | [notes] |

### Knowledge Gaps
- [topic]: [why needed] - [how to address]

### System Gaps
- [gap]: [what's needed]

### Alignment Gaps
- [gap]: [who/what]

### Unknowns
- [unknown]: [how to resolve]

**Total gaps:** [count]
**High-complexity gaps:** [count]
**Blockers:** [any gaps that block others]
```

## Exit Criteria

Proceed to TASKS when:
- All spec items have been assessed
- No "unknown" complexity items remain unaddressed
- Blockers are identified
- User has reviewed gap scope

Files: 1

Size: 3.1 KB

Complexity: 14/100

Category: General

Source: https://github.com/tapania/5d-skills/tree/main/skills/5d-gap-analysis

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts