Be the Answer in AI on Autopilot
Inspired by AthenaHQ — Be the Answer in AI Search - AI SEO across SEO, GEO & AEO. Loop until the workflow is current, exceptions are owned, and human sign-off is captured where required.
Inspired by AthenaHQ
by Trooper
/loop 30m Start the "Be the Answer in AI on Autopilot" loop. Inspired by AthenaHQ (https://www.athenahq.ai). Goal: open work triaged, exceptions owned, and core sales workflow current with audit trail Max iterations: 20 Between iterations run: Report open queue items, stale tasks, failed automations, and items awaiting human approval for AthenaHQ Exit when: zero open items without owner or explicit escalation, all external actions approved or sent, and systems of record current Step 1 — Aggregate pipeline: Sync leads, accounts, candidates, or calls into one activity stream. Step 2 — Prioritize next actions: AI ranks follow-ups, outreach, and stage moves by urgency and fit. Step 3 — Execute touchpoints: Draft emails, schedule calls, or update CRM fields for approval. Step 4 — Track commitments: Turn promises into owned tasks with full source context. Step 5 — Sync and report: Keep CRM/ATS current and report conversion or SLA gaps. ## Before you start Connect plugins: - GitHub (required) — Read branches, PRs, reviews, checks, workflow runs, and source diffs. - Google Analytics (required) — Read traffic, conversion, product, or campaign performance signals. - Notion (required) — Read and update approved briefs, docs, calendars, and reports. - Gmail (required) — Read incoming mail and prepare safe draft replies for approval. - Slack (required) — Post summaries, approvals, blockers, and handoff updates. - CRM (required) — Read accounts, deals, owners, stages, and onboarding state. Attach skills: - Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition. - Code change + local verification (optional) — Edit code safely, run commands, and keep changes scoped. - CI debugging (optional) — Read failing checks, logs, and the smallest actionable root cause. - Approval workflows (optional) — Keep outbound actions in draft or approval states when risk is non-trivial. - Browser QA (optional) — Exercise product flows, capture visual evidence, and verify fixes in-browser. - Content operations (optional) — Turn signals into reviewable briefs while preserving source attribution. - Operations briefing (optional) — Summarize sources into concise, owner-aware, non-invented updates. - Sales operations (optional) — Audit stale deals, owners, stages, forecast risk, and next steps. Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.
Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.
1. Aggregate pipeline
Sync leads, accounts, candidates, or calls into one activity stream.
2. Prioritize next actions
AI ranks follow-ups, outreach, and stage moves by urgency and fit.
3. Execute touchpoints
Draft emails, schedule calls, or update CRM fields for approval.
4. Track commitments
Turn promises into owned tasks with full source context.
5. Sync and report
Keep CRM/ATS current and report conversion or SLA gaps.
Guardrails
Rules the agent must follow so it cannot cheat the exit condition.
- Require human approval before customer-facing sends, payments, or legal submissions unless pre-approved templates apply
- Preserve full audit trail linking source data to every automated action
- Escalate compliance, safety, or regulatory-sensitive items immediately
More Sales loops
Inbox Triage with Approval
On an interval, classify incoming mail, draft safe replies for routine threads, and escalate anything that needs a human decision.
Morning Operator Brief
Daily interval loop that reads your calendar, open tickets, and inbox priorities, then delivers a concise operator brief with ranked actions.
Customer Onboarding Watch
Interval loop that watches new signups, runs the onboarding checklist against each account, and nudges or escalates stuck users.
