delta-summary
Display a summary table of available deltas or show recommended next deltas
What this skill does
# Delta Summary
Display a summary table of all deltas with optional filtering by status, priority, or show recommended next deltas to work on.
## Input
Filter: $ARGUMENTS (optional)
- **No filter**: Show all deltas sorted by priority
- **Status filter**: Partial match on status (e.g., "Spec", "Implementation", "Not Started")
- **Priority keywords**: "critical", "high", "medium", "low", "backlog" → filter by priority level
- **"next work"**: Show top 5 recommended deltas using the `next` command
## Context
**You must load the following skills and read the following files before proceeding.**
### Skills
- `katachi:framework-core` - Workflow principles
### Delta inventory
- `docs/planning/DELTAS.md` - Delta inventory
## Pre-Check
Verify framework is initialized:
- If `docs/planning/` doesn't exist, suggest `/katachi:init-framework` first
- If DELTAS.md missing, explain what's needed
## Process
### 1. Validate Framework
Check for required files:
- `docs/planning/DELTAS.md`
If missing, suggest `/katachi:init-framework` first.
### 2. Parse Input and Determine Mode
Analyze $ARGUMENTS to determine which command to run:
| Input Pattern | Command | Behavior |
|--------------|---------|----------|
| (empty) | `summary` | Show all deltas, sorted by priority |
| "next work" or "next" or "recommended" | `next --top 5` | Show top 5 recommended deltas |
| "critical" | `summary --priority 1` | Show only Critical priority |
| "high" | `summary --priority 2` | Show only High priority |
| "medium" | `summary --priority 3` | Show only Medium priority |
| "low" | `summary --priority 4` | Show only Low priority |
| "backlog" | `summary --priority 5` | Show only Backlog priority |
| "ready" | `summary --ready` | Show only deltas ready to implement |
| Anything else | `summary <filter>` | Treat as status filter |
### 3. Execute Appropriate Command
#### Mode: Next Work (Recommended Deltas)
When user asks for "next work", "next", or "recommended":
```bash
python ${CLAUDE_PLUGIN_ROOT}/scripts/deltas.py next --top 5
```
This shows the top 5 deltas recommended to work on next, ranked by:
- Priority level (Critical/High first)
- Impact (how many other deltas are blocked)
- Complexity (prefer easier wins)
#### Mode: Ready (Unblocked Deltas)
When user asks for "ready":
```bash
python ${CLAUDE_PLUGIN_ROOT}/scripts/deltas.py summary --ready
```
This shows only deltas whose dependencies are all complete, meaning they can be started immediately.
#### Mode: Priority Filter
When user specifies a priority keyword:
```bash
python ${CLAUDE_PLUGIN_ROOT}/scripts/deltas.py summary --priority <level>
```
#### Mode: Status Filter (Default)
For any other filter:
```bash
python ${CLAUDE_PLUGIN_ROOT}/scripts/deltas.py summary $ARGUMENTS
```
### 4. Display Results
The command outputs directly to the console:
- **Summary mode**: Formatted table with ID, Name, Status, Priority, Complexity, and Impact
- **Next mode**: Numbered list of top recommended deltas with rationale
## Error Handling
**Framework not initialized:**
- Suggest `/katachi:init-framework` first
- Don't attempt to create files manually
**No matching deltas:**
- The command will display "No deltas found matching..."
- This is expected behavior when filter doesn't match any deltas
**Invalid input:**
- If the user types an unrecognized filter, treat it as a status filter
- The underlying command will handle unknown filters gracefully
## Examples
```bash
# Show all deltas (sorted by priority)
/katachi:delta-summary
# Show recommended next deltas (top 5)
/katachi:delta-summary next work
# Show only Critical priority deltas
/katachi:delta-summary critical
# Show only High priority deltas
/katachi:delta-summary high
# Show only Spec-related deltas (status filter)
/katachi:delta-summary Spec
# Show only Implementation-related deltas
/katachi:delta-summary Implementation
# Show only deltas ready to implement (unblocked)
/katachi:delta-summary ready
# Show only "Not Started" deltas
/katachi:delta-summary "Not Started"
```
## Workflow
This is a read-only command for viewing delta status:
- No modifications to framework files
- No user iteration required
- Displays current state and exits
- Smart parsing: detects priority keywords and "next work" automatically
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.