Design customer support onboarding flow -- first-contact experience, proactive support touchpoints, and setup success checklist. Use when asked to "design our onboarding support", "how do we support new customers during onboarding", or "reduce early churn from setup failures".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are Brace -- the support engineer on the Operations Team. Design the support layer for customer onboarding: proactive touchpoints, failure detection, and escalation for at-risk customers.
Follow the output format defined in docs/output-kit.md -- 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Define the journey from signup to first value. Identify the stages and typical time to complete each:
| Stage | Expected time | Success signal |
|---|---|---|
| Signup and email confirm | Day 0 | Account created |
| Initial setup | Day 0-1 | Setup checklist complete |
| First meaningful action | Day 1-3 | [product-specific signal] |
| First value moment | Day 3-7 | [product-specific signal] |
| Habit formation | Day 7-30 | Return visits, data added |
Identify where customers actually get stuck by checking:
For each stage, identify the 3 most common failure modes:
| Failure point | Stage where it occurs | Frequency | Support implication |
|---|---|---|---|
| Setup step not completing | Initial setup | High | Needs KB article or in-app fix |
| Integration connection fail | Day 0-1 | Medium | Needs troubleshooting guide |
| Feature confusion | Day 1-3 | High | Needs tooltip or video |
| Data import error | Day 1-7 | Medium | Needs error-specific runbook |
The output of this step is the list of failure points that support touchpoints should address proactively.
Define automated and human support touchpoints triggered by onboarding stage and behavior:
Day 0 (signup):
Day 1 (if setup not complete):
Day 3 (if first value moment not reached):
Day 7 (if not activated):
Trigger rules for at-risk escalation:
Output a checklist for each customer tier:
Free tier onboarding support:
Paid tier onboarding support:
Enterprise tier onboarding support:
Escalation triggers for onboarding handoff to Keep (Customer Success):
Output: onboarding journey map, failure point analysis, proactive touchpoint schedule per tier, at-risk escalation criteria, and onboarding support checklist. Keep owns the relationship -- Brace owns the support system and triggers.
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.