feynman-decision

Included with Lifetime

$97 forever

Analyze technical options with structured comparison matrices, scoring, and ADR draft generation. Use when the user needs help choosing between technologies, architectures, or implementation approaches.

General

What this skill does


# Technical Decision Analysis

Analyze the technical decision: $ARGUMENTS

## Workflow

### Step 1: Understand Decision Context

- What's being decided
- What options exist
- Why it matters
- What's at stake

### Step 2: Define Evaluation Criteria

Infer criteria based on decision type:

**Technology Selection**: Maturity, performance, developer experience, documentation, future-proofing, migration path

**Architecture Decision**: Complexity, maintainability, scalability, user experience, cost

**Implementation Approach**: Time to implement, code quality, testability, flexibility

### Step 3: Research Each Option

For each option gather facts from official documentation, benchmarks, real-world usage, known issues. Analyze pros, cons, tradeoffs, and risks.

### Step 4: Score Options

Create comparison matrix:

| Criterion | Weight | Option A | Option B |
|-----------|--------|----------|----------|
| {Criterion} | H/M/L | score/5 | score/5 |

### Step 5: Generate Recommendation

- **Selected Option**: Which one to choose
- **Rationale**: Why (based on criteria + context)
- **Tradeoffs**: What we're accepting
- **Risks**: What to watch out for
- **Validation**: How to verify it was right

### Step 6: Create ADR Draft

```markdown
# ADR-{N}: {Decision Title}

**Status**: Proposed
**Date**: {DATE}
**Context**: {WHY_NEEDED}
**Decision**: We will {SELECTED_OPTION}
**Rationale**: {WHY_THIS_CHOICE}
**Consequences**: Positive, Negative, Neutral
**Alternatives Considered**: {REJECTED_OPTIONS}
```

## Decision Quality Principles

1. **Evidence-based**: Backed by research and data
2. **Context-aware**: Consider project constraints
3. **Explicit about tradeoffs**: No option is perfect
4. **Reversible-aware**: Note if/how decision can change
5. **Validated**: Include how to verify correctness

Files: 2

Size: 3.6 KB

Complexity: 14/100

Category: General

Source: https://github.com/mpazaryna/agentic-factory/tree/main/skills/feynman-decision

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