tonone.ai

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

日本語の概要は準備中です。原文の説明を表示しています。

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

日本語の概要は準備中です。原文の説明を表示しています。

Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".

日本語の概要は準備中です。原文の説明を表示しています。

Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

日本語の概要は準備中です。原文の説明を表示しています。

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Survey legal artifacts for audit readiness. Use when asked "are we audit ready", "what legal artifacts exist", or "survey our legal docs".

日本語の概要は準備中です。原文の説明を表示しています。

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

日本語の概要は準備中です。原文の説明を表示しています。

Run a WCAG accessibility audit against a component, page, or full product. Use when asked to "run an accessibility audit", "is this WCAG compliant", or "check a11y on this page".

日本語の概要は準備中です。原文の説明を表示しています。