Stats
Actions
Tags
From tonone
Takes ownership of inherited codebases via three-phase reconnaissance: maps architecture/infra/pipelines/security/observability, conducts targeted deep dives, synthesizes takeover report. Use when acquiring or handed-off systems.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tonone:apex-takeoverThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
Phase 1 — Reconnaissance (parallel specialist dispatches):
Run these in parallel — they are independent:
Deliver Phase 1 findings before proceeding.
Phase 2 — Deep Dive (based on Phase 1 findings, only dispatch what's relevant):
Skip specialists whose domain doesn't apply. Deliver Phase 2 findings before proceeding.
Phase 3 — Takeover Report. Synthesize all findings, then route through atlas-report:
Gather these sections for the report:
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.
npx claudepluginhub tonone-ai/tonone --plugin evalsSystem 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".
Reverse-engineers existing projects to produce auto-anchored Design Docs, API contracts, and Threat Models from real code, IaC, and observability data.
Runs a repository engineering audit with SARIF-compatible evidence, 4-level confidence scoring, and OpenSSF-style health evaluation. Use when assessing code quality or repository health.