apex-takeover
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".
git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/apex-takeover && cp -r /tmp/apex-takeover/plugins/ai-agency/tonone/skills/apex-takeover ~/.claude/skills/apex-takeoverSKILL.md
# 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.
Guard the beads execution record: enforce the write-flush-verify discipline that defeats the bd rapid-write race, audit epic dependency graphs for cycles and orphans, catch closures whose title overstates what shipped, flag open beads carrying no disposition or a disproven premise, and reconcile bd against its GitHub and Plane projections. Owns RECORD INTEGRITY; delegates graph analysis to bead-dependency-mapper and epic-closure drift to bead-epic-auditor rather than duplicating them. Use before closing an epic, after any batch of bd writes, when a bead premise looks stale, or when auditing whether the record matches reality. Trigger with "audit beads", "check the bead DAG", "did that close actually land", "bead hygiene".
Verify every factual assertion in a diff, PR body, commit message, bead note, or governing doc against the actual repository, and fail anything that cannot be substantiated by a command. Use before merging any PR that makes claims about counts, coverage, consumers, enforcement, provenance, or certification, and when auditing standing docs for rot. Trigger with "verify claims", "check this PR body", "is this claim true", "claim audit".
Design and build Omarchy (Quickshell/QML) bar-widget, panel, and service plugins that actually work on a stock install. Knows the hard runtime constraint (no node on the graphical session PATH), the first-party contracts (BarWidget, Panel, KeyboardPanel, PanelKeyCatcher, Service), the curl-from-QML data pattern, FileView persistence, and the marketplace submission bar. Use when starting a new Omarchy plugin, porting a plugin off an external runtime, wiring a service to a bar widget, or deciding how a widget should fetch and persist. Trigger with "build an omarchy plugin", "omarchy widget", "quickshell plugin", "port this plugin to QML".
Audit an Omarchy plugin before it reaches the marketplace: prove it installs and runs on a stock box (no node/python on the session PATH), run the omarchy-submit gate lane, validate on the rig with omarchy-plugin-validate and qmllint, and check the QML security invariants and first-party idiom contracts. Read-only: it reports and blocks, it does not rewrite the plugin. Use before submitting an entry, after any data-layer change, or when a plugin works on the dev box and you need to know whether it works for a real user. Trigger with "audit this omarchy plugin", "is this plugin submission ready", "will this plugin work when installed".
Audit and fix Claude Code SKILL.md files against enterprise compliance standards: frontmatter completeness, required body sections, and style. Use when validating or repairing skills in a plugin directory. Trigger with "audit skill", "fix skill compliance".
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|