Menu

Individual skill

apex-takeover

0upvotes

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".

plugins/ai-agency/tonone/skills/apex-takeover/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,917
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: claude-code

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top