mainframe-planning
Create a transformation guide for replacing mainframe-specific COBOL constructs with standard COBOL equivalents. Use when preparing COBOL code for local execution or migration.
What this skill does
Create a comprehensive transformation guide that maps each mainframe dependency to its standard COBOL replacement. This guide is a prerequisite for the actual transformation — DO NOT modify any code, only create the guide. ## Output Format Document each mainframe-specific construct with: 1. **Pattern**: The mainframe construct (e.g., `EXEC CICS READ FILE(...)`) 2. **Replacement**: The standard COBOL equivalent 3. **Error Handling**: How to replicate the mainframe's error behavior - Map CICS RESP/RESP2 codes to FILE STATUS equivalents - Specify which FILE STATUS values to check (e.g., 00=success, 23=not found, 35=file not exists) 4. **Resource Cleanup**: Any cleanup the replacement requires (CICS auto-manages resources; file I/O does not) 5. **Edge Cases**: Behavior differences between mainframe and standard COBOL ## Constructs to Address ### Data Operations (CICS/IMS/VSAM) - READ, WRITE, REWRITE, DELETE operations - STARTBR, READNEXT, READPREV (browse operations) - CICS error handling: HANDLE CONDITION, RESP/RESP2 options - VSAM → sequential or indexed file I/O ### UI/Terminal Operations (BMS maps, screens) - SEND MAP, RECEIVE MAP → these can be MOCKED or stubbed - Screen I/O is not needed for business logic validation - Document how to replace with simple ACCEPT/DISPLAY or test harness stubs - Focus on preserving the data flow, not the UI interaction ### Other Mainframe Constructs - Mainframe data types (COMP-3 packed decimal, etc.) - JCL-embedded constructs - IMS calls (if present) ## Critical Requirements - Every CICS command that can fail MUST have an error handling replacement documented - UI operations should be clearly marked as "mock/stub" so the agent doesn't get stuck on them - Prefer: file-based I/O over mainframe I/O, standard data types over mainframe types ## Common Mappings Reference ### FILE STATUS Codes | Code | Meaning | CICS Equivalent | |------|---------|-----------------| | 00 | Success | Normal completion | | 23 | Record not found | NOTFND condition | | 35 | File does not exist | NOTOPEN condition | | 22 | Duplicate key | DUPREC condition | | 3x | I/O errors | Various IOERR conditions | ### CICS to Standard COBOL | CICS Command | Standard COBOL | |--------------|----------------| | `EXEC CICS READ FILE(...)` | `READ filename INTO...` | | `EXEC CICS WRITE FILE(...)` | `WRITE record-name FROM...` | | `EXEC CICS REWRITE FILE(...)` | `REWRITE record-name FROM...` | | `EXEC CICS DELETE FILE(...)` | `DELETE filename RECORD` | | `EXEC CICS STARTBR FILE(...)` | `START filename KEY...` | | `EXEC CICS READNEXT FILE(...)` | `READ filename NEXT INTO...` |
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.