Survey legal artifacts for audit readiness. Use when asked "are we audit ready", "what legal artifacts exist", or "survey our legal docs".
The English summary is being prepared. Showing the original description.
Design a performance benchmark for an API — test scenarios, metrics, and tooling. Use when asked to "benchmark this API", "design a load test", or "measure throughput".
The English summary is being prepared. Showing the original description.
Survey existing compliance artifacts — policies, audits, certifications. Use when asked "what compliance docs do we have", "survey our policies", or "inventory our compliance artifacts".
The English summary is being prepared. Showing the original description.
Design ticket triage system -- routing rules, priority tags, queue structure, and first-response automation. Use when asked to "design our ticket routing", "how should we tag tickets", "set up our helpdesk", or "reduce time to first response".
The English summary is being prepared. Showing the original description.
Review and redline a contract — flag risk, missing clauses, one-sided terms. Use when asked to "review this contract", "redline this agreement", or "is this contract risky".
The English summary is being prepared. Showing the original description.
Audit AI spend — per-model cost breakdown, top consumers, waste identification, optimization levers. Use when asked "why is our AI bill so high", "audit LLM spend", or "where is our token waste".
The English summary is being prepared. Showing the original description.
Design cost reduction strategies — model tiering, prompt compression, caching, batch inference. Use when asked to "reduce our AI costs", "set up model tiering", or "cut LLM spend".
The English summary is being prepared. Showing the original description.
Map AI cost topology — billing attribution, team-level spend, forecast vs actuals, alert gaps. Use when asked to "map our AI spend", "who is spending on LLMs", or "set up AI cost attribution".
The English summary is being prepared. Showing the original description.
Reach ANY tonone specialist on demand, even ones not installed in this session's roster — no restart needed. Use when asked "which agent handles this", "reach a specialist we didn't install", "route this to the right agent", or whenever a scoped apex-profile roster is missing the right hat for the job.
The English summary is being prepared. Showing the original description.
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
The English summary is being prepared. Showing the original 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".
The English summary is being prepared. Showing the original description.
Spawn-count analytics for the tonone roster — which agents this project actually uses, from local session transcripts. Use when "which agents do we actually use", "show tonone stats", "prune the roster", or before running apex-profile.
The English summary is being prepared. Showing the original description.
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
The English summary is being prepared. Showing the original description.
Write support playbook -- response templates, issue-type runbooks, tone guide, and common resolution paths. Use when asked to "write support templates", "build a support playbook", "train our support agents", or "standardize our support responses".
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)