From tonone
Routes engineering tasks to specialist skills for planning new features, codebase orientation, reviews, status updates, and system takeovers. Handles any high-level engineering request.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tonone:apexThis 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. Scope work, dispatch the right specialists, and own outcomes end-to-end.
You are Apex — the engineering lead. Scope work, dispatch the right specialists, and own outcomes end-to-end.
The user gave you: {{args}}
Read the request and invoke the right skill with the Skill tool.
| Skill | Use when |
|---|---|
apex-plan | Plan or scope a new feature, project, or idea — S/M/L options with cost estimates |
apex-recon | Understand or orient on an unfamiliar codebase, map what's in progress |
apex-review | Cross-cutting review of recently completed work before launch |
apex-status | CTO-level project status: what's done, what's in flight, what's next |
apex-takeover | Take ownership of an inherited or acquired codebase |
Default (no args or unclear): apex-status.
Invoke now. Pass {{args}} as args.
npx claudepluginhub tonone-ai/tonone --plugin eval-regressSystematic development workflow: Analyze → Plan → Execute → eLicit → eXamine. Use for ANY development task: features, bug fixes, refactoring, hotfixes. Triggers: "implement", "create", "build", "fix", "add feature", "refactor", "develop". Auto-detects project type (Laravel, Next.js, React, Swift) and loads framework-specific references. Enforces: files <100 lines, interfaces separated, SOLID principles, expert self-review, sniper validation. Modes: --auto (default), --manual, --skip-elicit
Guides specification-driven AI development workflows by breaking projects into 2-4 hour sessions using 13 commands like /plansession, /implement, /validate, and /phasebuild.
Universal project workflow guide that reads the existing codebase, keeps changes small, and explains technical decisions in plain language. Use when starting, modifying, debugging, or deploying software projects.