ecm-studio

Plan safe batches of ECM Studio capability changes from a JSON operation list by validating IDs, names, parents, hierarchy rules, lifecycle operations, and command ordering before execution. Use for bulk reparenting, renaming, retiring, deleting draft leaves, or merge planning in ECM model repositories.

Safely create, update, move, retire, merge, and delete capabilities in ECM Studio repositories that store authoritative data in ecm/capabilities.jsonl and ecm-studio.json. Use this whenever the user asks to add capabilities, rename or reparent capabilities, change lifecycle state, merge duplicates, delete mistaken draft leaves, or otherwise modify capability data in an ECM repo, even if they do not mention JSONL files or ECM Studio by name.

Audit governance and traceability evidence in ECM Studio model repositories, including structural-operation rationale, downstream handling, retired capability traceability, ownership metadata, audit file health, release records, and publish evidence. Use before governance reviews and releases.

Analyze impact for a capability in ECM Studio model repositories by finding ancestors, descendants, replacement links, audit events, and generic JSON references in mappings, downstream consumers, change requests, and tasks. Use before retire, merge, delete, move, or major capability changes.

Convert external CSV capability exports into ECM Studio import-ready CSV, JSONL, or bundled JSON for ECM model repositories. Use when Codex needs to map source columns to capability fields, generate stable import files, validate import shape, or prepare data for ECM Studio import without editing the live ecm/capabilities.jsonl file.

Summarize ECM Studio capability model differences between two Git refs in an ECM model repository, including added, removed, renamed, moved, retired, lifecycle-changed, metadata-changed, and type-transitioned capabilities. Use for branch reviews, release notes, and scenario comparison.

Review ECM Studio model repositories for capability quality issues such as weak descriptions, missing ownership metadata, duplicate-like names, uneven decomposition, lifecycle inconsistencies, and missing tags or domains. Use before reviews, releases, restructuring, or governance checks.

Validate, inspect, and diagnose ECM Studio repositories that store capability data in ecm/capabilities.jsonl. Use this whenever the user asks whether an ECM repo is valid, wants to inspect capability IDs and paths, needs help understanding capability hierarchy issues, or before and after capability edits in an ECM repo, even if they only say the model seems broken or inconsistent.

Prepare ECM Studio model repositories for release by validating repository state, checking Git readiness, inspecting model and publish history, drafting release notes, and identifying blockers before an ECM release is cut or published. Use for release readiness checks, not for publishing.