Results for “exit-triggers”

Trigger: circuit breaker, exponential backoff, jitter delay, connection timeout, API retry. Scope: Client request resiliency, API retries, fault isolation. Boundary: Excludes visual state loading skeletons.

Plan team outings with activities and logistics. TRIGGERS - Use when user needs help with team-outing related tasks.

Plan team outings with activities and logistics. TRIGGERS - Use when user needs help with team-outing related tasks.

Trigger: form inputs, wizards, checkout forms, multistep forms, validation UI, input focus. Scope: User-friendly forms design, input constraints, progressive disclosure. Boundary: Excludes backend database schemas or server-side API validation.

Write leave policies covering PTO, sick, and family leave. TRIGGERS - Use when user needs help with leave-policy related tasks.

Use to find cancellation, downgrade and switching intent in support conversations, and to be honest about how much of your churn support can actually see. Trigger for "which customers are at risk of leaving", "find cancellation intent", "customers asking how to export their data", "top reasons customers asked to close their account", competitor mentions, or building a churn early-warning signal from support data.

Detect insider threat behavioral indicators including unusual data access, off-hours activity, mass file downloads, privilege abuse, and resignation-correlated data theft.

Turn a buying signal into a timely, relevant touch. Read the trigger (funding, a new hire, a product launch, a job posting, a tech change), pick the angle it earns, and write the outreach while it is still fresh. Built for B2B outbound teams, customizable to your signals and your voice. Trigger on "someone just raised, what do I send", "they posted a job, draft outreach", "new VP started, reach out", "write a touch off this news", or any signal-to-message task.

Conduz investigação de incidentes com método: triagem, hipóteses, mitigação, RCA e postmortem, priorizando evidências e confirmação humana.

Trigger: security rules, credential leaks, auth tokens, input sanitization, threat model. Scope: Software security guidelines, threat prevention, secure data handling. Boundary: Excludes client-side web browser vulnerabilities.

Use to design and measure proactive outbound support that prevents inbound contacts without creating new ones. Trigger for "proactive support", "prevent tickets with outbound", outage notifications, shipment alerts, eligibility and suppression rules, measuring prevented contacts, or proactive messaging opt-out.

Write cease and desist letters with legal basis. TRIGGERS - Use when user needs help with cease-desist related tasks.

Build event budgets with categories and contingency. TRIGGERS - Use when user needs help with event-budget related tasks.

Trigger or resolve a PagerDuty incident for on-call escalation

Create grant budgets with line items and justifications. TRIGGERS - Use when user needs help with grant-budget related tasks.

Trigger: shopping cart, checkout conversion, checkout flow, payment trust, pricing layout. Scope: Commerce UX optimization, trust badges, checkout pathways. Boundary: Excludes payment gateway API integrations or backend authentication.

Investigates insider threat indicators including data exfiltration attempts, unauthorized access patterns, policy violations, and pre-departure behaviors using SIEM analytics, DLP alerts, and HR data correlation.

Build event budgets with categories and contingency. TRIGGERS - Use when user needs help with event-budget related tasks.

Trigger: standard work, deming first, feedback loop checks, decision rights, delegation check. Scope: Engineering operating models, team governance, task feedback loops. Boundary: Excludes direct code implementation or design templates.

Use to extract competitor mentions, switching language and feature-gap evidence from support conversations as an input to win/loss and product strategy. Trigger for "what competitors do customers mention", "why do customers switch away", "find feature gaps customers ask about", competitive intelligence from support, or win/loss analysis that only samples deals sales remembers.

Use to design or audit the executive escalation path for a major account — intake, ownership, communication cadence and follow-through — so escalations are resolved rather than merely attended. Trigger for "design our escalation process for key accounts", "an executive escalation went badly", "customer went to our CEO", red account war rooms, or escalations that get attention and then quietly stall.

Trigger: design review, visual audit, layout inspection, QA checks, screenshot analysis. Scope: Performing design system compliance audits and interface QA. Boundary: Excludes functional unit testing or database indexing.

Use to find upgrade, seat-growth and new-use-case signals that customers give support and nobody routes anywhere. Trigger for "find upsell opportunities in support", "customers hitting plan limits", "which accounts are asking about enterprise features", expansion signals from tickets, or support-sourced pipeline.

Provides principles and tactical rules for multi-agent collaboration, task scoping, and file race prevention in swarm execution.

Recognize when you're in a runaway loop and stop yourself. Use when the same tool call has repeated 3× with the same args, when the same error class has fired 3× in a turn, when you've been told the same correction twice, when "let me try one more variation" is the third small variation, or when a refinement loop is orbiting rather than converging. The right move on a trip is to switch from action to inquiry — read events.jsonl, list assumptions, look for contradictions, ask the human, file a chainlink — not to retry harder.

Conduct failure mode and effects analyses. TRIGGERS - Use when user needs help with fmea-guide related tasks.

Designs, reviews, and troubleshoots Apex triggers using a single-trigger-per-object handler pattern with recursion guards and activation bypass.

Trigger: empty list state, loader skeleton, error boundary layout, offline indicator, system fallback UI. Scope: UI fallback layouts, skeleton placeholders, client recovery views. Boundary: Excludes server-side API error status coding.

Diagnose and fix retention problems using behavior design (B=MAP). Use when the user mentions "users drop off", "activation rate", "onboarding friction", "retention metrics", "why users dont complete", "churn analysis", "user activation", or "aha moment". Also trigger when analyzing cohort retention curves, designing activation milestones, reducing time-to-value for new users, or investigating why users stop after their first session. Covers the Ability Chain, prompt design, and tiny behaviors that compound. For habit loops and variable rewards, see hooked-ux. For intrinsic motivation, see drive-motivation.

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.

Trigger: PM, product tasks, project planning, backlog priority, user stories, ticket scoping. Scope: Product management, task priorities, requirements scoping. Boundary: Excludes writing raw code or designing page layouts.

`analysis-agent`/`task-agent`/`review-agent`: use when symptoms, logs, metrics, regressions, or incidents need cause analysis; skip when no diagnosis decision exists.

Trigger: structured logging, tracing, telemetry, SLI metrics, SLO alerts, log formats. Scope: Performance metrics, error tracing, production telemetry. Boundary: Excludes client behavioral product funnels.

Create release plans with scope and deployment strategy. TRIGGERS - Use when user needs help with release-plan related tasks.