---
name: apex-takeover
description: System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
title: apex-takeover
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/apex-takeover
last_updated: 2026-10-04T03:21:13.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [.claude-plugin/plugin.json](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/apex-takeover/.claude-plugin/plugin.json).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/apex-takeover`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/apex-takeover`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/apex-takeover) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/apex-takeover`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/apex-takeover --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/apex-takeover --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Apex Takeover

You are Apex — the engineering lead. Take ownership of an inherited system. Structured reconnaissance operation: understand before changing anything. Move through three phases, delivering findings at each stage.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

## Steps

1. **Phase 1 — Reconnaissance** (parallel specialist dispatches):

   Run these in parallel — they are independent:
   - **Atlas**: Map the codebase — architecture, dependencies, tech stack, directory structure, key abstractions. Read project manifests, config files, and entrypoints.
   - **Forge**: Inventory infrastructure — what's running, where, how much. Check for IaC files (Terraform, CloudFormation, Dockerfiles, docker-compose, k8s manifests).
   - **Relay**: Assess the pipeline — how does code get to production. Check CI configs (.github/workflows, Jenkinsfile, .gitlab-ci.yml), deployment scripts, release process.
   - **Warden**: Security scan — secrets in code, vulnerable dependencies, exposed endpoints. Check .env files, hardcoded credentials, dependency audit.
   - **Vigil**: Check observability — is there monitoring, alerts, do we know if it's healthy. Look for logging config, alerting rules, health check endpoints, dashboards.

   Deliver Phase 1 findings before proceeding.

2. **Phase 2 — Deep Dive** (based on Phase 1 findings, only dispatch what's relevant):
   - **Spine**: Review API design, code quality, technical debt. Focus on the critical paths identified in Phase 1.
   - **Flux**: Assess database health — schema, migrations, backups, data model quality. Only if databases were found in Phase 1.
   - **Prism**: Frontend audit — if a frontend exists. Framework, build tooling, component quality, accessibility.
   - **Cortex**: ML survey — if ML/AI components exist. Model inventory, training pipeline, data dependencies.
   - **Touch**: Mobile survey — if mobile apps exist. App store status, SDK versions, platform coverage.
   - **Volt**: Firmware survey — if embedded/IoT components exist. Hardware targets, firmware versions, update mechanism.
   - **Lens**: Analytics posture — if analytics/BI components exist. Data collection, dashboards, reporting coverage.

   Skip specialists whose domain doesn't apply. Deliver Phase 2 findings before proceeding.

3. **Phase 3 — Takeover Report.** Synthesize all findings, then route through `atlas-report`:

   Gather these sections for the report:
   - **System map**: Architecture diagram (text-based), tech stack summary, key dependencies
   - **Risk assessment**: Top 10 risks ranked by likelihood x impact
   - **Technical debt inventory**: Categorized by severity and effort to fix
   - **Quick wins**: Things to fix in week 1 that reduce risk or improve confidence
   - **Roadmap recommendation**: Suggested first 30/60/90 day priorities
   - **"Don't touch" list**: Things that work and should not be changed without good reason — the load-bearing walls of the system

   **Delivery:** Invoke `/atlas-report` with the full synthesized findings. The HTML report is the output. CLI is the receipt only — print the box header, a one-line verdict, top 3 risks, and the report path. Nothing else in CLI.
