delta-details
Show comprehensive details for a specific delta or answer a question about it
What this skill does
# Delta Details
Show comprehensive details for a specific delta, including its definition, dependencies, dependents, existing documents, and blockers. Optionally answer a focused question about the delta.
## Input
Arguments: $ARGUMENTS
- **First token**: DELTA-ID (required) - e.g., `DLT-001`
- **Remainder**: Optional freeform question about the delta
Examples:
- `DLT-001` - full details
- `DLT-001 what's the priority?` - focused answer
- `DLT-001 is this ready to implement?` - focused answer
## Context
**You must load the following skills and read the following files before proceeding.**
### Skills
- `katachi:framework-core` - Workflow principles and status conventions
### Delta inventory
- `docs/planning/DELTAS.md` - Delta inventory
## Pre-Check
1. Verify framework is initialized:
- If `docs/planning/` doesn't exist, suggest `/katachi:init-framework` first
- If DELTAS.md missing, explain what's needed
2. Parse `$ARGUMENTS`:
- Extract the first token as DELTA-ID
- Everything after the first token is the optional question
3. Validate the delta exists:
```bash
python ${CLAUDE_PLUGIN_ROOT}/scripts/deltas.py status show <DELTA-ID>
```
If the delta is not found, show the error and suggest `/katachi:delta-summary` to see available deltas.
## Process
### 1. Gather Delta Information
Run the following commands to collect all delta data:
```bash
# Core info: name, status, priority, complexity, description, deps, dependents
python ${CLAUDE_PLUGIN_ROOT}/scripts/deltas.py status show <DELTA-ID>
# Full dependency tree visualization
python ${CLAUDE_PLUGIN_ROOT}/scripts/deltas.py deps tree <DELTA-ID>
```
### 2. Check for Documents
Check existence of working documents:
- `docs/delta-specs/<DELTA-ID>.md`
- `docs/delta-designs/<DELTA-ID>.md`
- `docs/delta-plans/<DELTA-ID>.md`
For each document that exists, read it to extract key context.
### 3. Route to Mode
Based on whether a question was provided in the input:
- **No question** → Read `references/full-details.md` within this skill directory and follow its instructions to present a comprehensive view.
- **Question provided** → Read `references/question-mode.md` within this skill directory and follow its instructions to answer the specific question.
## Error Handling
**Framework not initialized:**
- Suggest `/katachi:init-framework` first
- Don't attempt to create files manually
**Delta not found:**
- Show the error from `status show`
- Suggest `/katachi:delta-summary` to see available deltas
**No arguments provided:**
- Ask the user which delta they want details for
- Suggest `/katachi:delta-summary` to browse available deltas
## Workflow
This is a read-only command:
- No modifications to framework files
- No user iteration required
- Displays information and exits
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.