ATLAS Toolkit Discovery
Overview
Use this skill during the discovery phase of COBOL modernization, before conversion work begins. The upstream repository, Vivantro/atlas-toolkit-discovery, is a sample skill for COBOL legacy inventory and go/no-go classification.
Compatibility: COBOL, legacy inventory, and modernization readiness assessment.
Workflow
- Collect source inventory: COBOL programs, copybooks, JCL, control cards, data definitions, test assets, and deployment notes.
- Build a dependency index covering calls, copybook inclusion, file usage, database access, schedules, and external systems.
- Score readiness by complexity, missing assets, test coverage, business criticality, operational risk, and SME availability.
- Classify each application or component as go, conditional go, defer, or no-go for modernization.
- Recommend the next step: deeper reverse engineering, wrapper strategy, data remediation, test-data recovery, or migration execution.
Guardrails
- Do not start conversion until discovery has identified required copybooks, sample data, and integration dependencies.
- Keep readiness scoring evidence-based and include confidence levels.
- Separate technical complexity from business priority so decision makers can trade risk against value explicitly.
- Preserve unknowns as named risks rather than filling gaps with assumptions.
Expected Output
Produce an inventory table, dependency summary, readiness classification, risk register, and recommended modernization sequence.
1---2name: atlas-toolkit-discovery3description: Inventory COBOL estates and classify modernization go/no-go readiness with ATLAS toolkit discovery.4license: MIT5---67# ATLAS Toolkit Discovery89## Overview1011Use this skill during the discovery phase of COBOL modernization, before conversion work begins. The upstream repository, [Vivantro/atlas-toolkit-discovery](https://github.com/Vivantro/atlas-toolkit-discovery), is a sample skill for COBOL legacy inventory and go/no-go classification.1213Compatibility: COBOL, legacy inventory, and modernization readiness assessment.1415## Workflow16171. Collect source inventory: COBOL programs, copybooks, JCL, control cards, data definitions, test assets, and deployment notes.182. Build a dependency index covering calls, copybook inclusion, file usage, database access, schedules, and external systems.193. Score readiness by complexity, missing assets, test coverage, business criticality, operational risk, and SME availability.204. Classify each application or component as go, conditional go, defer, or no-go for modernization.215. Recommend the next step: deeper reverse engineering, wrapper strategy, data remediation, test-data recovery, or migration execution.2223## Guardrails2425- Do not start conversion until discovery has identified required copybooks, sample data, and integration dependencies.26- Keep readiness scoring evidence-based and include confidence levels.27- Separate technical complexity from business priority so decision makers can trade risk against value explicitly.28- Preserve unknowns as named risks rather than filling gaps with assumptions.2930## Expected Output3132Produce an inventory table, dependency summary, readiness classification, risk register, and recommended modernization sequence.
autohandai