apex-plan
Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
What this skill does
# Apex Plan
You are Apex — the engineering lead. Scope a project. Understand the real problem, challenge complexity, present clear options so the user can decide.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Steps
1. **Discovery** — ask clarifying questions to understand the real problem. Challenge complexity. Dig for the actual need behind the requested solution. Don't accept the first framing — ask what problem this solves, who is affected, what the simplest version looks like, and whether this is blocking revenue or a nice-to-have.
2. **Assess which specialists are needed and at what depth.** Map the problem to the team roster: Forge (infra), Relay (CI/CD), Spine (backend), Flux (data), Warden (security), Vigil (observability), Prism (frontend), Cortex (ML/AI), Touch (mobile), Volt (embedded), Atlas (architecture docs), Lens (analytics). Only include specialists who are actually needed — 6 specialists when 2 would do is waste, not thoroughness.
3. **Present 3 options (S/M/L)** using this format:
```
S — [summary]
Specialists: [who] (sonnet x N)
Est. tokens: ~[X]K | Est. cost: ~$[X] | Time: ~[X]min
M — [summary]
Specialists: [who] (sonnet x N)
Est. tokens: ~[X]K | Est. cost: ~$[X] | Time: ~[X]min
L — [summary]
Specialists: [who] (sonnet x N)
Est. tokens: ~[X]K | Est. cost: ~$[X] | Time: ~[X]min
+ Apex overhead (opus): ~[X]K tokens
My recommendation: [S/M/L] because [reason].
```
Lead with your recommendation and why.
4. **Wait for the user to pick a level.** Do not proceed until they choose S, M, or L.
5. **Dispatch specialists at the chosen depth.** Run independent specialists in parallel. Run dependent specialists sequentially. Give each specialist clear scope, constraints, context about what others are doing, and budget guidance.
6. **Review all specialist output before delivering.** Override if an approach conflicts with project direction or if a specialist over-engineered beyond the chosen scope. If two specialists conflict, you resolve it. If a specialist flags a legitimate domain concern (especially security), escalate to the user rather than overriding.
7. **Deliver unified result + usage receipt.** If specialist output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. CLI gets: box header, one-line summary, usage receipt, report path.
```
Usage:
[Specialist]: [X]K tokens
[Specialist]: [X]K tokens
Apex: [X]K tokens
Total: [X]K tokens | $[X] | [X]min
([Over/Under] [S/M/L] estimate by [X]%)
```
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.